Software testing is a critical part of software development that ensures the quality, reliability, and functionality delivered meets technical and customer requirements.
That’s why it’s essential every member of a Quality Assurance team is on the same page when discussing key testing terms and TestMonitor-specific features.
Here’s a glossary of the most common and important terms all QA professionals should know. We encourage you to expand and refine this list to meet your unique testing needs.
The final stage of testing where the software is validated against predefined requirements to confirm that it meets the acceptance criteria for release.
An error or flaw in the software that causes it to produce incorrect results or behave unexpectedly.
A term referring to any flaw or imperfection in the software that requires fixing.
The desired outcome or behavior of the software when executed under specific conditions.
Problems or concerns identified during testing that need further review or resolution.
Criteria or requirements that must be met before running a test case.
Testing focused on verifying that the software meets specified functional and non-functional requirements.
Statements that describe what the software should do.
A testing approach used to identify and mitigate potential risks to a piece of software during development and deployment.
Potential threats or vulnerabilities that could negatively impact the software as developed, as it is used, or its users.
Pre-defined procedures or steps used by testers to verify specific aspects of the software's functionality or behavior work as expected.
The setup where tests are executed, including the hardware, software, and configurations. Different test environments can be used to test different elements of software.
The process of performing the test cases against the software to evaluate its behavior.
Outcomes or observations obtained from executing test cases.
Instances of tests executed on the software.
A person responsible for planning, executing, and reporting test activities.
The person responsible for a particular task or issue in TestMonitor.
TestMonitor's feature for recording, tracking, and resolving software bugs or defects.
A report in TestMonitor showing the extent of test case coverage across the software’s different key elements, such as security, functionality, or performance.
TestMonitor's ability to connect with other tools and systems used in software development, defect tracking, project management, or other testing scenarios.
TestMonitor's feature for managing and tracking software issues or defects found during testing.
Significant points in the project timeline used to track progress and completion status against a defined schedule.
A summary of project progress and status at specific milestones within TestMonitor.
In TestMonitor, the result of a completed test execution (e.g., passed, failed, blocked).
TestMonitor's visual representation of project data and metrics to aid in communicating status or sharing results.
An overview of key metrics and information related to the entire software project in TestMonitor.
The overall software development effort that is being managed in TestMonitor.
The ability to re-execute a previous test run in TestMonitor.
TestMonitor's functionality for managing and organizing project requirements.
The ability to track and manage risks associated with the software development process in TestMonitor.
Detailed steps provided in TestMonitor written for testers, used for executing specific test cases.
A metric in TestMonitor representing the amount of work assigned to testers within a specified timeframe.
A type of report in TestMonitor that shows the relationship between test cases and requirements or risks.
Predefined structures or formats available in TestMonitor for creating consistent test cases, test runs, requirements or milestones.