Table 1. A-D



Ad-hoc cycle

If no Test Cycles have been set up for a Version, then any test which gets executed is reported against an "ad-hoc" cycle. This is the default cycle.

Ad-hoc test execution

If a test is being executed outside of a test cycle, then it is termed to be executed in an ad-hoc fashion.


Attachments allow users to associate files or documents with test cases, issues, or other test-related entities. These attachments can include screenshots, log files, documents, or any other relevant artifacts that provide additional context or information for testers or stakeholders.

Behavior-Driven Development (BDD)

Behavior-driven development is a software development methodology that combines technical aspects and business interests. It implies that the team decides what to test and to what extent and creates test scenarios in a simple language (like Gherkin) that is understandable by even non-technical-savvy employees.


You can make duplicates of several different types of entities within your instance. You can clone test cases, test steps, and more.

Cloning a Test Case

Cloning a Test Case involves creating an exact copy of an existing test case. This allows testers to reuse or modify an existing test case as a starting point for creating new test cases with similar characteristics or requirements, saving time and effort in test case creation.

Custom Field

A non-standard field the user creates in order to meet specific needs. Custom Field Types have their own glossary.


The Component/s set up in Jira for that project.

Cycle Summary

A grouping of executed or unexecuted tests (e.g. "Functionality", "Regression" etc.). More than one test cycle can exist for a Version.

Cloud instance

A cloud app is a web-based solution hosted by SmartBear. Cloud-based solution means the move of your data to the cloud so that you can access your data remotely. This solution makes data storage convenient for you. In this case, we store the data on our side. You can also utilize the advantage of automatic updates to an app. You pay a monthly subscription fee and you receive support from our technical support team.

Table 2. E-K




When a test is run and its result or status is recorded. Executions refer to the process of actually running or performing test cases in Zephyr Squad. Testers execute test cases to verify the functionality and behavior of an application or system. Executions can be logged and tracked within the system to monitor progress and capture test results.

Execution statuses

Pass, Fail, Blocked, WIP (Work In Progress), and Unexecuted are default statuses. Custom statuses can be added.


Addons that allow you to view testing-specific metrics. You can add gadgets to Zephyr Squad using the Gadget Directory.


A plain-text language that uses some keywords to organize descriptions into scenarios, test steps and other blocks.


In Zephyr, issues refer to problems or concerns encountered during the testing process. These can include defects, bugs, or any other obstacles that impact the progress or quality of testing.

Import data

The import data functionality allows users to bulk import test-related data, such as test cases, test execution results, or other test management information, into the system. This feature helps to streamline the process of migrating or updating large amounts of data.

Index recovery

Index recovery is the process of restoring or recovering the search index in case of any index-related issues or data loss. It involves recovering the index files and ensuring that the search functionality is fully operational.

Table 3. L-O




User generated Labels

Migration logs

Migration logs are records or logs generated during the process of migrating data from one system or version to another in Zephyr Squad. These logs capture details about the data migration process, such as the status of each migrated item, any errors or warnings encountered, and other relevant information for tracking and troubleshooting purposes.

Mapping files

Mapping files are used to establish relationships or connections between different data sets or systems. These files define how data from one source should be mapped or aligned with data in another system or format, ensuring that information is accurately transferred or synchronized during data migrations, integrations, or other data-related operations.

Migration method

Migration method refers to the approach or technique used to transfer data from one system or environment to another in Zephyr Squad . It can involve various methods such as manual data entry, bulk imports, data integrations, or using specialized migration tools or APIs.

Table 4. P-S




Reindexing is the process of rebuilding the search index for improved search performance and accuracy. When executed, it updates and organizes the index to ensure that search queries deliver relevant and up-to-date results.


Simulation of user actions that are executed through special commands contained in tests.

Test case

This is a detailed step-by-step description of what should be done to test something.This can be as high level or detailed as possible, with links to requirements, lots of properties, execution history etc. In Jira, its a standard issue-type.

Test cases in Zephyr Scale are entities that are stored on the Scale side which prevents additional load on Jira and does not influence the Jira performance.

Test Issue Type

Test Issue Type is a categorization or classification of issues in Zephyr Squad. It helps to organize and track different types of problems or concerns that may arise during testing, such as functional issues, performance issues, usability issues, etc.

Test Execution Status

Test Execution Status indicates the current state or outcome of a test case execution. It can include statuses such as Pass, Fail, Blocked, Not Run, or other custom statuses defined by the testing team. Tracking test execution status helps in monitoring progress and identifying the overall quality of the testing effort.

Test Metrics

Test Metrics are quantitative measurements or indicators that provide insights into the testing process and its effectiveness. These metrics can include test coverage, test execution progress, defect density, defect trends, and other key performance indicators (KPIs) that help evaluate the quality and efficiency of the testing activities.

Test Execution Result

When you execute a test case, the app generates and stores a set of information called the Test Execution Result. This information includes details such as the tester who performed the execution, the date of execution, any defects found, the testing environment, and the status of the execution (pass or fail).

Test Summary

High-level summary and counts of all the tests that have been created in a particular project, grouped in various ways.

Accessible in a Jira project via the navigation tab on the left.

Test Steps

Test Steps are individual actions or instructions that need to be performed to execute a specific test case. In Zephyr Squad, test steps can be defined and associated with test cases to provide detailed guidance for testers during the execution phase.


The ability to trace linkages from requirements all the way to defects or vice versa.


The Test issue-type has the default issue workflow.


A simple structured query language that allows you to string together the right fields to search using specific values with the appropriate operators and keywords.

Publication date: