Smoke Testing
https://www.youtube.com/watch?v=MUn-OusJakA
1.What is Smoke Testing?
Smoke testing is a type of software testing which ensures that the major functionalities of the application are working and software is in a good state to perform further detail testing. The outcome of smoke testing decides if a build is stable enough to proceed with further testing.
It is a type of shallow and wide testing.
Performed with very limited test cases to ensure that the important features are working fine and are good to proceed with the detailed testing.
Usually smoke testing is performed with positive scenarios and with valid data.
Smoke testing establishes the acceptance criteria for QA to accept or reject a build for further testing. .
3. What is the purpose/goal of smoke testing?
Ensure that the critical and or major functionalities of an application are working fine.
Build is stable to be given to testers.
Build is stable to perform detail testing.
4. When to use smoke testing?
It is performed by developers before releasing the build to the testers to ensure that build is ready for test and it is performed by testers to ensure that build is ready for detail testing.
5. What are the advantages of Smoke testing
It helps in finding the bugs in the early stage of testing.
It minimizes integration risks.
It helps in verifying the issues fixed or any new changes are NOT impacting the major functionalities of the application.
Very limited number of test cases are required to do the smoke testing so can be easily automated.
Smoke testing is not time consuming
6. What are the disadvantages of Smoke testing
Smoke testing does not cover the detailed testing.
Critical issues may not be covered in smoke testing as it is done with very few test cases.
Smoke testing is not performed with negative scenarios and with invalid data.
1.What is Smoke Testing?
Smoke testing is a type of software testing which ensures that the major functionalities of the application are working and software is in a good state to perform further detail testing. The outcome of smoke testing decides if a build is stable enough to proceed with further testing.
It is a type of shallow and wide testing.
Performed with very limited test cases to ensure that the important features are working fine and are good to proceed with the detailed testing.
Usually smoke testing is performed with positive scenarios and with valid data.
- Why smoke testing is also known as ‘Build Acceptance testing’?
Smoke testing establishes the acceptance criteria for QA to accept or reject a build for further testing. .
3. What is the purpose/goal of smoke testing?
Ensure that the critical and or major functionalities of an application are working fine.
Build is stable to be given to testers.
Build is stable to perform detail testing.
4. When to use smoke testing?
It is performed by developers before releasing the build to the testers to ensure that build is ready for test and it is performed by testers to ensure that build is ready for detail testing.
5. What are the advantages of Smoke testing
It helps in finding the bugs in the early stage of testing.
It minimizes integration risks.
It helps in verifying the issues fixed or any new changes are NOT impacting the major functionalities of the application.
Very limited number of test cases are required to do the smoke testing so can be easily automated.
Smoke testing is not time consuming
6. What are the disadvantages of Smoke testing
Smoke testing does not cover the detailed testing.
Critical issues may not be covered in smoke testing as it is done with very few test cases.
Smoke testing is not performed with negative scenarios and with invalid data.
Comments
Post a Comment