Reviews and Testing Flashcards
An evaluation of a life-cycle work product(s) or project status to determine if there are any deviations from planned results and to recommend improvement.
Review
Any condition that deviates from expectations based on requirements specifications, design documents, standards, plans, and so on, or from someone’s experiences.
Anomaly (defect)
A formal evaluation of a project-level plan or project progress relative to that plan by a designated review team.
Management review
Milestones might be linked to customer involvement and even contract payments such as in the defense world of conducting PDRs and CDRs.
What does PDR stand for?
Preliminary Design Review
Milestones might be linked to customer involvement and even contract payments such as in the defense world of conducting PDRs and CDRs.
What does CDR stand for?
Critical Design Review
An informal verification technique in which the life-cycle work product is examined by the author and one other person.
Buddy check
A formal team evaluation of a life-cycle work product to:
- Identify any discrepancies from specifications and standards.
- Determine its suitability for use.
- Provide recommendations after the examination of various alternatives.
Technical review
Technical reviews are typically used for the classic design reviews such as PDRs, CDRs, and TRRs.
What does TRR stand for?
Test Readiness Review
A formal verification technique in which life-cycle work products are examined in detail by a group of peers for the explicit purpose of detecting and identifying defects.
Inspection
A quality control function in that it is used to verify the functionality and performance of life-cycle work products or product components as they move through the product life cycle.
Testing
___ testing is a process of testing the individual components, subsystems, hardware components such as programmable logic arrays, and software components such as subprograms, subroutines, or procedures.
Unit
The objective of ___ testing is to test component interfaces and confirm that the components meet the interface requirements and that the components can indeed be assembled.
integration
___ testing is the first time at which the entire system can be tested against the system requirements specifications.
Systems
The purpose of ___ testing is to confirm that a system is ready for operational use and that the confidence built up in systems testing is justified.
acceptance
___ testing is the execution of a series of tests to check that modifications to parts of an existing system will not negatively affect other working components or sybsystems.
Regression
The process of finding areas of a program not exercised by a set of test cases, creating additional test cases to increase coverage, and determining a quantitative measure of code coverage that serves an indirect measure of quality.
Test coverage analysis
___ coverage measures whether each executable statement is encountered.
Statement
___ coverage measures whether Boolean expressions tested in control structures are evaluated to both true and false.
Decision
___ coverage measures the true or false outcome of each Boolean subexpression.
Condition
___ coverage measures whether every possible combination of Boolean subexpression occurs.
Multiple condition
___ coverage measures whether each of the possible paths in each function has been followed.
Path
Test case design technique. Tests that exercise all decision point outcomes at least once, and ensure that all statements or entry points are executed at least once.
Logic coverage
Test case design technique. Defines condition or error classes to help reduce the number of finite tests. Assumes that a test of a representative value within a class also tests all values or conditions within that class.
Equivalence partitioning
Test case design technique. Tests each edge condition of an equivalence class; also considers output equivalence classes as well as input classes.
Boundary value analysis