Software Testing Cycle Flashcards
It is also known as Software Testing Process
Software Testing Life Cycle
It defines the various stages / phases / activities in the testing of software
Software Testing Life Cycle
This STLC phase is where you review the business and software requirements and identify any defects in those specifications
Requirements Analysis
This STLC phase is where once you have gathered a general idea of what needs to be tested, you ‘plan’ for the tests.
Test Planning
This STLC phase is where you design / detail your tests on the basis of detailed requirements / design of the software
Test Designing
This STLC phase is where you setup the test environment (server / client / network, etc) with the goal of replicating the end-users’ environment
Test Environment Setup
This STLC phase is where you execute your Test Cases / Scripts in the Test Environment to see whether they pass/
Test Execution
This STLC phase is where you prepare various reports for various stakeholders
Test Reporting and Closure
Work Product for this STLC Phase: ‘Review Defect’ Reports
Requirements Analysis
Work Product for this STLC Phase: Test Plan, Test Estimation, Test Schedule
Test Planning
Work Product for this STLC Phase: Test Cases / Test Scripts / Test Data, Requirements Traceability Matrix
Test Designing
Work Product for this STLC Phase: Test Environment
Test Environment Setup
Work Product for this STLC Phase: Test Results (Incremental), Defect Reports
Test Execution
Work Product for this STLC Phase: Test Results (Final), test Metrics, and Test Closure report
Test Reporting and Closure
The First STLC Phase
Requirements Analysis
The Second STLC Phase
Test Planning
The Third STLC Phase
Test Designing
The Fourth STLC Phase
Test Environment Setup
The Fifth STLC Phase
Test Execution
The Last STLC Phase
Test Reporting and Closure
This Software Testing Principle means that Testing can only reveal defects; it cannot prove that a system is defect-free.
Testing shows the presence of defects, not their absence
This Software Testing Principle means that due to infinite scenarios and paths, testing everything is unfeasible. Prioritization is key.
Exhaustive testing is impossible
This Software Testing Principle means that Catching defects early (e.g., during requirement reviews) prevents costly fixes later.
Early Testing Saves Time and Money
This Software Testing Principle means The Pareto Principle (80-20 rule) applies —- most defects are found in a small portion of the system
Defects cluster together
This Software Testing Principle means Repeating the same tests over time reduces their effectiveness, Tests should evolve with the software
Beware of the Pesticide Paradox
This Software Testing Principle means that Testing strategies must be adapted to the type of software being testes (e.g., games vs safety-critical systems).
Testing is context-dependent
This Software Testing Principle means that a defect-free system is not necessarily useful if it does not meet user expectations.
Absence-of-errors is a fallacy
These are different stages of the software development lifecycle where testing is conducted
Software Testing Levels
A level of the software testing process where individual units of a software are tested.
Unit Testing
The purpose of this level is to validate that each unit of the software performs as designed
Unit Testing
A level of the software testing process where individual units are combined and tested as group
Integration Testing
The purpose of this level of testing to expose faults in the interaction between integrated units.
Integration Testing
A level of the software testing process where a complete, integrated system is tested.
System Testing
The purpose of this level is to evaluate the system’s compliance with the specified requirements
System Testing
A level of the software testing process where a system is tested for acceptability
Acceptance Testing
The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery.
Acceptance Testing
It is a separate level of Software Testing Levels that is just a type of testing that can be performed at any of the four main levels
Regression Testing
WHEN to test
Level
HOW to test
Method
WHAT to test
Type
