📌  相关文章
📜  脚本测试和探索性测试的区别

📅  最后修改于: 2021-09-15 01:43:30             🧑  作者: Mango

1. 脚本测试：

在测试特定功能的脚本测试中，测试人员遵循详细的逐步系统方法。对于此测试，测试人员必须提前定义功能的测试用例以及执行它的指令，最后是测试的预期结果。测试人员清楚地遵循测试说明和步骤，但以防他们可能会偏离脚本，但在脚本测试的情况下这是非常小的。它确保每个功能都必须经过测试并通过。在此脚本化测试技术资源中，需要编写良好的脚本说明和测试用例以及验证。

好处：

  1. 非常适合自动化。
  2. 善于发现功能缺陷。
  3. 标准化文档有助于可重复性和跟踪。

缺点：

  1. 非标准测试出来是一个问题。
  2. 发现的错误更少。
  3. 测试范围仅限于脚本。

2. 探索性测试：

探索性测试更倾向于基于学习和经验的测试方法，这意味着它更多地取决于测试人员的责任。因此，测试人员可以将这种探索性测试应用于任何测试技术和任何时间的开发阶段。探索性测试的关键在于它取决于各个测试人员的技能和经验。由于它适应变化，因此非常适合快速变化的开发过程，非常适合敏捷开发方法。

好处：

  1. 当应用程序处于活动状态时，它会以更好的方式分析应用程序。
  2. 测试人员的创造力、经验和技能对测试结果有很大影响。
  3. 帮助查找可用性和 UI 问题。
  4. 项目所有者可以获得脚本测试无法获得的见解。

缺点：

  1. 没有可供参考的文档。
  2. 可能存在取决于测试人员的偏差。
  3. 可能会遗漏严重的错误。

脚本测试和探索性测试的区别：

S.NO.

SCRIPTED TESTING

EXPLORATORY TESTING
01. The test scripts can be traced back to the original requirements and specifications to demonstrate test coverage. In this testing no well documented, clear and measurable test coverage.
02. The application is verified against the specifications. The application is verified and compared against the expectations and understanding of the tester.
03. The testing can be easily reproduced. Where as in exploratory testing, testing can not be reproduced, but the defects can be.
04. This approach emphasizes prediction and decision-making. This approach emphasizes adaptability and learning.
05. At the end of test cycle bugs are detected. This approaches focuses more on test design.
06. Testers need to follow the sequence and steps of test cases which are designed in advance. Testers can alter tests on the fly.
07. Feedback is slower. Enables rapid feedback.
08. In this testing all test scripts and test cases are designed and reviewed in advance. As like scripted testing, in this test cases cannot be reviewed in advance.
09. At the end of the testing cycle, testers can confirm if all the requirements have been met or not. As there is no clear and documented test cases, so there is no way to check and confirm that all the requirements have been met.
10. Managing test coverage is easier. Managing test coverage is challenging.
11. It can be automated.  It cannot be automated.