Key Concepts
The table below outlines key terms used throughout the AgileTest documentation and interface. Review this glossary to familiarize yourself with essential concepts, and click the links for detailed explanations on each topic.
Concepts
Concept | Description | Also known in the Testing community as |
|---|---|---|
A structured set of steps can be manual or automated, used to verify a requirement or functionality. | Test Case, Test Scenario | |
A single test action, each has a defined action, sample data, and expected results of the manual test case. | Test Step | |
A clear and measurable goal explains how the system should behave and its purpose. | - | |
Initial conditions must be assured before the execution of the Test's steps. | - | |
A group of test cases, requirements, or preconditions that are organized in a structured approach. | - | |
A time-based plan, which is used to organize test cases and create executions within your project. | - | |
A specific run of a list of test cases, along with the status and results. | Test Cycle, Test Run | |
A checklist with less detailed test items for quick checking or verifying the daily checkup. | Checklist | |
An unscripted test approach where testers explore the application to find defects, relying on their knowledge and experience. | - | |
An issue or problem found during testing, which may be linked to a specific feature, epic, or story. | Defect, Bug, Error |
References
Should you need any assistance or further AgileTest inquiries, contact our 24/7 Support Desk!