Software testing is ongoing activity within software development life cycle. Software testing life cycle gives brief idea about requirement, plan, schedule, execution and report etc. Activities are in Software Testing Life Cycle as
Test Verification and construction
Report and Rework
In Software Testing Life Cycle (STLC) analyze and study the requirements for testing the specified functions.
The Quality Assurance (QA) panel may interact with different stakeholders (Client, Business Analyst, Technical Leads, and System Architects etc) to understand the functional and non functional requirements in detail.
STLC requirement phase helps to identify the scope of the testing. If any feature is not testable, communicate it during this phase so that the mitigation strategy can be planned and check feasibility for the given testing project.
Test plan plays an important role in achieving a process orientated approach using predetermined plan well in advance to reduce the further risks.
Once the requirements of the project are confirmed a test plan is documented as
Objective, task and scope
Roles and Responsibility
Features to be tested and not
Risk and Contingency
Tools to be used
Identify the test conditions through the requirements document, product risks and test plan.
Analyze what type of software testing should be carried out at the various stages of software development life cycle and software testing life cycle.
Test planning defines “what to be tested”.
Test design based on the requirement of the project documented in Software Requirement Specification (SRS).
Test design defines “How to test”.
Design test conditions, break condition into multiple sub conditions and increase coverage.
Test Verification and Construction-:
Verify the entire requirement based on project documented Software Requirement Specification (SRS).
Execute various test cases designed for various stages of functionality of SDLC.
Analyze the result and make sure that your entry and exist criterion is met.
Fill your traceability metrics to track your progress in not meet to criteria.
A Bug or defect profile document has to be updated for letting the developers know about bug. Bug profile document contains
Test case id
Classification of bug (Critical, high, medium and low)
Report and Rework-:
Reported bug fix and rework by the development team and undergo testing process again to assure that the bug found is resolved.
Creating plans for improvement and enhancement is on ongoing process after implementation also.