Software Testing Life Cycle Flashcards
What are the major phases of STLC Model?
- Requirement Analysis
- Test Planning
- Test case development
- Test Environment setup
- Test Execution
- Test Cycle closure
What is Entry and Exit Criteria in STLC?
Entry Criteria = the prerequisite items that must be completed before testing can begin
Exit Criteria = defines the items that must be completed before testing can be concluded
Describe Requirement Analysis
Identify types of tests to be performed.
Gather details about testing priorities and focus.
Prepare Requirement Traceability Matrix (RTM).
Identify test environment details where testing is supposed to be carried out.
Automation feasibility analysis (if required).
Describe Test Planning
Preparation of test plan/strategy document for various types of testing
Test tool selection
Test effort estimation
Resource planning and determining roles and responsibilities.
Training requirement
Describe Test Case Development Phase
Create test cases, automation scripts (if applicable)
Review and baseline test cases and scripts
Create test data (If Test Environment is available)
Describe Test Environment Setup
we decide what browser , is it Chrome , Firefox
are we doing this on tablet, phone, desktop
Understand the required architecture, environment set-up and prepare hardware and software requirement list for the Test Environment.
Setup test Environment and test data
Perform smoke test on the build
Describe Test Execution Phase
Execute tests as per plan
Document test results, and log defects for failed cases
Map defects to test cases in RTM
Retest the Defect fixes
Track the defects to closure
Describe Test Cycle Closure
Evaluate cycle completion criteria based on Time, Test coverage, Cost,Software, Critical Business Objectives, Quality
Prepare test metrics based on the above parameters.
Document the learning out of the project
Prepare Test closure report
Qualitative and quantitative reporting of quality of the work product to the customer.
Test result analysis to find out the defect distribution by type and severity.
What is Requirements Traceability Matrix ( RTM)
a document that maps and traces user requirement with test cases.
It captures all requirements proposed by the client and requirement traceability in a single document, delivered at the conclusion of the Software developement life cycle.
The main purpose is to validate that all requirements are checked via test cases such that no functionality is unchecked during Software testing.
