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

先决条件 – 软件测试

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.