Fundamentals of Software Testing Process/ STLC
1.Test Planning:
1.Determine the scope and risks and identify the objectives of testing.
2. Determine the test approach
3. Implement the test policy and/or the test strategy.
4. Determine the required test resources.
5. Schedule test analysis and design task, test implementation, execution
and evaluation.
6. Determine the exit criteria
2. Test Control:
1. Measure and analyse the results of reviews and testing.
2. Monitor and document progress, test coverage and exit criteria.
3. Provide information on testing.
4. Initiate corrective actions.
3. Test Analysis & Design:
1.Review test basis (such as product risk analysis, requirements, architecture, design specs) that help us build our tests.
2. Identify gaps and ambiguities in the specifications.
3. Identify test conditions – high level list of what are we interested in testing.
4. Evaluate test-ability of the requirement and system – ex: if performance of the software is important , that should be specified in a testable way.
5. Design the test environment set-up and identify and required infrastructure and tools.
4. Test Implantation:
1. Develop and prioritize our test cases, using the techniques and create test data.
2. Priority of test cases, decided during test planning should be taken in account.
3. Create test suites from test cases for efficient test execution.
4. Test suite is a logical collection of test cases which naturally work together.
5. Implement and verify the environment – make sure appropriate hardware and
software has been set up.
5. Test Execution:
1. Execute the test suites and individual test cases, this can be done manually or using automated tools.
2. Log the outcome of the test execution and record identities.
3. Logging should be done for each and every test case run for success or failure. This can be use for test analysis.
4. Re-execute tests to confirm fix, also called as re-testing.
6. Evaluating exit criteria and reporting:
1. Evaluating exit criteria is the activity where test execution is assessed against the objectives.
2. This should be done fir each test level
Ex : Exit criteria for unit testing:
a) all unit test cases are executed.
b) No open defects exists in the unit.
3. It’s very important to collect metrics in order to decide the end of the test
4. May require change in test plan ex: addition of resources, addition/deletion of tests.
7. Test Closure:
1. Major activity is to collect data from completed test activities. ( Test results/notes of unexpected events ).
2. Finalize and archive test ware, such as scripts, test environments, and any test infrastructure.
3. Hand over test-ware to the maintenance organisation.
4. Analyse lessons learned for future releases and projects.
Posts
