Call to Test

Owned by Anubhuti Shrivastava
Last updated: Oct 10, 2024 by Dominik Trygar
3 min read

Starting October 11, 2024 (Zephyr Enterprise 8.2), the Zephyr Enterprise documentation moved from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise documentation page. Please see: Call to Test | Zephyr Enterprise Documentation

Adopting a modular test-case design approach is one effective way to boost reusability for large-scale test-case libraries. Instead of duplicating or copying and pasting test cases or steps, this approach emphasizes that you break them down into small, reusable pieces and then recombine the tests to achieve larger end-to-end testing scenarios.

While modularization is a bit more complex, it can lead to even greater testing efficiencies and results when used appropriately.

The most valuable test cases are broadly applicable and reusable across different cycles and releases. Test engineers should devote serious thought to how to design test cases to be as specific as they need to be but also generic enough to be reused in different situations with different data inputs.

Testers can break down test cases into logical, manageable functions or modules. These modules are isolated to create independent tests that can then be recombined or reused to make larger test cases to achieve complex end-to-end testing scenarios. Zephyr Enterprise gives you the ability to nest child modules under main test cases, even with multiple levels.

Reusing Test Cases with Call to Test

  • From the Test Step section of any test case, click Call to Test to reuse existing test cases.

2024-03-20_15-48-11.png

  • Browse and select the desired test cases, then click Add.

2024-03-20_16-11-31.png

  • The “Call to test” can only use the test case from the current release.

  • The test cases appear in a special step type called Call to Test.

  • we show the TestcaseID(Version) Name of the Testcase

  • TestcaseID(Version) is clickable and can navigate to the source test case

  • The reusable steps appear in the expanded step view.

Version Concept

  • Calls to test are links to the source test case. If you make changes to the source test, then the version of the source test case will increase.

  • Users need to sync the “Call To Test” to bring the changes done on the source test case.

Test Execution

  • In Test Execution when the User plans the Test case for the execution it will show each test step as an individual step

  • Each step from the “call to test” will have the [Test Case ID (Version)]

  • [Test Case ID (Version)] is clickable and been navigated has to the source test case.

Administration

  • Users can configure the Maximum nested level of Call to Tests in a test case by default 3.