blocks|key|1314487|text|重新测试就是测试失败的用例和解决的bug。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1314488|回归测试是一种测试，它检查添加或更改的功能是否没有导致现有代码中的错误。|1314489|在你的案例中，模块A的重测是50分，模块B的重测是40分。|1314490|很难说你需要多少回归测试，但在这种情况下(许多测试用例失败)，你可能需要测试所有的测试用例。通常，您不会在回归中测试所有内容。|1314491|你可以在维基百科(https://en.wikipedia.org/wiki/Regression_testing)上阅读更多关于回归测试的内容|offset|length|1314492|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Regression_testing^0|0|0|0|0|9|1C|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$J|Y|K|Z|1|10]]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Retesting is testing this tast cases which failed and bugs were solved. 

Regression tests are test which check if added or changed functionality not caused faults in existing code.

In your case retesting will be 50 in Module A and 40 in Module B.

It is hard to say how many regression tests do you need but in such a situation (many test cases failed) probably you need to test all test cases. In general you do not test everything in regression. 

You can read more about regression testing on wikipedia (<a href="https://en.wikipedia.org/wiki/Regression_testing" rel="noreferrer">https://en.wikipedia.org/wiki/Regression_testing</a>)

blocks|key|1259330|text|我同意Kinga的回答。为了识别回归测试用例，您可以创建一个可追溯性矩阵，它将帮助您识别潜在的受影响区域，并且您可以在回归测试套件中包含这些区域的测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1259331|您可以阅读有关traceability+matrix的更多信息|offset|length|1259332|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Traceability_matrix^0|0|7|J|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I agree with Kinga's answer. In order to identify regression test cases, you can create a traceability matrix which will help you identify the potentially affected areas and you can include tests for those areas in your regression test suite. 
You can read more about <a href="https://en.wikipedia.org/wiki/Traceability_matrix" rel="nofollow noreferrer">traceability matrix</a>

blocks|key|1253394|text|执行回归测试是为了确认最近的程序或代码更改是否没有对现有功能产生负面影响。回归测试的目的是，新的代码更改不应该对现有功能产生任何副作用。。对最终执行失败的测试用例进行重新测试，以确认缺陷修复后测试用例通过。在缺陷修复的基础上进行重新测试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253395|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Regression testing is carried out to confirm whether a recent program or code change has not adversely affected existing features.
The purpose of regression testing is that new code changes should not have any side effects to existing functionalities
.
.
Re-testing is carried out to confirm the test cases that failed in the final execution are passing after the defects are fixed. 
Re-testing is done on the basis of the defect fixes

blocks|key|1314604|text|重新测试通常是为了测试报告的bug是否已经修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1314605|回归测试基本上是为了检查修改对依赖模块的影响。它通常在重新测试完成后进行。|1314606|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Retesting usually carried out to test whether the reported bug has been fixed or not.

Regression testing is basically done to check the impact of modification on dependent modules. It usually carried out after the completion of retesting.

blocks|key|1314570|text|您提到的用于重新测试的测试用例数量是正确的。在重新测试中，我们测试那些最初失败的测试用例，现在它们已经被开发人员修复，所以它们被重新测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1314571|您在回归中测试的测试用例的数量取决于您为回归测试套件选择的测试用例。有几个因素，我们根据这些因素来决定在回归测试中包括什么测试用例，或者not.These因素是什么：|1314572|1)如果我们有足够的时间和资源，那么我们可以在回归测试中检查整个应用程序。对于您的问题，这意味着在回归中，您可以为模块A和模块B分别检查100个测试用例和100个测试用例。|1314573|2)您提到模块A的回归测试为50，模块B的回归测试为60，但在回归测试中只测试通过的测试用例并不是必需的，通常也是不遵循的。|1314574|通常在回归中，我们测试那些受到新功能影响的功能。这意味着受模块A和模块B影响的特性也应该包含在回归测试中。|1314575|如果我们没有足够的时间，那么我们可以根据以下几点做出决定：|1314576|a)优先级:基于客户高优先级特性的测试用例。|1314577|b)更改:基于特性的测试用例，这些特性在两个版本之间频繁更改。|1314578|C)经验:基于以前版本中错误数量最多且更容易出错的特性的测试用例。|1314579|等。|1314580|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|14|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|U|$]]

