Yep, that kind of bug is called a regression. And regression testing is a basic component of (automated and manual) testing. This class of tests often just arises from creating tests for new stuff and specific bugs along the way, but continuing to verify new builds against the whole cumulative test set.
You fix one thing, and another problem pops up somewhere else.
If your modules are unit testable, you can try to write as many tests as possible to cover potential scenarios like this. If the modules can't be realistically unit tested, then yeah, you'll have to regression test the whole system to catch things like this.
Your Scenario is basically stated as during confirmation testing cycle the defect got fixed and that part of the application started working as intended but that fix have introduced or uncovered a different defect elsewhere in the software. So clearly it’s A Regression Bug and should be uncovered in Regression Testing of previously passed functionality.
After adding new functionalities into existing project then we need to check impact of added functionalities on existing functionalities. It is called regression testing.
Def:- Regression testing is a form of software testing that confirms or denies a software’s functionality after the software undergoes changes or enhancement.
发布评论
评论（4）
是的，这种错误称为回归。回归测试是（自动和手动）测试的基本组成部分。此类测试通常只是为新内容和特定错误创建测试而产生，但继续针对整个累积测试集验证新版本。
Yep, that kind of bug is called a regression. And regression testing is a basic component of (automated and manual) testing. This class of tests often just arises from creating tests for new stuff and specific bugs along the way, but continuing to verify new builds against the whole cumulative test set.
我有时将这种现象称为“打地鼠”。
你解决了一件事，但其他地方又出现了另一个问题。
如果您的模块是可单元测试的，您可以尝试编写尽可能多的测试来覆盖此类潜在场景。如果模块无法进行实际的单元测试，那么是的，您必须对整个系统进行回归测试才能捕获此类内容。
I sometimes call this phenomenon "Whack-a-Mole."
You fix one thing, and another problem pops up somewhere else.
If your modules are unit testable, you can try to write as many tests as possible to cover potential scenarios like this. If the modules can't be realistically unit tested, then yeah, you'll have to regression test the whole system to catch things like this.
您的场景基本上被描述为在确认测试周期中缺陷得到修复，并且应用程序的该部分开始按预期工作，但该修复已在软件的其他地方引入或发现了不同的缺陷。所以很明显它是
回归错误应该在先前通过的功能的回归测试中被发现。
Your Scenario is basically stated as during confirmation testing cycle the defect got fixed and that part of the application started working as intended but that fix have introduced or uncovered a different defect elsewhere in the software. So clearly it’s
A Regression Bug and should be uncovered in Regression Testing of previously passed functionality.
在现有项目中添加新功能后，我们需要检查添加的功能对现有功能的影响。这称为回归测试。
Def:- 回归测试是软件测试的一种形式，它在软件发生更改或增强后确认或否认软件的功能。
After adding new functionalities into existing project then we need to check impact of added functionalities on existing functionalities. It is called regression testing.
Def:- Regression testing is a form of software testing that confirms or denies a software’s functionality after the software undergoes changes or enhancement.