Software Testing Life cycle

SOFTWARE TESTING LIFE CYCLE:-

Software Testing Life cycle is nothing but a sequence of activities done for testing software.

STLC is a series of activities carried out methodologically to help certify your software product. There are steps carried out to make the product bug free.

REQUIREMENT ANALYSIS

During this requirement analysis phase testers gather the requirement document. Tester goes through the document and discuss with the stakeholders if any question arises. In this phase what type of testing needs to be carried out is decided and Identifying test environment where testing is supposed to be carried out.

TESTPLAN

In this stage, effort and cost estimates for the project are to determine and would prepare and finalize the Test Plan. In this phase, Test Strategy is also determined. In his stage, the test plan/strategy document for various types of testing is prepared. Testing tools selection is done and effort for testing is estimated. The number of resources required and their roles and responsibilities is determined.

        TEST CASE DEVELOPMENT

In this phase test case is developed, test data is verified and rework on test case is done. Test data, is identified/created and is reviewed and then reworked as well in this phase.

This phase involves creating the test case and automation scripts. Reviewing the test case and scripts. Create test data which can be used for testing.

TEST ENVIRONMENT SETUP:-

Test environment decides the software and hardware conditions under which a work product is tested. Test environment set-up is one of the critical aspects of testing process and can be done in parallel with Test Case Development Stage. Test team may not be involved in this activity if the customer/development team provides the test environment in which case the test team is required to do a readiness check (smoke testing) of the given environment.

TEST EXECUTION:-

During this phase, the testers will carry out the testing based on the test plans and the test cases prepared. Bugs will be reported back to the development team for correction and retesting will be performed.

TEST CYCLE CLOUSER:-

Testing team will meet, discuss and analyze testing artifacts to identify strategies that have to be implemented in the future, taking lessons from the current test cycle. The idea is to remove the process bottlenecks for future test cycles and share best practices for any similar projects in the future.