definitons Flashcards
Checks if everything works as planned
Testing
Fixes things when they don’t work as planned
Debugging
A fundamental reason for the occurrence of a problem; can be addressed, removed to prevent or reduce frequency of failures or defects
Root cause
Mistake made by a human
Error
An issue identified in the system
Defect
When a defect causes the system to not work as expected
Failure
Defines test objects and selects an approach to achieve them
Test planning
Ongoing checking of all test activities and comparison of actual progress against the plan
Test monitoring and control
Analyzing the test basis to identify testable features, define and prioritize associated test conditions, risks, risk levels
Test analysis
Elaborates test conditions into test cases and other testware
Test design
Creating or acquiring the necessary testware for test execution
Test implementation
Running tests according to the test execution schedule
Test execution
Occurs at project milestones for any unresolved defects, change requests, or product backlog items created
Test completion
Directs coding through test cases; tests are written first, code is written to satisfy tests, and then both are refactored
Test-Driven Development (TDD)
Derives tests from acceptance criteria as part of the system design process; tests are written before the application part is developed to satisfy the tests
Acceptance Test-Driven Development (ATDD)
Expresses desired behavior of an application with test cases written in a simple form of natural language (Given/When/Then format); test cases are automatically translated into executable tests
Behavior-Driven Development (BDD)
Principle of early testing in SDLC; reviewing specifications from a testing perspective, writing test cases before code, using CI/CD for fast feedback and automated component tests, completing static analysis before dynamic testing, performing non-functional testing at component test level
Shift-left approach
Focuses on testing components in isolation
Component testing
Focuses on testing interfaces and interactions between components
Component integration testing
Focuses on overall behavior and capabilities of an entire system or product, including functional and non-functional testing
System testing
Focuses on testing interfaces of the system under test and other systems/services
System integration testing
Focuses on validation and demonstrating readiness for deployment, ensuring the system fulfills user’s business needs
Acceptance testing
Evaluates functions a component/system should perform (what the test object should do)
Functional testing
Evaluates attributes other than functional characteristics (how well system behaves); includes performance, compatibility, usability, reliability, security, maintainability, portability
Non-functional testing
Specification-based testing that checks system’s behavior against its specifications
Black-box testing
Structure-based testing that derives tests from the system’s implementation or internal structure
White-box testing
Confirms that an original defect has been successfully fixed by executing test cases that previously failed due to the defect and adding new tests for any necessary changes.
Confirmation testing
Confirms that no adverse consequences have been caused by a change, including a fix that has already been confirmation tested.
Regression testing
Testing that can be corrective, adaptive to changes in the environment, or aimed at improving performance or maintainability. It includes triggers like modifications, upgrades, migrations, and retirement.
Maintenance testing
Process of defining the scope of review, work product to review, quality characteristics to be evaluated, areas to focus on, exit criteria, standards, etc.
Planning
Ensuring that everyone and everything involved is prepared to start the review process.
Review initiation
Assessing the quality of the work product under review individually, identifying anomalies, recommendations, and questions using review techniques.
Individual review
Process of deciding the status, ownership, and required actions for each anomaly identified during the review.
Communication and analysis
Creating a defect report for every defect found during the review to ensure corrective actions are followed up.
Fixing and reporting
Individual who decides what is to be reviewed and provides necessary resources for the review process.
Manager
Creates and fixes the work product under review.
Author
Ensures the effective running of review meetings during the review process.
Moderator
Collates anomalies from reviewers and records review information.
Scribe
Individual responsible for performing reviews of work products.
Reviewer
Individual who takes overall responsibility for the review process.
Review leader
Review process without a defined process or formal documentation output.
Informal review
Review led by the author to evaluate quality, educate reviewers, gain consensus, and motivate the author.
Walkthrough
Review performed by technically qualified reviewers and led by a moderator to make decisions regarding technical problems.
Technical review
Most formal type of review following a complete generic process with the main objective of finding the maximum number of anomalies.
Inspection
Utilizing the knowledge and experience of testers to effectively implement test cases and detect defects that may be missed by other testing methods.
Experience-based testing
Coverage items are executable statements
Statement testing
Transfer of control between two nodes in the control flow graph
Branch
Coverage items are branches; aim is to design test cases to exercise branches
Branch testing
Technique to anticipate errors based on tester’s knowledge
Error guessing
Simultaneously design, execute, and evaluate tests while learning about the test object
Exploratory testing
Tester designs, implements, and executes tests based on a checklist
Checklist-based testing
Represents a feature valuable to a user or purchaser of a system
User story
Looks ahead to the end of a single iteration; concerned with the iteration backlog
Iteration planning
Looks ahead to the release of a product; defines and re-defines the product backlog
Release planning
Preconditions for undertaking a given activity
Entry criteria
Defines what must be achieved to declare an activity complete
Exit criteria
Pull from data and past experiences
Estimation based on ratios
Pull from past experiences
Extrapolation
Method using experts for estimation
Wideband Delphi
Estimate calculation using optimistic, likely, and pessimistic values
Three-point estimation
Prioritization methods include risk-based, coverage-based, and requirements-based
Test case prioritization
Model showing different granularity levels of tests
Test pyramid
Probability of risk occurrence
Risk likelihood
Consequences of risk occurrence
Risk impact
Include organizational, people, technical, and supplier issues
Project risks
Include user dissatisfaction, revenue loss, trust damage, maintenance costs, criminal penalties, damages
Product risks
