Skip to main content
Skip table of contents

Key Terminology

To effectively use AgileTest, it is essential to understand the following key terminology:

1. Requirements

A requirement refers to a specific statement or condition that defines what a product, system, or service must achieve or possess to meet the needs of stakeholders. Requirements serve as guidelines and constraints that shape the design, development, and implementation of the project.

2. Precondition

A precondition refers to a set of conditions or requirements that must be met before a test case can be executed. Preconditions establish the necessary environment or initial state in which the test case can be run effectively and reliably.

Preconditions help ensure that the system or software being tested is in a known and stable state before executing specific test scenarios. They set the context or prerequisites for the test case to yield accurate and meaningful results. By defining preconditions, testers can control the starting conditions and dependencies necessary for the test case to function as intended.

3. Test Case

A test case is a detailed set of steps or actions that define how a specific functionality or requirement will be tested. Test cases contain pre-defined expected results and serve as a basis for executing and validating software behavior.

4. Test Plan

A test plan is a high-level document that outlines the testing objectives, scope, and approach for a specific project or release. It provides a roadmap for the testing activities and helps teams organize their testing efforts.

5. Test Execution

Test execution refers to the process of running test cases and documenting the actual results. Testers execute the test cases and update the status (pass, fail, blocker, etc) along with any relevant observations or defects encountered during the testing process.

6. Defect

A defect, also known as a bug or issue, represents an unexpected behavior or deviation from the expected results. Defects are logged when a test case fails, and they are tracked, prioritized, and resolved through the issue tracking capabilities of Jira.

Understanding these key terms will help you navigate and utilize AgileTest effectively for your software testing needs.



Should you need any assistance or further AgileTest inquiries, contact here!

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.