Frequently Asked Questions

Test plans provide a high-level view of your entire test initiative. You can customize test plan fields to track scope, risks, strategy, pass/fail criteria, test bed, and other things. Associate test cycles with a test plan to better track test executions. There are also several reports you can filter by test plan, which aggregate all stats/results from the child test cycles linked to the test plan. You aren’t required to use test plans with Zephyr Scale, but they are incredibly useful if you choose to do so.

Yes, Zephyr Scale is tightly integrated with Jira, so you can link test cases, test cycles, and test plans to any issue type in Jira. Zephyr Scale also offers traceability reports to track traceability and coverage.

Yes, basic versioning functionality is available for test cases. Version control is enabled by default and allows teams to collaborate and manage multiple versions of test cases in parallel while maintaining data integrity and providing an audit history of changes. Versions can easily be viewed and compared for audit purposes.

Definitely. The order of test cases within a test cycle can be set from the Cycles view. Just drag and drop test cases into whatever order you prefer, and this order is reflected in the Test Player. Zephyr Scale does not currently support the "test suite/set" functionality, which allows you to organize groups of test cases outside of a test cycle, though you can use folders to organize your test cases.

Yes, Zephyr Scale supports call-to-test. Instead of duplicating or copying/pasting test cases or steps, break them down into smaller, reusable pieces to construct new tests and achieve larger end-to-end testing scenarios. That way, test cases can be referenced (or called) into other test cases to enhance reuse.

Yes, Zephyr Scale supports parameters within test cases.

Yes, with Zephyr Scale, small and agile teams can manage testing in a lightweight and straightforward fashion. You can create and link test cases or acceptance tests to user stories/bugs and create test cycles directly from the Jira issue or the Kanban board.

Yes, Zephyr Scale supports test data to be used within test cases.

Yes, Zephyr Scale supports BDD type test cases.

With our REST API, which is free when you install Zephyr Scale, you can access testing data from Jira and carry out a variety of useful tasks, such as migrating from another tool by importing your data, integrating with automated testing tools, and more. By using the API, you can publish automated test-execution results to Zephyr Scale and use our powerful reporting to view metrics on your entire testing process. The API is HTTP-based and can be used from any framework, programming language, or tool.

Absolutely! Zephyr Scale supports custom fields for test cases, test cycles, test plans, test steps and test executions.

Yes, Zephyr Scale Server/Data Center offers a range of cross-project reporting (72 out of the box!). There are also a few legacy reports that will eventually be redeveloped for the new reporting suite. Custom reports are not supported at this time.

Yes! Check out the documentation for more information.

Yes, you can import test cases from Microsoft Excel, CSV files, and more using the importing wizard. See Importing Test Cases for a full list of available import options.

Yes, Zephyr Scale Server/Data Center supports various JQL functions.

We currently do not have any plans to move to Atlassian Forge.

Atlassian requires that you purchase the same license level for apps as you have for your base product. Here’s the explanation. There is, unfortunately, no way to purchase a lower license tier for apps at this time.

You can get a free 30-day trial from Atlassian Marketplace. This period can only be extended by Atlassian, for another 7 days.

Zephyr Scale is not SOC 2 compliant, however, we are participating in and compliant with the following programs owned by Atlassian:

• Marketplace Security Bug Bounty Program
• Security Self-Assessment Program
• Cloud Fortified apps program

We currently don’t conduct external audits of the app.

As we are compliant with the Atlassian Security Program, a self-assessment is updated and sent to Atlassian every year. This is a company-wide assessment, not a per-product assessment.

Yes, more information is available on request.

We are enrolled in the Bug Bounty program run by Bugcrowd as part of the Atlassian “Vendor Security Assessment” program. As part of the program security, researchers pentest our application and report back all security vulnerabilities, and we fix all the identified vulnerabilities as per the SLA’s setup by Atlassian for the program. If we continue to meet the requirements of the vendor security assessment program, Atlassian confers a security badge on the app in the marketplace.

SmartBear has an Information Security Policy. The ISMS is aligned with NIST CSF and CIS Controls. Please see IS 000 – Information Security Policy. Our privacy policy can be accessed on our website at smartbear.com/privacy.

We don’t have any security relevant certificates yet.

Anonymous data is collected and processed by third-party applications:

• Sentry – error-tracking and performance-monitoring

• Segment – product usage data aggregation platform

• Amplitude – product usage data analytics platform

No personal data is collected and processed by these tools.

Example of the data processed includes:

No, although we closely monitor the performance of our production systems and act to maintain and improve it accordingly.