Bug Life cycle: Stages of a Bug that goes through it's entire life cycle from New to Close.

✓ New: When a bug is logged and posted for the first time. It’s state is given as new.

✓ Assigned: After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer and the developer team. It’s state given as assigned.

✓ Open: At this state the developer has started analyzing and working on the defect fix.

✓ Fixed: When developer makes necessary code changes and verifies the changes then he/she can make bug status as ‘Fixed’ and the bug is passed to testing team.

✓ Pending retest: After fixing the defect the developer has given that particular code for retesting to the tester. Here the testing is pending on the testers end. Hence its status is pending retest.

✓ Retest: At this stage the tester do the retesting of the changed code which developer has given to him to check whether the defect got fixed or not.

✓ Verified: The tester tests the bug again after it got fixed by the developer. If the bug is not present in the software, he approves that the bug is fixed and changes the status to “verified”.

✓ Re-open: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to “reopened”. The bug goes through the life cycle once again.

✓ Closed : Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “closed”. This state means that the bug is fixed, tested and approved.

• Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “duplicate“.

• Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to “rejected”.

• Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software.

• Not a bug: The state given as “Not a bug” if there is no change in the functionality of the application. For an example: If a customer asks for some change in the look and feel of the application like change of color of some text then it is not a bug but just some change in the look of the application.

Important Software Testing Interview Questions

             

 

1. Manual vs Automation Testing
2. Waterfall vs Agile model
3. Bug life cycle
4. Error, bugs, defect
5. Entry criteria and Extra criteria
6. Mutation Testing
7. Defect clustering
8. Exploratory testing
9. Difference between Regression vs Retesting
10. Alpha vs Beta
11. Smoke vs Sanity
12. Static vs Dynamic
13. Domain testing
14. SDLC
15. STLC
16. How to test login, sign up page
17. 100% testing possible ?
18. Write test cases for add to cart screen.
19. High level test cases scenario for uber or Ola app
20. How you maintain communication between development team and others. 
21. Explain your work as tester.
22. Test design techniques
23. Requirement Traceability Metrix
24. Shift left testing
25. Severity and Priority with examples

Why Testing is important.....

 

                                          

Why Testing is important.....

Testing is about verifying that what was specified; what was delivered. In simple word software, testing is an activity to check whether the actual results match the expected result. It is very important to understand that testing is also a continuous process. Testing does not stand alone it is intimately dependant activity but it is separate process activity. Testing is the activity which can reduce the defects.

Testing is also begun from the starting phase of the SW Life cycle from the requirements. Traditionally testing is taking place at end of the s/w life cycle (Waterfall model), Testing should take place throughout the software life cycle. If you want to cut down the cost of the bug find a bug as early as possible. Testing is like repeated activity testing never completed in one pass it has to be given more passes or you can more iteration. Because as you do so you generate more confident for that product.

We say the best software which tested by thousands of users under various different condition. Then we can say it is good to go or “stable” but this does not mean that software is bugfree.it’s mean that bugs are well-identified and well understood.

Software bugs can potentially cause monetary or even loss of life. It can be expensive or even dangerous.