Now days almost everyone is aware of software systems they are part of our lives. We use software in day to day business applications such as banking, consumer products, mobile phones etc.so these applications must be error free.
Software testing finds the mistakes and ensures the quality of the developed. When we are testing something we are checking whether it is OK. The flaws in the software may cause a system to fail. Testing ensures the correctness, completeness and quality of the developed software and gives the confidence in the quality of the software.
“Software Testing delivers the bad news with a smile”.
When software does not behave as expected it may lead to a problem. Testing is necessary because we all make mistakes and some of the mistakes cause a failure. Always testing is done by the third persons because we all blind to our own faults so we make a same mistakes when we check our own work as we made when we did it. Another person is more likely to spot the flaws.
Mistakes are the defects or bugs in the software system; some defects are unimportant some of them are expensive or dangerous. Any defects may cause the system to fail to do what it should do causing a failure.
The defects and failures arising from:
* Errors in the specification, design, implementation
* Errors in use of system
* Environmental conditions
The errors or mistakes can cause a defect or fault at any stage within the software Development life cycle. The error in the requirement can cause defect in the system. An unambiguous requirement can cause a defect same as the error in the designing, implementation and maintenance stages of the SDLC can cause a defect or failure of the develop software system. So the testing is necessary and important on all stages of the SDLC (Software Development Life Cycle).
When the defect or bug found first time it passes through the different stages these stages are called the phases of the bug and it is defined as a Bug Life Cycle. The following diagram illustrates the the different stages of the bug.
Using Defect tracking tool the following process is followed
- Logging in to the tool
- Defect Life Cycle
- Creating a defect
- Changing status of defects
- Generating metrics and reports
When bug is found first time to the tester its status is ‘New’. The tester reported the bug to the development team with the status ‘New’. Then the development leader assigns the bug to the developer with the status “Assigned”. When developer starts working on it its status is “Open”. The developer makes the necessary changes and solves the bug and passes it to the tester with the status “Resolved”. Tester retests the bug and if it is working fine then the bug status is ‘Closed’. And if the the bug is not fix properly and previous problem persist in the system then tester report it to the development team with the status “Reopened”. Again ‘Reopened’ bug passes with the same stages until it get ‘Closed’.Each bug should go through the life cycle to be closed.
No comments:
Post a Comment