MμClipse only supports JUnit 3 and is no longer maintained. Jester as for it, is laborious and requires a complicated configuration; plus is not maintained anymore. The best tool I could find is Javalanche I had wrote a entire article about this !
我的公司 State Farm 编写了一个 Ant 任务，我们可以将其贡献给 Jumble 项目。 根据我在他们的邮件列表中读到的内容，其他人也在为 Jumble 开发 Ant 任务。
我也在看Javalanche。 当我完成后，我会很高兴分享我所知道的。
Jester does provide a file for the mutations and they are limited. To some degree, you can add your own mutations to the file.
I've experimented with Jumble and Jester and I found that Jumble provides more mutations and better documentation. Additionally, I've had quick responses from the project owners when I've emailed them. One drawback to Jumble is that it operates on the bytecode using BCEL. That presents something of a learning curve for many developers.
My company, State Farm, wrote an Ant task that we may contribute back to the Jumble project. Based on what I've read in their mailing lists, others are working on an Ant task for Jumble too.
I'm looking at Javalanche as well. I’ll be glad to share what I know when I’m done.
I know it's an old thread, but it's still an answer to the question. I'm working with some friends on an open source .NET mutation testing framework called NinjaTurtles, which you can find on CodePlex and on Nuget. The main project website is here.
混乱是另一回事:)。 它有一个简单的命令行界面，并且还附带一个 Eclipse 插件。 反馈是控制台中的所有文本。 我对这个工具很满意，我计划编写一些 ANT 目标，将其添加到我的项目持续集成中。
我也在看 Javalanche 但还没有尝试过。
几周后我会有消息。
I took a look at Jester (the actual source code) and it seems to me that it does not support too many mutations. There is a file in there where these mutations are specified. I might be wrong about the above but what I definitely did not like was the mix between launching the tool from command line and the little GUI feedback interface. Why not give feedback in the command line like JUnit does when run outside an IDE?
Jumble is another thing :). It has a simple command line interface and comes with an Eclipse plugin too. The feedback is all text in the console. I am happy with this tool and I plan to write some ANT target to add it in my project continuous integration.
I am also looking at Javalanche but did not try it yet.
There is also PIT which can be hooked into your build via a maven plugin or command line interface.
It provides much nicer reports than the other available tools with combined mutation and line coverage. It also runs considerably faster than the source based tools for Java such as Jester, and about twice as fast as Jumble.
Unlike the Jumble and Javalanche it also works with all the major mocking frameworks (Mockito, JMock, EasyMock, PowerMock and JMockit).
发布评论
评论（11）
可能会有一些兴趣。 微软研究院：https://pex4fun.com/
Might be of some interest. Microsoft Research's: https://pex4fun.com/
您可以尝试 μJava。 我还没有使用过它，但看起来突变测试可能是评估测试套件的一种有趣的方法。
You can try µJava. I haven't used it, but it looks like mutation testing might be an interesting way to evaluate test suites.
MμClipse 仅支持 JUnit 3 并且不再维护。
而Jester则比较费力并且需要复杂的配置； plus 不再维护。
我能找到的最好的工具是 Javalanche
我写了一篇关于此的整篇文章！< /a>
MμClipse only supports JUnit 3 and is no longer maintained.
Jester as for it, is laborious and requires a complicated configuration; plus is not maintained anymore.
The best tool I could find is Javalanche
I had wrote a entire article about this !
Jester 确实提供了突变文件，但它们是有限的。 在某种程度上，您可以将自己的突变添加到文件中。
我尝试过 Jumble 和 Jester，发现 Jumble 提供了更多的突变和更好的文档。 此外，当我向项目所有者发送电子邮件时，我很快就得到了回复。 Jumble 的一个缺点是它使用 BCEL 对字节码进行操作。 这对许多开发人员来说是一个学习曲线。
我的公司 State Farm 编写了一个 Ant 任务，我们可以将其贡献给 Jumble 项目。 根据我在他们的邮件列表中读到的内容，其他人也在为 Jumble 开发 Ant 任务。
我也在看Javalanche。 当我完成后，我会很高兴分享我所知道的。
Jester does provide a file for the mutations and they are limited. To some degree, you can add your own mutations to the file.
I've experimented with Jumble and Jester and I found that Jumble provides more mutations and better documentation. Additionally, I've had quick responses from the project owners when I've emailed them. One drawback to Jumble is that it operates on the bytecode using BCEL. That presents something of a learning curve for many developers.
My company, State Farm, wrote an Ant task that we may contribute back to the Jumble project. Based on what I've read in their mailing lists, others are working on an Ant task for Jumble too.
I'm looking at Javalanche as well. I’ll be glad to share what I know when I’m done.
我知道这是一个旧线程，但它仍然是问题的答案。 我正在与一些朋友合作开发一个名为 NinjaTurtles 的开源 .NET 突变测试框架，您可以在 CodePlex 和 在 Nuget 上。 主要项目网站位于此处。
I know it's an old thread, but it's still an answer to the question. I'm working with some friends on an open source .NET mutation testing framework called NinjaTurtles, which you can find on CodePlex and on Nuget. The main project website is here.
我只知道两个框架，但它们都是针对 Java 的:)
恐怕我还没有使用过它们中的任何一个。
I only know of two frameworks, but they're both for Java :)
I haven't used either of them, I'm afraid.
CREAM 是 C#/.Net 的工具
http://galera.ii.pw.edu.pl/~adr /CREAM/index.php
CREAM is a tool for C#/.Net
http://galera.ii.pw.edu.pl/~adr/CREAM/index.php
对于 Ruby，有 Heckle，并且一个叫 Boo_hiss 的新人。
For Ruby there is Heckle, and a newcomer called Boo_hiss.
对于.Net社区，有NesTer，但它有一些严重的局限性。 例如仅支持C#和NUnit。
似乎也没有得到积极维护，但这可能是一个起点。
For the .Net community, there is NesTer, but it has some serious limitations. E.g. only supports C# and NUnit.
Does not appear to be actively maintained either, but it might be a starting point.
我看了一下 Jester（实际的源代码），在我看来它不支持太多的突变。 那里有一个文件指定了这些突变。 我对上面的看法可能是错误的，但我绝对不喜欢的是从命令行启动工具和小 GUI 反馈界面之间的混合。 为什么不像 JUnit 在 IDE 外部运行时那样在命令行中提供反馈？
混乱是另一回事:)。 它有一个简单的命令行界面，并且还附带一个 Eclipse 插件。 反馈是控制台中的所有文本。 我对这个工具很满意，我计划编写一些 ANT 目标，将其添加到我的项目持续集成中。
我也在看 Javalanche 但还没有尝试过。
几周后我会有消息。
I took a look at Jester (the actual source code) and it seems to me that it does not support too many mutations. There is a file in there where these mutations are specified. I might be wrong about the above but what I definitely did not like was the mix between launching the tool from command line and the little GUI feedback interface. Why not give feedback in the command line like JUnit does when run outside an IDE?
Jumble is another thing :). It has a simple command line interface and comes with an Eclipse plugin too. The feedback is all text in the console. I am happy with this tool and I plan to write some ANT target to add it in my project continuous integration.
I am also looking at Javalanche but did not try it yet.
I'll have news in a few weeks.
还有 PIT 可以通过 Maven 插件或命令行界面连接到您的构建中。
它提供了比其他可用工具更好的报告，结合了突变和品系覆盖。 它的运行速度也比 Jester 等基于源代码的 Java 工具快得多，大约是 Jumble 的两倍。
与 Jumble 和 Javalanche 不同，它还适用于所有主要的模拟框架（Mockito、JMock、EasyMock、PowerMock 和 JMockit）。
（披露我是作者）。
There is also PIT which can be hooked into your build via a maven plugin or command line interface.
It provides much nicer reports than the other available tools with combined mutation and line coverage. It also runs considerably faster than the source based tools for Java such as Jester, and about twice as fast as Jumble.
Unlike the Jumble and Javalanche it also works with all the major mocking frameworks (Mockito, JMock, EasyMock, PowerMock and JMockit).
(disclosure I'm the author).