Additional Zephyr features
we are considering moving our test plans to Zephyr from another testing application. In preparation for this step, we are trying to identify a set of features in Zephyr that could make such a migration easy. Can I therefore ask you for help in answering the question if the following features are currently available in Zephyr ?
- Test case: Automation - This field describes whether the test case is currently automated and in which framework. This is mainly used to measure how much of our testing is automated
- Test case: results history - A very useful feature. You can view a history of all the test cases that appeared in any test plan, when they were executed and what results were recorded against that test plan, with a clickable link to the test plan.
- Creating a Test Plan - 4th Test Plan: Types (Release, Component, Network) - another application allows us to create a Release test plan for Release regression tests. We can also create test plans of Component or Network type.
- Test Plan: Linking related test plans - another application allows us to pull related test plans into the Release test plan. Example: Master Test Plan.
- Test Plan: Results Page - Another application's test plan consists of several pages. The results page is used to record the results of test case execution. The results can be completed automatically by automation (a third-party application automation package or other framework that uses the application API to update the results) or manually by an SQE engineer. The result can be pending, autopass, autofail, pass, fail, skip or NA.
- Test Plan: Results page: Update Results - Test case permutation results on the results page can be updated either by directly modifying fields such as recipient, score, description, etc. or by mass editing by selecting multiple permutations and changing them all at once.
- Test Plan: Results Page: Results Activity - In another application, you can not only store the results of a test execution, but also view a history of how the results have changed over time, like an audit trail.
- Automation - Automation sets can be created directly in another application based on the automation scripts and arguments listed in each permutation of the test case. These automations can be run in full or in part and can update the results in the test plan if so desired. Similar results can be achieved using Jenkins with Zephyr.
- Automation: Results List - The Results List page for each automation package lists all historical automation runs, with a complete list of all scripts, their execution results, and logs for debugging purposes. This historical data is very useful.
- Automation: Results List: Select failed scripts for restart - After running an automation package, when some test cases fail, another application provides a cool feature that allows you to simply press a button and select only failed cases for restart. This is very useful for large automation packages that contain many scripts. Otherwise, manually selecting failed scripts is very cumbersome.
- Automation Metrics - Automation metrics pages in another application provide metrics on how many permutations of test cases have been automated at the network and component level.
- Search bar - another application has a very powerful search bar where you can type in any text and then all matching search results for Test Cases, Test Plans, Automations, Releases, etc. are displayed.