The number of test cases for retesting mentioned by you is right. In retesting we test those test cases which got failed initially and now they have been fixed by developer so they are retested.

The number of test cases you test in regression depends on what test cases you have chooses for your regression test suite. There are several factors on the basis of which we decide what test case to include in regression testing or what to not.These factors can be:

1) If we have enough time and resources then we can check whole application in regression testing. With respect to your question, this means in regression you can check 100 test cases for module A and 100 cases for module B.

2) You mentioned regression tests for module A as 50 and for module B as 60 but it is not necessary and generally not followed that you test only passed test cases in regression testing.

Usually in regression we test those features which got IMPACTED by the new feature. This means features which got affected by module A and Module B should also get included in regression testing. 

If we do not have enough time then we can decide on basis of:

a) Priority: The test cases which are based on features which are of high priority to customers.

b) Changes: The test cases which are based on features which get under change very frequently in between releases.

c)Experience: The test cases which are based on the features which have got most number of error in previous releases and are more error prone.

etc.

blocks|key|5098880|text|在模块的A和B中都有100个测试用例|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5098881|在测试过程中，模块A有50个失败的测试用例，模块B有40个失败的测试用例。|5098882|据我所知，您第一次测试了这些模块，发现模块A的100个测试用例中有50个失败。|5098883|那么模块A和模块B都没有描述任何地方的重新测试和回归测试。|5098884|如果您再次对第一次失败的测试用例执行了测试，则这称为重新测试|5098885|在重新测试期间，如果您发现除这40个bug之外还有一个bug，那么这意味着该bug是在修复40个bug的过程中出现的。在这里，这个bug被称为回归。|5098886|entityMap^0|0|7|0|0|11|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|Z|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|10|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|Q|$]]

You got 100 test cases in both of the module's A and B 

During testing, Module A got 50 failed test cases and Module B got 40 failed test cases.

As per my understanding, You have tested these modules the first time and Found 50 are failed out of 100 test cases in module A.

Then neither Module A or Module B has described the Retesting and Regression testing anywhere.

If again you have performed testing on the test cases which are failed at a very first time then that is called retesting 

and during retesting if you found a bug apart from those 40 bugs then it means that bug coming during the fixing of 40 bugs. Here that bug is called regression.

blocks|key|5098935|text|一旦该版本中的缺陷被修复，QA团队就会执行重新测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5098936|回归测试是针对每个版本以及功能项进行的，因此无论何时部署了代码，代码都不应该影响现有的功能。|5098937|现在，在模块A中，重测测试用例为50个，回归测试用例为50个，模块B中，重测测试用例为40个，回归测试用例为60个。|5098938|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Retesting is carried out by the QA Team once the defect is fixed in that release.

Regression testing is done for every release along with functional items so that whenever there is code deployed, the code shouldn't affect the existing functionalities.

Now, coming to you question in module A, retesting testcases are 50 and regression testcases are 50, In module B, retesting testcases are 40 and regression testcases are 60.

