February 2020
...
Category | Feature | Description | Trello Board link |
---|---|---|---|
Enterprise Admin & Scaling | Ability to give read-only permission to Zephyr | Added the ability to give certain users read-only permissions to the Test Repository and Global Repository. This restricts the ability to create, modify, and delete records, while still allowing team members to review test assets. | Link |
SSO Improvements | Improved SSO support on two areas:
| Link | |
LDAP Improvements | Improved LDAP support on two areas:
| Link | |
Added full API token management for Zephyr, including:
| Link | ||
Audit Log Improvements | Improved the Audit Log to include more audited events, and redesigned the audit log page which may now be accessed from the About Zephyr page. | Link | |
Automation | Improved zBot installation & setup | Refactored the zBot architecture to achieve a few goals:
| Link |
Customizable Parser | Re-architected the Zephyr automation parsers to achieve three goals:
| Link | |
Usability | Ability to copy or move an entire folder from one Test Cycle to another | Added the ability to copy or move a Test Cycle Folder from one Test Cycle to another Test Cycle, making it significantly easier to re-use test cases across different Test Cycles. | Link |
Improved Jira Defect filing | Improved the Jira Defect Filing page on two areas:
| Link | |
Email Notifications | Added a brand new feature for email notifications, including email notifications for two use-cases:
| Link | |
User Experience (UX) update | Kicked-off a User Experience revamp for Zephyr, including a major UI overhaul to update the color scheme and fix alignments, and several UX improvements throughout the application for a better experience. | Link |
...
Type of Enhancement | Description |
---|---|
OpenJDK support for zBots | This has simplified zBot installation, avoiding the need for end-users to install Oracle Java on their computers. |
This allows Admins to disable specific users (and free up their license usage) directly from the Zephyr UI. | |
Updated behavior when a user edits and creates a new version of a test case that has already been executed (or partially executed). In earlier versions of Zephyr, the execution status would remain unchanged for the new version creating confusion. In version 6.6, upon creating a new version, the user will have an option to maintain the execution status or to reset the status to Unexecuted. | |
Cap application log files | Zephyr logs are now capped every 24 hours, creating new files for each day for easier debugging and cleaning up old log data. |
Installer improvements | Improved security with password masking, encryption for DB password, and license simplification (only a single license is needed for all of Zephyr). |
Upgrader improvements | Fixed an issue where the Tomcat temp folder was filled with .gz files, consuming a large amount of hard drive space. |
By default, Zephyr will now create remote links in Jira when test cases are mapped to requirements, which is the expected behavior. | |
Added Tag Column Option for Grids | Added the option to include a ‘Tag’ column for all grid views for the Test Repository, Global Test Repository, and Text Execution for easier sorting by tags. |
Small update to remove the ‘D’ button (to file a defect) when the test case has passed, avoiding user confusion. | |
Test Execution grid count | Fixed an issue where the test cases in the Test Execution grid were being counted by the number of defects associated to them. |
Fixed an issue where any updates made to the test case execution status to and from “Not Executed” were not being recorded and reflected in the Execution History for the test case. |
...
Upgrading to 6.6
For more information on upgrading, please refer to Upgrading Zephyr Enterprise.
...