ASP.NET 应用程序的免费自动回归测试工具？
我们在一个小团队中工作。我们经常遇到这样的问题：developer1 对存储过程或函数进行了一些更改，从而影响了developer2 的工作。此类问题是后来偶然发现的。请指导我如何阻止此类问题。我们可以运行一个免费工具来测试此类问题吗？
We are working in a small team. We often had problems like developer1 did some changes in stored procedure or function and it affected work of developer2. Such issues are traced out by chance later. Please guide me how such issues can be stopped. Is there a free tool that we can run to test such issues?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
慢慢引入单元测试、重点集成测试和完整系统测试。
对于所有这些，都使用 .net 单元测试框架来完成。这将取决于您在测试中所做的操作，从而导致出现上述任何场景。 确保分别保留这 3 种类型的测试，因为它们的执行速度会有很大差异。
对于单元测试框架，我建议 NUnit 但还有其他框架，我是其中一个我发现有趣但从未跳转的是 xUnit.net。
对于完整的系统测试，我建议使用 WatiN 在单元测试框架中运行它们。您也可以使用Selenium RC。
对于这种特定类型的场景，我强烈建议集中进行集成测试。完整的系统测试可能会发现这种情况，但它仍然会让您找出它崩溃的原因。
相反，将测试集中在调用过程的非常具体的数据库访问代码中。通过在其中添加场景来揭示开发人员在编写相关 .net 代码时对所述过程的所有期望，可以非常快速地揭示该集成代码的回归问题并非常有效地进行处理。另请注意，developer1 可以轻松地多次运行涉及该过程或数据库区域的集中集成测试/这比对完整系统测试进行相同的操作更有可能发生。
Slowly introduce unit tests, focused integration tests and full system tests.
For all of those use a .net unit test framework to do it. It'll be what you do in the test what makes it be any of the above scenarios. Make sure to keep each of those 3 type of tests separately, as those will have a big difference on the speed it takes to execute them.
For the unit test framework I suggest NUnit but there are others, one that I've found interesting but never made the jump is xUnit.net.
For full system tests I suggest to run them in the unit test framework using WatiN. You could also go with Selenium RC.
For that specific type of scenario I strongly suggest focused integration tests. Full system tests might catch such scenario, but it will still left you to figure out why it broke.
Instead focus the test in the very specific db access code that makes the call to the procedure. By adding scenarios in there that reveal all the expectations developer2 had from said procedure when (s)he wrote the related .net code, regression issues with that integration code can be revealed very quickly and be dealt with very effectively. Also note that developer1 can easily run the focused integration tests that involve that procedure or area of the database many times / which is a lot more likely to happen than doing the same with full system tests.
您可以使用 NUnit 等工具进行自动化单元测试，也可以使用 < a href="http://seleniumhq.org/" rel="nofollow noreferrer">硒。请注意，这两种选择（即使使用免费工具）可能需要大量的时间和精力投入。通常，单元测试用例是由开发人员自己创建的，而对于自动化黑盒测试，则使用单独的 QA 团队 - 这主要是因为单元测试用例通常用 C#、VB.NET 等语言编写，而自动化黑盒测试测试工具通常使用脚本语言。
You can do either automated unit testing using tools such as NUnit or automated black-box testing using tools such as Selenium. Note that both options (even with free tools) may need significant investment in terms of time and efforts. Typically, unit test cases are created by developers them selves while for automated black box testing, a separate team of QA is utilized - this is mostly because unit test cases are generally written in languages such as C#, VB.NET while automated black-box testing tools typically utilize scripting languages.