冒烟测试和健全性测试有什么区别? [英] What is the difference between smoke testing and sanity testing?

问题描述

冒烟测试和健全性测试有什么区别?什么时候进行冒烟测试，什么时候进行健全性测试?

What is the difference between smoke testing and sanity testing? When do will perform smoke testing and when do will perform sanity testing?

推荐答案

健全性测试

健全性测试是回归测试的子集，在我们没有足够时间进行测试时执行.

Sanity testing

Sanity testing is the subset of regression testing and it is performed when we do not have enough time for doing testing.

健全性测试是表面级别的测试，QA 工程师验证产品和项目中可用的所有菜单、功能、命令是否正常工作.

Sanity testing is the surface level testing where QA engineer verifies that all the menus, functions, commands available in the product and project are working fine.

例如，在一个项目中有 5 个模块:登录页面、主页、用户详情页面、新用户创建和任务创建.

For example, in a project there are 5 modules: Login Page, Home Page, User's Details Page, New User Creation and Task Creation.

假设我们在登录页面有一个错误:登录页面的用户名字段接受短于 6 个字母数字字符的用户名，这不符合要求，因为在要求中指定用户名应至少为 6字母数字字符.

Suppose we have a bug in the login page: the login page's username field accepts usernames which are shorter than 6 alphanumeric characters, and this is against the requirements, as in the requirements it is specified that the username should be at least 6 alphanumeric characters.

现在测试团队将错误报告给开发团队进行修复.在开发团队修复错误并将应用程序传递给测试团队后，测试团队还会检查应用程序的其他模块，以验证错误修复不会影响其他模块的功能.但请记住一点:测试团队只检查模块的极端功能，由于时间短，不会深入测试细节.

Now the bug is reported by the testing team to the developer team to fix it. After the developing team fixes the bug and passes the app to the testing team, the testing team also checks the other modules of the application in order to verify that the bug fix does not affect the functionality of the other modules. But keep one point always in mind: the testing team only checks the extreme functionality of the modules, it does not go deep to test the details because of the short time.

健全性测试是在构建通过冒烟测试并被 QA 团队接受以进行进一步测试后进行的.健全性测试通过更精细的细节检查主要功能.

Sanity testing is performed after the build has cleared the smoke tests and has been accepted by QA team for further testing. Sanity testing checks the major functionality with finer details.

当开发团队在更改代码后需要快速了解产品的状态时，或者在功能中更改了一些受控代码以修复任何关键问题，以及严格的发布时间时，就会执行健全性测试——框架不允许完整的回归测试.

Sanity testing is performed when the development team needs to know quickly the state of the product after they have done changes in the code, or there is some controlled code changed in a feature to fix any critical issue, and stringent release time-frame does not allow complete regression testing.

在软件构建后执行冒烟测试，以确定程序的关键功能是否正常工作.它在软件构建上执行任何详细的功能或回归测试之前"执行.

Smoke Testing is performed after a software build to ascertain that the critical functionalities of the program are working fine. It is executed "before" any detailed functional or regression tests are executed on the software build.

目的是拒绝严重损坏的应用程序，以便 QA 团队不会浪费时间安装和测试软件应用程序.

The purpose is to reject a badly broken application, so that the QA team does not waste time installing and testing the software application.

在冒烟测试中，选择的测试用例涵盖系统最重要的功能或组件.目标不是执行详尽的测试，而是验证系统的关键功能是否正常工作.例如，典型的冒烟测试是:

In smoke testing, the test cases chosen cover the most important functionalities or components of the system. The objective is not to perform exhaustive testing, but to verify that the critical functionalities of the system are working fine. For example, typical smoke tests would be:

• 验证应用程序是否成功启动，
• 检查 GUI 是否响应

这篇关于冒烟测试和健全性测试有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！