QA 如何在验证新产品特性和功能的同时验证现有产品功能是否仍然有效？
QA 如何在验证新产品特性和功能的同时验证现有产品功能是否仍然有效？
How does QA verify that existing product functionality is still working while verifying new product features and functionality?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
通常，您会使用单元测试来安排某种回归测试。除此之外，这几乎是不可能的。
Normally, you would employ unit tests to arrange for some sort of regression testing. Other than that, this is hardly possible.
回归测试。部分自动化，部分手动，具体取决于工具、时间和金钱。
通常，您应该进行不同级别的测试，即使作为软件开发人员，我们希望将所有事情自动化，但有些事情必须通过测试人员执行的测试用例集合来手动验证。
关于回归测试的维基百科文章值得一读。
从大多数手动检查的整个测试集合中，通常值得选择保证系统功能的最小集合以降低成本。当然，这种平衡是一个很好的平衡，并且在很大程度上取决于代码实际更改的程度。软件产品的良好模块化对于良好的回归测试有很大帮助。
Regression Testing. Partly automated, partly manual, depending on the tools, time and money.
Normally you should different levels of testing, and even though as software developers we would like to automate everything, some things have to be verified by hand, by having a collection of test cases executed by testers.
The Wikipedia article on regression testing is a good read.
From the whole collection of tests that most be checked by hand, it is normally worthwhile to select the minimum set that guarantee the functionality of the system to reduce costs. The balance, of course, is a fine one and depends a lot on how much the code was actually changed. Good modularization of the software product helps a lot on having good regression testing.
我阅读了大量有关测试的内容，在三脚架（所有地方）上找到了极好的资源。我将链接到它，以便其他人也可以从中受益。查看 什么是软件测试..？ 它的轮廓清晰，可以回答您可能遇到的“大多数”问题。
http://bazman.tripod.com
I read up quite a lot about testing, found an excellent resource on tripod (of all places). I will just link to it so other people can benefit from it also. Look under What is software Testing..? It's clearly outlined to answer the "majority" of questions you might have.
http://bazman.tripod.com
除了 @Developer Art 指出的单元测试之外，验证现有功能的另一种主要方法是进行自动化集成和系统级测试。这些将捕获单元测试容易遗漏的系统组件之间的接口问题。
关于测试自动化的维基百科条目是对该主题的很好的介绍。
The other main way to verifiy existing functionality is to have automated integration and system level test/s, in addition to unit testing as pointed out by @Developer Art. These will catch problems in the interfaces between system components that unit tests are liable to miss.
The Wikipedia entry on test automation is a good introduction to the topic.