blocks|key|3630904|text|回归与重新测试对于测试人员来说总是一个令人困惑的话题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3630905|下面是我们在执行回归测试时需要注意的事项|3630906|3630907|Impacted+|unordered-list-item|3630908|3630909|错误修复|3630910|有哪些新更改|3630911|要了解更多信息，请查看以下内容：https://www.youtube.com/watch?v=i5DNiSEz464&t=174s|offset|length|3630912|entityMap|0|LINK|mutability|MUTABLE|url|https://www.youtube.com/watch?v=i5DNiSEz464&t=174s^0|0|0|0|0|0|0|0|G|1E|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|11|8|@]|9|@]|A|$]]|$1|H|3|-4|5|G|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|G|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@$O|16|P|17|1|18]]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Regression vs retesting is a always confusing topic for testers.
Majorly below things we need to take care while performing regression testing
<ul>
<li>Impacted area</li>
<li>What are the new changes</li>
<li>Bug fixes</li>
</ul>
For more understanding checkout this: <a href="https://www.youtube.com/watch?v=i5DNiSEz464&amp;t=174s" rel="nofollow noreferrer">https://www.youtube.com/watch?v=i5DNiSEz464&amp;t=174s</a>

blocks|key|5099033|text|回归测试：-定义为一种测试类型，用于验证软件中的更改不会影响现有功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5099034|在回归过程中，我们确保新的更改和错误修复不会影响产品。在这个过程中，我们重新执行之前的测试用例，以验证该功能的更改或错误修复的影响。|5099035|重新测试:-也称为对报告的bug.Retesting进行确认测试，以确保在测试过程中提出的缺陷是固定的&只有在开发端修复失败的测试用例时，才会根据requirement.We重新执行这些测试用例。|5099036|如果你得到了模块A中的100个测试用例，在测试模块A的过程中，你得到了50个失败的测试用例。因此，当你开始重新执行后，开发人员将修复50个失败的测试用例时，失败的50个测试用例被定义为重新测试。|5099037|和回归测试用例：-+Rest重新执行通过的50个测试用例被定义为回归testing.We需要验证它是否应该影响其余通过的测试用例。|5099038|在模块b的测试期间，如果你得到了100个测试用例中的40个失败的测试用例。修复错误后:-重新测试测试用例:-+40回归测试用例:-+60|5099039|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Regression testing:- is defined the type of testing that is done to verify that change in the software does not impact the existing functionality.
On the regression we ensure the new change &amp; bug fixes does not impact the product. In this we executed the previous test cases are re-executed to verify the impact of the change or bug fixes for the feature.
Re-testing :- is also known as the confirmation testing of the reported bug.Retesting is done to ensure that the defect raised during the testing are fixed &amp; work according to the requirement.We only re-executed the failed test-cases when these are fixed from the development side.
If you got the 100 test-cases in the module A and during testing of module A you got 50 failed test-cases.For this when the 50 failed test-cases will be fixed by the developer after when you start re-executing the failed 50 test-cases is defined as the re-testing.
And regression test-cases:- Rest re-executing of the passed 50 test-cases is known is defined as the regression testing.We need to verify that it should impact the rest passed test cases.
During the testing of Module b if you got 40 failed test-cases out of 100 test-cases.
After bug fixing :- Re-testing test-cases :- 40
Regression test-cases :- 60

My question as follows:
There are two modules like Module A and Module B. In Module A, I got 100 testcases and Module B also got 100 testcases. During testing, Module A got 50 failed testcases and Module B got 40 failed testcases.

Now my question is, What are the number of Retesting and Regression testcases to be executed in Module A and Module B on Modified Software Build..?

As per my understanding, In module A, retesting testcases=50 and regression testcases = 50, In module B, retesting testcases = 40 and regression testcases = 60.

Retesting vs Regression Testing

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我的问题如下:有两个模块，像模块A和模块B。在模块A中，我得到了100个测试用例，模块B也得到了100个测试用例。在测试过程中，模块A有50个失败的测试用例，模块B有40个失败的测试用例。现在我的问题是，在修改后的软件构建中，模块A和模块B中要执行的重新测试和回归测试用例的数量是多少？据我所知，在模块A中，重新测试testcases=50和回归测试用例= 50，在模块B中，重新测试测试用例= 40

问重新测试与回归测试
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重新测试与回归测试EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重新测试与回归测试
EN