需要 C# .Net 的实时、自动、后台编译器和测试运行器
我用谷歌搜索并尝试了测试脚本（powershell/spec/nunit/msbuild）。我正在寻找一个测试运行程序来监视我的代码，并不断重建和重新运行我的所有测试以获得解决方案。目前我正在使用 Resharper，它可以对我的代码进行实时编译分析、resharper 测试运行程序和测试驱动的 .Net。
如果解决方案自动编译，运行我的测试并给出带有红/绿点的报告（甚至可能给我带有超链接的报告），这将是理想的。
编辑： 我已经找到了我正在寻找的东西：我发现的工具完全符合我想要的功能：http://www.ncrunch.net/ 这不是广告。
此外，带有快捷方式（cntrl+shift+q）的 TestDriven .Net 效果也很好。
I have googled around and played around with test scripts (powershell/spec/nunit/msbuild). I am looking for a test runner that will monitor my code and will continuously rebuild and rerun all my tests for a solution. Currently I am using Resharper which has real-time compile analysis of my code, the resharper test runner and test driven .Net.
If the solution automatically compiled, ran my tests and gave a report with a red/green dot (maybe even give me a report with hyperlinks) this would be ideal.
Edit:
I have found exactly what I was looking for: the tool I found that does exactly what I want it to do:http://www.ncrunch.net/
This is not an ad.
Also, TestDriven .Net with a shortcut (cntrl+shift+q) works pretty well.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
NCrunch 开始看起来非常有前途。
NCrunch is starting to look very promising.
James Avery 不久前设置了类似的内容： http://averyblog.com /net/announcing-autotest-net-0-1/
看起来谷歌代码项目仍然存在。
James Avery set up something like this a while ago: http://averyblog.com/net/announcing-autotest-net-0-1/
Looks like the google code project is still around.
这种工具称为构建服务器和定期提交（例如使用分布式源代码控制）。
我想知道你是否曾经在 VS 中直接在某个地方看到过这个工作？一旦 VS 开始编译或测试运行，它就死了，因此在完成之前您无法工作（如果构建和测试包含整个解决方案，有时需要几分钟）。后台进程看起来也不像解决方案，因为它可能会导致锁定文件（除非使用卷影复制，这可能会导致其他问题）。
Such tool is called build server and regular commits (for example with distributed source control).
I wonder if you have ever seen this work in VS directly somewhere? Once VS starts compilation or test run, it is dead so you cannot work until it is done (sometimes for several minutes if the build and test contains whole solution). Background process also doesn't look like a solution because it can cause locking files (unless shadow copying is used which can result in other problems).