Phases in Software testing life cycle will be listed below. This cycle later phases will get
changed based on traditional development life cycle and latest agile
methodology or Scrum framework.
Requirement Analysis:
This phase deals with analysing the requirements through SRS(System requirement) and BRS(Business requirement) documents. Traditional SDLC like Waterfall, Prototype and spiral will have late testing is due to this that we will cover on principles of testing. Analysing the requirements at later stage and identifying the requirement issues at later stage will cause major impacts to the application in sense of business. Outcome of requirement analysis phase is Strategy document.
This phase deals with analysing the requirements through SRS(System requirement) and BRS(Business requirement) documents. Traditional SDLC like Waterfall, Prototype and spiral will have late testing is due to this that we will cover on principles of testing. Analysing the requirements at later stage and identifying the requirement issues at later stage will cause major impacts to the application in sense of business. Outcome of requirement analysis phase is Strategy document.
Test Strategy
Document - Test Manager – Static
Document
1.
Business priorities
2.
Risk and its mitigation
5.
Process of test execution
7.
Training needed or not
Test
Planning:
Test Plan Document
- Test Manager/ Test lead – Dynamic document
It will
change throughout the testing lifecycle and also it will answers the below questions
with planning.
1. When- When the testing for the feature or module is going to be performed?
2. What - What are the expectation in the functionality or feature?
3. Where - Where refers the test environment includes os and browser.
4.
How - How means the approach or type of testing going to be performed for that feature.
5. Who -Who means the resource person going to execute the specific feature or functionality as per plan.
Test Case
Development:
1.
Preparing test cases
2.
Test data Preparation
Environment
Setup:
1.
Test case review - Review the prepared test cases and ensure with the team that the scope is covered in the test case.
2.
Updating of test cases based on the feedback received from the peers.
Test
Execution:
1.
Executing the test cases and identifying potential
bugs
2.
Assigning bugs to appropriate developers and follow-up
for its closure
3.
For Agile, It will happen in parallel cycles in every
build
Test Cycle
Closure:
1.
Preparing the test report
2.
Sent it to appropriate distribution list daily, weekly
or bi weekly manner.
