Tutorials Testing
The software design is done in systematical manner or using the UML language. The tester can do the reviews over the design and can suggest the ideas and the modifications needed.
Code reviews are similar to unit testing. Once the code is ready for release, the tester should be ready to do unit testing for the code. He must be ready with his own unit test cases. Though a developer does the unit testing, a tester must also do it. The developers may oversee some of the minute mistakes in the code, which a tester may find out.
Once the unit testing is completed and the code is released to QA, the functional testing is done. A top-level testing is done at the beginning of the testing to find out the top-level failures. If any top-level failures occur, the bugs should be reported to the developer immediately to get the required workaround.
The test reports should be documented properly and the bugs have to be reported to the developer after the testing is completed.
Once the bugs are fixed, another release is given to the QA with the modified changes. Regression testing is executed. Once the QA assures the software, the software is released to production. Before releasing to production, another round of top-level testing is done.
The testing process is an iterative process. Once the bugs are fixed, the testing has to be done repeatedly. Thus the testing process is an unending process.
First Page: Life Cycle of Testing Process
|
Hi The article is very informative, Thanks & Regards Kots. |
| this is good |
|
Nice One Regards Rahul bagati |
| This topic is very informative and helpful |
| good one |
| Thanks for the notes.It is very informative |
| Excellent Article. |
| thank u soo much. its excellent . |
|
Good attempt, except that there can be a few modifications. 1. Code Review is not necessary except in case of White Box Testing. Unit testing should NOT be a responsibility of the tester. 2. Bug reporting will come after Test Execution and Test Report will be the last activity before Release to Manufacturing/ Production. So the steps above would be more like: 7. Test Execution 8. Bugs Reporting 9. Regression Testing This loops to Step 8 and finally when desired bug open to fixed level is reach Step 10 Test Report detailing the testing efforts and remaining open issues and why they are not fixed and why it is recommended for release. There is a difference between Bug Report and Test Report. 10. Test Reports 11. Release to production. |
