Smoke testing and Real Testing – Manual testing
Smoke testing and Real Testing – Manual testing
d) Smoke testing :
Smoke testing is team level activity . During this test all testers can gather at one cabin and then operate corresponding sprint screen to screen to know run time errors in that sprint.
In general testers can select some cases as fixed for all sprint builds smoke testing. Here , selected cases are related to main modules / activities of sprint.
If any selected case for smoke testing was failed on sprint , then testers can reject that sprint. If all selected test cases upon smoke testing were passed on sprint then testers can go to real testing.
Highlights :
–> Get sprint build from sever to one cabin system.
–> All testers can gather at that cabin system.
–> Execute some fixed cases related to main modules on sprint.
–> If any case field , testers reject sprint for real testing.
–> If all selected cases for smoke test were passed , then testers can go to real test.
–> Smoke testing is also called as build verification testing or tester acceptance testing .
e) Real Testing / Comprehensive Testing :
After completion of smoke testing on sprint build by executing a fixed set of cases related to main modules or functionalities , corresponding scrum team testers can back to their cabin system and concentrate on responsible modules testing by executing all cases.
| Smoke Testing | Real Testing |
| –> By all testers in one cabin.
–> On sprint
–> Execute some fixed set of level cases related to main modules or activities.
–> If any case was failed , reject sprint for real test.
–> To confirm that sprint build working or not in “Test environment”. |
–> By testers in corresponding cabin.
–> On responsible modules in sprint.
–> Execute all cases related to responsible modules.
–> If any case was failed , report defect / issue/ incident/ ticket to developer.
–> To confirm that sprint build is working correctly and completely or not w.r.t customer requirements and expectations. |
Note 1 :
During real testing corresponding tester can compare each test case expected value and sprint actual value. If any miss match in between expected and actual , corresponding tester can stop testing and concentrate on defect reporting.
Note 2 :
Miss match in between test case expected value and sprint build actual value is called as defect /issue / incident / ticket.
f) Error ,Defect ,Bug and failure:
A developer finds a problem in his/her program called as Error/ Flaw.
A tester finds a problem in developers developed software called it as Defect/ issue / incident/ ticket. Developers accepted tester reported defect is called it as bug.
Customer or endures faced a problem in software call it as failure / latent bug / missed bug.
In this article we have seen Smoke testing and Real Testing – Manual testing and Error ,Defect ,Bug and failure. In the next article will see Defect Report Format in IEEE829.
