Qa Glossary
Browse 18 qa terms defined in plain English, from the cultural dictionary of computing.
18 Qa Terms
- Bug Bash
- A concentrated team event where engineers, designers, PMs, and testers actively try to find defects in a feature or release candidate before launch. It is as...
- Bug Report
- A report describing a software defect, usually including observed behavior, expected behavior, environment details, reproduction steps, and supporting evidence...
- E2E Testing
- End-to-end (E2E) testing validates the entire application stack by simulating real user interactions from the UI through backend services to the database and...
- Integration Testing
- Integration testing verifies that separate components or services work correctly when connected together, catching bugs that emerge only from interactions...
- No Repro
- Short for 'no reproduction,' meaning a reported bug could not be made to occur again in the current test environment. It often signals an environment mismatch,...
- Regression Test
- A test specifically written or retained to verify that a previously fixed bug does not reappear — or more broadly, that new changes have not broken existing...
- Software Testing
- The practice of executing software under controlled conditions to verify that it behaves as expected and to discover defects. Encompasses multiple levels —...
- Staging Environment
- A pre-production environment that mirrors the production infrastructure as closely as possible — same services, configuration, and (ideally) anonymized...
- System Test
- An end-to-end test that validates the complete, integrated system against its specified requirements — exercising the full stack including UI, APIs, databases,...
- Test Assertion
- A statement within a test that declares an expected condition — such as assertEquals(actual, expected) or expect(result).toBe(true) — which either passes...
- Test Case
- A single, self-contained specification of inputs, execution steps, and expected outcomes designed to verify one specific behavior or requirement of the system...
- Test Data
- Predefined or generated input values, database records, and fixture files used to exercise a system during testing — crafted to cover typical scenarios, edge...
- Test Harness
- The infrastructure code that surrounds and drives a test suite — handling test discovery, execution orchestration, environment setup and teardown, result...
- Testing Pyramid
- A testing strategy model shaped like a pyramid: a broad base of fast, cheap unit tests, a middle layer of integration tests, and a narrow top of slow,...
- Test Plan
- A document that specifies the scope, approach, resources, schedule, and pass/fail criteria for testing a particular feature or release, serving as the contract...
- Test Strategy
- A high-level document or decision framework that defines which types of testing (unit, integration, E2E, performance, etc.) a project will employ, the ratio...
- Test Suite
- A collection of related test cases grouped together, typically organized by feature, module, or test type, that can be executed as a single unit by a test...
- Unreproducible Bug
- A bug that is known to exist from reports or evidence but cannot be consistently reproduced on demand, making diagnosis and fix validation difficult. These...
Related Topics
- Testing (13 terms in common)
- Ci/Cd (3 terms in common)
- Debugging (2 terms in common)
- Automation (2 terms in common)
- Architecture (2 terms in common)
- Unit Testing (2 terms in common)
- Bug Reports (1 terms in common)
- Issues (1 terms in common)
- Fixtures (1 terms in common)
- Deployment (1 terms in common)
- Integration (1 terms in common)
- Intermittent Failures (1 terms in common)
- Release Process (1 terms in common)
- Team Rituals (1 terms in common)
- Reliability (1 terms in common)
- Maintenance (1 terms in common)
- Documentation (1 terms in common)
- Devops (1 terms in common)