重新测试与健全性测试之间的区别

先决条件–软件测试

1.重新测试：
在“软件测试”中，“重新测试”指的是再次对模块进行测试，以确保修复了该错误。这意味着在纠正错误/缺陷后，可以确认最终执行失败的测试用例是否通过。

重新测试的过程如下-

• 首先，在应用程序的任何模块中都检测到错误。
• 然后，显影剂对其进行校正/修改。
• 开发人员再次解决并测试问题后，称为重新测试。

2.健全性测试：
在软件测试中，健全性测试是指在接收到软件版本后进行的测试，其中代码或功能进行了微小更改，以确定错误/错误已得到修复，并且由于这些更改而没有引入其他问题。

健全性测试的过程如下-

• 首先会收到一个软件版本。
• 确定更改后提议的功能大致按预期工作。
• 如果完整性测试失败，则将拒绝该构建。
• 如果健全性测试通过，它将通过进一步测试。

重新测试与健全性测试之间的区别：

S.No.	Re-Testing	Sanity Testing
1.	Re-Testing is carried out to check and confirm that the test cases that failed in the final execution are passing after those errors/defects are solved.	Sanity Testing is carried out to check and confirm that the functionalities are working perfectly after minor functionality/bug fixes or any changes.
2.	Defect verification comes under Re-Testing as a part.	Defect verification does not come under Sanity Testing as a part.
3.	Re-Testing is performed before start of Sanity Testing and Regression Testing.	Sanity Testing is performed before Regression Testing and after Smoke Testing.
4.	Test cases can not be automated for Re-Testing.	Sanity Testing is often executed manually.
5.	Re-Testing can be performed with the previously used test cases. Means test cases can be reused.	Sanity Testing can be performed without test cases with domain knowledge.
6.	Priority of Re-Testing is higher than Sanity Testing.	Priority of Sanity testing is lower than Sanity Testing.
7.	Before start of testing, test cases for Re-Testing cannot be obtained.	Test cases for Sanity Testing can be obtained from obtained from the functional specification, manuals, and defect reports in regards to corrected problems.