Software testing Life Cycle

Software test automation is not a testing task only, it needs to be developed based on the existing functional requirement. Software testing life cycle follows all the steps as for normal software development follows.Software testing life cycle follows the following phases

• Requirements study and analysis phase
• Test Planning phase
• Test design phase in terms business and application flow
• Design Reviews by design expert
• Design Test Cases
• Code for the test cases
• Code Reviews
• Test Execution
• Test Reports
• Bugs Reporting
• Fixes reported bugs
• Execute test once again against new release
• Release to production

Please note that ,before going to eaplan each steps , I want add that in whole project development life cycle, testing is a very crucial and important part and it consumes highest amount of time. If testing is neglected then erroneous software released may increase total cost of the project and damaged  impression on the project and business. For successful testing, testing team should be involved in a project from initial stage of project development.

Requirements Phase

In many projects, after  development team completes the development of the project,released to testing team for testing .But I strongly fill that testing team should also  involve  along with development team for requirement stage . In this phase tester should analysis the requirement of the project from end user point of view. .All requirements should gather and well documented for future use.

Test Plan

A good plan behind for all successful work . In testing also , a well approach test plan should be prepared as per business needs .

A well approach test plan includes

• Document the all features of the application  to be tested
• Approaches of the test
• Methodology to be used
• Man-hour calculation and measure skills requirement
• Resources required for the whole testing process
• Tools and technology for optimal testing
• Different types of test cases and scenarios

Test Design

Test design depend whether testing is done manually or automatically.For automated testing the framework of the testing should be designed first.
Prepared a checklist, covering all features of each modules of the entire project.Test design should be neat and clean and it should present as diagrammatically.The design phase of testing process is very crucial. On basis of the test design test cases are prepared.Entire project Quality and business depends on test design phase.

Test design includes

• All module of the entire project should identified first.
• Interconnection, data flow and relationship of all modules should identified and if required draw a flow chart diagram.

Design Reviews

It is always recommends to review test  design by design expert ( A person who is having expertize testing and on business  flow ). Reviewer  should  put some comment, suggestion and value addition on the same.

Test Cases Preparation

Test cases are prepared on the basis of test design. It is scenario based. Test cases are prepared on the basis of following categories of scenarios:

• Real word scenarios
• Positive scenarios
• Negative scenarios and
• Boundary conditions scenarios

Development phase

As per the test cases ,developer  start coding.Review the codes  and get ready for unit testing .Before release the code, tester should do some unit testing of  the code. Tester should prepare his own unit test plan and find out the minor mistake done by developer.

Test Execution and Bugs Reporting

After unit testing is completed, the code to be released for testing. Then tester should ready for all types of test cases and find out bugs as many as can. If tester find out more bugs, then good success on testing. The bugs should immediately report to developer to workaround. As developers fix the bug and released the code, tester should re-open the bug and test again and again. The test reports should be documented properly and the bugs have to be reported to the developer after the testing is completed.

Release to Production

Testing is an iterative process .Once the bugs are fixed, the testing has to be done repeatedly. After all bugs are fixed by developer, new release is given to QA with the modified changes. Then tester should execute Regression testing. Before release to production, tester should do another round of top-level testing. Once QA give assurance the project, then the project is released to production.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.