Software Testing Glossary
Essential terminology for software testing and quality assurance. From test cases to requirements traceability, learn the language of testing.
Not sure where to start?
Pick a theme. Each one groups the core terms and points to a deeper guide when you are ready to put them to work.
Test Planning & Strategy
The decisions you make before anyone runs a test.
Full guide: test management in JiraCoverage & Traceability
Proving what is tested - and finding what is not.
Guide: requirements traceability matrixA
B
E
End-to-End Testing
Testing complete user workflows across the entire application stack from start to finish.
Expected Result
The anticipated outcome of a test case step or the test case as a whole.
Exploratory Testing
An unscripted testing approach where testers actively explore the software using their expertise and intuition.
P
R
S
Smoke Testing
Quick testing of critical functionality to verify the build is stable enough for further testing.
System Integration Testing (SIT)
System Integration Testing (SIT) checks that separately built systems, services and third-party components work together correctly once they are connected.
System Testing
End-to-end testing of the complete, integrated software system against specified requirements.
T
Test Automation
Using software tools to execute tests automatically without manual intervention.
Test Case
A documented set of conditions and steps used to verify that a software feature works as expected.
Test Coverage
A measure of how much of the software or requirements are tested by test cases.
Test Cycle
A test cycle is one round of running a selected set of test cases against a specific build, with assigned testers, a time window, and recorded results - typically one per sprint, release, or test phase such as UAT.
Test Data
The input values, datasets, and environmental data used during test execution.
Test Environment
The hardware, software, network, and configuration setup where tests are executed.
Test Execution
The process of running test cases and recording the actual results.
Test Plan
A document outlining the testing approach, scope, resources, and schedule for a project or release.
Test Report
A document summarizing test execution activities, results, and quality assessment for stakeholders.
Test Scenario
A high-level description of a possible user situation or functionality to be tested.
Test Strategy
A high-level document defining the organization's overall testing approach, standards, and guidelines.
Test Suite
A collection of test cases grouped together for a specific testing purpose.
U
UAT Environment
A UAT environment is the production-like setup where business users run User Acceptance Testing before a release goes live.
Unit Testing
Testing individual functions, methods, or components in isolation from the rest of the system.
User Acceptance Testing (UAT)
User Acceptance Testing (UAT) is the final verification phase where business users - not the QA team - run real-world scenarios against finished software and formally sign off that it is ready for release.
Put Your Knowledge into Practice
Now that you know the terminology, try BesTest for hands-on test management. Create test cases, track requirements, and manage test cycles - all in Jira.
Try BesTest Free