mutation-testing

Mutation testing - Pittest error (No mutations found)

北城余情 提交于 2021-01-28 08:45:37
问题 I am using https://github.com/hcoles/pitest to write mutation tests on our existing Unit Test suite. We are getting an error as below: 12:09:40 PM PIT >> INFO : MINION : 12:09:40 PM PIT >> FINE : Expecting 1 tests classes from parent 12:09:40 PM PIT >> INFO : MINION : 12:09:40 PM PIT >> FINE : Tests classes received 12:09:40 PM PIT >> INFO : MINION : 12:09:40 PM PIT >> INFO : Found 0 tests 12:09:40 PM PIT >> INFO : MINION : 12:09:40 PM PIT >> INFO : Dependency analysis reduced number of

Pitest can't detect class of test

爱⌒轻易说出口 提交于 2020-01-10 06:09:28
问题 i have problem with my configuration of maven and pitest. Pitest generation mutation is ok but he can't see my class of test .. if you have any solution :D I have main source like that /src/main/java/com.plugin..... .java I have test source like that /src/test/java/com.plugin.... .java pom.xml config : <plugin> <groupId>org.pitest</groupId> <artifactId>pitest-maven</artifactId> <version>1.1.9</version> <configuration> <targetClasses> <param>com.plugin.business.centre*</param> </targetClasses>

Pitest can't detect class of test

给你一囗甜甜゛ 提交于 2020-01-10 06:09:14
问题 i have problem with my configuration of maven and pitest. Pitest generation mutation is ok but he can't see my class of test .. if you have any solution :D I have main source like that /src/main/java/com.plugin..... .java I have test source like that /src/test/java/com.plugin.... .java pom.xml config : <plugin> <groupId>org.pitest</groupId> <artifactId>pitest-maven</artifactId> <version>1.1.9</version> <configuration> <targetClasses> <param>com.plugin.business.centre*</param> </targetClasses>

Run Pitest from the command line

孤街醉人 提交于 2019-12-23 08:28:59
问题 According to Pitest's documentation, it seems that this should be simple, but it is giving me some trouble. I should be able to have java -cp <your classpath> \ org.pitest.mutationtest.commandline.MutationCoverageReport \ --reportDir c:\\mutationReports \ --targetClasses example.foo.* \ --sourceDirs c:\\myProject\\src \ --targetTests example.foo* but I don't know what some of those things should be for my project, such as "<your classpath>". My project's file structure looks like this:

Run Pitest from the command line

泪湿孤枕 提交于 2019-12-23 08:28:11
问题 According to Pitest's documentation, it seems that this should be simple, but it is giving me some trouble. I should be able to have java -cp <your classpath> \ org.pitest.mutationtest.commandline.MutationCoverageReport \ --reportDir c:\\mutationReports \ --targetClasses example.foo.* \ --sourceDirs c:\\myProject\\src \ --targetTests example.foo* but I don't know what some of those things should be for my project, such as "<your classpath>". My project's file structure looks like this:

How can I perform mutation testing of my Java program?

此生再无相见时 提交于 2019-12-21 04:53:38
问题 Can anyone provide suggestions of tools that can be used to make mutations within a Java program at a source-code (not byte-code) level? I need to seed my source code with faults. I would prefer an application with a GUI, if one exists. 回答1: I've found PIT Mutation Testing tool, which I quite like. With MuJava I have exceptions caused by @Override annotations. Seems that it doesnt' support Java 5/6. 回答2: When I took a software engineering class on testing at GMU, we used Mu Java, for one of

Is mutation testing useful in practice?

五迷三道 提交于 2019-12-18 10:47:12
问题 Do you have any examples of real life applications of mutation testing? Does it work better than simple test coverage tools? Or is it useless? What are the advantages/disadvantages of mutation testing in the real world? 回答1: The usefulness of unit tests is no longer discussed. They are essential in conception of a quality application. But, how can we assess their relevance? A code coverage indicator up to 100% doesn’t mean the code is 100% tested. This is just a view of executed code during

JUnit tests pass but PIT says the suite isn't green

久未见 提交于 2019-12-04 10:17:33
问题 While trying to run a PIT mutation test I get the following error: mutationCoverage failed: All tests did not pass without mutation when calculating line coverage. Mutation testing requires a green suite. The tests run just fine when I do a normal test build but while running the mutation tests phase they supposedly fail but no details are provided as to why. I have gone through the reasons listed on the PIT Testing FAQ but I still have no clue what could be wrong. I tried: adding the

How can I perform mutation testing of my Java program?

不想你离开。 提交于 2019-12-03 14:24:51
Can anyone provide suggestions of tools that can be used to make mutations within a Java program at a source-code (not byte-code) level? I need to seed my source code with faults. I would prefer an application with a GUI, if one exists. I've found PIT Mutation Testing tool, which I quite like. With MuJava I have exceptions caused by @Override annotations. Seems that it doesnt' support Java 5/6. When I took a software engineering class on testing at GMU, we used Mu Java , for one of the chapters. HTH This is the technique used by the open source test coverage tool Jester . A look at it's source

Are there any good mutation testing tools for ruby 1.9 and RSpec2?

半世苍凉 提交于 2019-12-03 09:47:59
问题 I used to use Heckle, but it is incompatible with ruby 1.9 because of issues with ParseTree. I've looked for alternatives, but the only thing that looked promising was Chaser, and that did not have any clear documentation that I could use to see if I could make it work with RSpec. It seems to have Test::Unit dependencies. So - is anyone out there using any cool tools to really check the quality of your tests? Alternatively - are there any coverage tools that provide better than c0 coverage?