In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.
In Smoke Testing QA team choose the Test Case which cover the most important functionality. Smoke Testing we can is the first step of testing, rest Function Testing, System testing and other type of Testing will work after Smoke Testing.
Smoke Testing is very quick, generally it takes few minutes and provide the feedback that should further testing is necessary or not. Smoke testing is best cost effective testing because it saves too much time to install and testing further if basic features are not working. Software Testing cover the major function of the software but none of them in detail. Smoke Testing generally perform by developer with using script or black box. Tester also perform Smoke Testing.
Smoke Testing can be possible in both way. It may be Manual and Automation. Smoke Testing came from the hardware Testing. Like in hardware first test is like team will switch on to check did the hardware catches the fire or smoke.
In Smoke Testing QA team will not perform the exhaustive testing. They check the critical functionality like does the application window is opening, Click on button is enable, GUI responsiveness etc. Smoke Testing is needed when we are creating first time build.
Suppose we are testing the Login page of the software so our Smoke Testing Test Cases will be from detailed Test Cases of Login Page
Smoke Testing is very quick, generally it takes few minutes and provide the feedback that should further testing is necessary or not. Smoke testing is best cost effective testing because it saves too much time to install and testing further if basic features are not working. Software Testing cover the major function of the software but none of them in detail. Smoke Testing generally perform by developer with using script or black box. Tester also perform Smoke Testing.
Smoke Testing can be possible in both way. It may be Manual and Automation. Smoke Testing came from the hardware Testing. Like in hardware first test is like team will switch on to check did the hardware catches the fire or smoke.
In Smoke Testing QA team will not perform the exhaustive testing. They check the critical functionality like does the application window is opening, Click on button is enable, GUI responsiveness etc. Smoke Testing is needed when we are creating first time build.
Suppose we are testing the Login page of the software so our Smoke Testing Test Cases will be from detailed Test Cases of Login Page
- Login page is opening
- Page is responsive if required
- Both Test box(email and Password field) and Submit button is enable
- With valid test data Login is done
Comments
Post a Comment