Life cycle of Software testing

The life cycle testing software test identifies activities to perform and when (which is the best time) to carry out testing activities. Although tests of difference between organizations, there is a life cycle testing.

Software testing life cycle consists of six (generic) phases:
* Test Planning
* Test Analysis
* Test design
* Construction and verification,
* Testing Cycles
* Final test of the implementation and
* Post Implementation.

Software testing has its own life cycle that crosses every stage of SDLC. The basic requirements in testing the software life cycle is to control or deal with software testing - manual, automatic and performance.

Test Planning-

This is the phase in which the Project Manager has to decide what things need to be tested, I have an adequate budget, etc. Proper planning course at this stage largely to reduce the risk of low quality software. This planning is a continuous process without end.

Test Analysis-
Once you make a prove plan and decided, the next step is to dig in on the project and decide which prove should be carried out at different stages of SDLC, do we need or plan to automate, if so, then, when the right time to automate, what type of specific documents I need for testing.

Adequate and regular meetings be held between the test equipment, project managers, development teams, business analysts to check the progress of the things that will give you a clear idea of moving the project and ensure the integrity of the test plan created in the planning phase, which will further help in enhancing the right testing strategy created earlier. We will start creating test case formats and test cases itself. At this stage we need to develop Functional validation matrix based on Business Requirements to ensure that all system requirements are covered by one or more test cases, identify test cases to automate, begin to examine the documentation, i.e., functional design, Business Requirements, Specifications, products, etc. Also define External areas for stress and performance testing.

Construction and verification-
At this stage we have to complete all test plans, test cases, complete script automated test cases, stress and performance test plans need to be completed. We must support the development team in its early test drive. And, obviously, the reporting of errors is carried out as when they are insects. Integration tests are performed and errors (if any) are reported.

Test Cycles-
At this stage we have to complete the test cycles until test cases are executed without errors or a predefined condition is reached. Run test cases -> Error Reporting -> revise test cases (if needed) -> Add new test cases (if needed) -> bug fixes -> retesting (test cycle 2, 3-cycle tests ....).

Final testing and implementation-
In this we have to run stress and other benchmark cases, the documentation for the test has been completed or updated, the grant of different matrices for the test. The acceptance, loading and recovery tests were also conducted and the application must be verified under the conditions of production.
Post-deployment-
At this stage, the testing process is evaluated and lessons learned from this testing process are documented. Line of attack to avoid similar problems in future projects is identified. Create plans to improve processes. The error log and improvements is an ongoing process. Cleaning test environment is done and test machines are restored to the baseline at this time.