I - Fundamentals of Testing Flashcards
Objectives of Testing
- to find failures and defects.
- to build confidence in the level of quality of the software.
- to verify whether all specified contractual, legal, or regulatory requirements and user expectations have been fulfilled.
- to provide information to make decisions.
Testing
The process consisting of all lifecycle activities, both static and dynamic to find defects in software and document them.
Debugging
The process of finding, analyzing and removing the causes of failures in software.
Quality Management
includes all activities that direct and control an organization with regard to quality
Quality Assurance (QA)
Defect prevention strategy
Quality Control (QC)
Defect detection strategy
Error
A human action that produces an incorrect result.
Defect
An imperfection or deficiency in a work product where it does not meet its requirements or specifications.
Failure
An event in which a component or system does not perform a required function within specified limits.
Validation
Confirmation by examination and through provision of objective
evidence that specified requirements for an INTENDED USE or APPLICATION have been fulfilled.
Ex. I can successfully click on the different links on a webpage.
Verification
Confirmation by examination and through provision of objective evidence that the specified requirements have been fulfilled.
Ex. There are 5 user options present on the page, as listed in the requirements. (visual confirmation)
Test Process
Planning
Analysis
Design
Implementation
Execution
Completion
(Monitoring & Control)
Test Process Work Products
Planning > Test Plan/Master Test Plan
Analysis > Test Conditions and Defect Report (test basis)
Design > Test Cases, Identification of Test Data, and Design of the Test Environment
Implementation > Test Procedures, Test Suites, and Test Execution Schedule
Execution > ID/Version of Testware, Test Results, and Defect Report (test object)
Completion > Test Report(s)
(Monitoring & Control) > Test Summary Report
Traceability
- makes test coverage measurable
(e. g.: requirements, test condition, exit criteria) - allows analyzing the impact of changes (chapter2)
- making test auditable
- ensures meeting IT governance criteria
- provides information to assess product quality, process capability, and project progress against
business goals - improves understandability progress reports for stakeholders
Test Basis > Test Condition > Test Case > Test Procedure > Test Suite > Test Result
Test Objective
The reason or purpose of testing.
Test Analysis
The activity that identifies test conditions by analyzing the test basis.
Test Basis
The body of knowledge used as the basis for test analysis and design.
Test Condition
A testable aspect of a component or system identified as a basis for testing.
Test Oracle
A source to determine an expected result to compare with the actual result of the system under test.
Test Planning
The activity of establishing or updating a test plan.
Testware
Work products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing.
Traceability Definition
The degree to which a relationship can be established between two or more work products.
Test Case
A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.
Test Design
The activity that derives and specifies test cases from test conditions.
Test Implementation
The activity that prepares the testware needed for test execution based on test analysis and design.
Test Procedure
A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post execution.
Test Suite
A set of test scripts or test procedures to be executed in a specific test run.
Test Execution
The process of running a test on the component or system under test, producing actual result(s).
Test Item
A part of a test object used in the test process.
Test Object
The component or system to be tested.
Test Completion
The activity that makes testware available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders.
Test Control
The activity that develops and applies corrective actions to get a test project on track when it deviates from what was planned.
Test Monitoring
The activity that checks the status of testing activities, identifies any variances from planned or expected, and reports status to stakeholders.
