...
...
...
...
...
...
...
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
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: https://support.smartbear.com/zephyr-enterprise/docs/en/zephyr-enterprise/zephyr-user-guide/test-repository/call-to-test.html |
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.
...
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
...
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.
...