使单元测试快速失败以进行突变测试-Makingunittestsfailquicklyformutationtesting

2  

Your best best is to check out the heckle source from github, patch it, and submit that patch to the developers. You ought to be able to write a custom test runner for heckle.

你最好的方法是从github查看heckle源码,修补它,并将该补丁提交给开发人员。你应该能够为heckle编写一个自定义测试运行器。

Monkey patching is never the answer for something like this. In fact, monkey patching is almost never the answer for anything.

猴子补丁永远不会是这样的回答。事实上,猴子补丁几乎不是任何事情的答案。

2  

My mutant tool uses the rspec2 --fail-fast option to stop immediately once a failing example was encountered. Together with the --rspec-dm2 strategy that only executes affected unit tests we get very fast mutation coverage testing. See this asciicast for a (speed) demonstration.

我的突变工具使用rspec2 --fail-fast选项在遇到失败的示例后立即停止。与仅执行受影响的单元测试的--rspec-dm2策略一起,我们可以获得非常快速的变异覆盖测试。请参阅此asciicast进行(速度)演示。

1  

One approach I've started using was writing unit tests for each method, and putting them in separate files, organized like rubyspecs. I run each spec in isolation, specifying the exact method I want to heckle. I have a rake task that manages all this and prints a report at the end with failing mutations, if any.

我开始使用的一种方法是为每个方法编写单元测试,并将它们放在单独的文件中,组织起来像rubyspecs。我单独运行每个规范,指定我想要解决的确切方法。我有一个rake任务来管理所有这些并在最后打印一个报告,如果有的话,失败的突变。

In the end I get full heckle coverage of each method, without waiting forever for the results. Plus it's even better than the normal approach everyone uses, because I don't get any incidental coverage -- each methods's specs must cover all mutations of that method.

最后,我得到了对每种方法的全面覆盖,而不必永远等待结果。此外,它甚至比每个人使用的正常方法更好,因为我没有得到任何偶然的报道 - 每个方法的规范必须涵盖该方法的所有突变。