Continuous Testing Foundation flashcards
Continuous Testing Foundation · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Continuous testing
- Executing automated tests continuously throughout the delivery pipeline to provide immediate feedback on business risks, enabling faster and safer releases.
- Shift-left testing
- Moving testing activities earlier in the software lifecycle, such as requirements review and unit testing, to find defects when they are cheaper to fix.
- Test pyramid
- A model recommending many fast unit tests, fewer service/API tests, and very few UI tests to balance speed, cost, and confidence.
- Ice-cream cone anti-pattern
- A testing shape with many manual/UI tests and few unit tests, leading to slow feedback, high maintenance, and brittle test suites.
- Defect escape rate
- The percentage of defects that reach production compared to total defects found; a key metric of test effectiveness.
- Test oracle
- A mechanism or source of truth used to determine whether a test has passed or failed, such as expected outputs or invariants.
- Three amigos
- A collaboration practice where business, development, and testing roles jointly refine acceptance criteria and examples before coding begins.
- Blameless postmortem
- A review after an incident focused on system and process improvements rather than individual blame, feeding into better tests and monitoring.
- Definition of Done
- A shared checklist that includes automated tests passing, code reviewed, and quality gates met before a user story is considered complete.
- Behavior-driven development
- A collaborative approach using plain-language Given-When-Then scenarios to define and automate acceptance criteria, bridging business and technical teams.
- Risk-based testing
- Prioritizing test effort based on the likelihood and impact of potential failures, focusing automation and exploratory testing on high-risk areas.
- Smoke tests
- A fast, critical-path subset of tests run to verify basic functionality before deeper testing or deployment.
- Canary release
- A shift-right technique that deploys a change to a small subset of users to monitor behavior and limit risk before full rollout.
- Service virtualization
- Simulating dependent systems that are unavailable or costly to use, enabling testing of integrations without full environments.
- Flaky test
- A test that produces inconsistent results on repeated runs with the same code, often due to timing, environment, or test design issues.
- Contract testing
- Verifying that a service's requests and responses conform to a shared contract, enabling independent testing of consumer and provider.
- JUnit
- A widely used unit testing framework for Java that integrates with build tools and CI servers to run automated tests.
- Selenium WebDriver
- A browser automation tool for UI testing that drives real browsers and supports multiple programming languages.
- Cucumber
- A BDD tool that executes plain-language scenarios written in Gherkin, linking steps to automation code.
- Pact
- A consumer-driven contract testing tool that records consumer expectations and verifies provider compliance.
- Jenkins
- An open-source automation server used to orchestrate CI/CD pipelines, including test execution and reporting.
- Quality gate
- A set of criteria, such as no critical defects and all smoke tests passing, that must be met before proceeding to the next stage.
- Entry criteria
- Conditions that must be satisfied before testing begins, such as a deployed build, ready environment, and available test data.
- Exit criteria
- Conditions that must be met to conclude a test phase, such as planned tests executed, defects triaged, and quality gates satisfied.
- Traceability matrix
- A document or tool mapping tests to requirements to ensure coverage and support impact analysis when changes occur.
- Page object model
- A UI test design pattern that encapsulates page elements and actions in reusable classes, reducing duplication and brittleness.
- Test double
- A generic term for objects like stubs, mocks, fakes, or spies used to replace real dependencies in tests.
- Hermetic test
- A test that is fully isolated and repeatable, setting up its own data and environment without relying on external state.
- Test impact analysis
- A technique that selects and prioritizes tests affected by code changes, reducing feedback time and resource usage.
- Defect density
- The number of defects per unit of software size, such as per thousand lines of code, used to assess quality.
- Test strategy
- A high-level document defining test levels, types, environments, tools, metrics, and quality gates aligned with business goals.
- Test level
- A stage of testing such as unit, component, integration, system, or acceptance, each with distinct objectives and scope.