Zephyr Enterprise Erfahrungen

It allowed the entire project team to work together on all aspects of their testing within the context of their specific software releases, while keeping a global view.
Using structured and freeform test execution cycles, and the ability to run manual or kick-off automated tests in the automation tool of our choice allowed greater scalability.
All the results get updated in real time to dashboards for senior management to review. All testing assets, across all products, projects, releases and sprints all in one place. Standardize on tests, data, metrics, processes, executions, documents, reports etc. Able to re-purpose and reuse which saved time and increased productivity.
We required a test management application that would seamlessly integrate with our other business critical tools e.g. JIRA, Confluence, Eggplant, Ready API, Test Complete, Selenium, Jenkins etc

There were some bugs found after major releases, but these were always turned around and resolved very quickly after reporting them. If we found areas that required new feature requests or enhancements, these are generally delivered in a 4 or 8 week cycle

With Zephyr I can create tests right inside Jenkins that leverage labels and components and release cycles.

I find creating steps to be an awful editing experience. I tend to write tests in the ticket description instead just so I can avoid the cumbersome work of filling out steps.

Robust two-way synchronization with Jira. Automatically sync's with sprint stories and bugs. Ease of use with solid API integrations and plug-ins with other major release pipeline applications. Customer support and interactions have been outstanding. Zephyr has a Customer Advisory Board, which meets twice a year, to listen to, and respond to the industry. The product and team have advanced rapidly, allowing our organization to accelerate our DevOps initiative. Zephyr continues to be on the foreground of innovation, as seen by their latest release named "Maestro," their DevOps plugin that takes Zephyr to the next level, as a qualitative test management solution. Very satisfied with all aspects of the product and its future road-map.

The only con to Zephyr, is its ability to manage role-based securities. However, through an engagement with our top executives, and the senior executive team from Zephyr, they now have this concern vetted and will be working to incorporate this capability into a future release. Zephyr actively listens to its customers, so any (and I mean any) concerns you have, they truly listen and actively work to satisfy the need.

- Zephyr can be integrated to Jira so you can maximize the functionalities of Jira to Zephyr's core features- In Zephyr, you can create test cases, test plans, and test cycles very easily- Jira's different issue types like bugs and stories can easily be linked together with Zephyr- User friendly and components are easy to navigate- Can be integrated to other third-party apps for dashboard and reporting

- Even though the tool is user friendly and easy to navigate, the user experience is quite difficult and the flow of the process can become tedious especially if needs to be done multiple times- Creating of test cases is difficult when it comes to copying and pasting of multiple test steps

Integrated with Jira, allowed QA to easily capture screenshots

Cant login, login errors, can't use standard Atlassian credentials and forces you to create API keys, constantly forgets credentials but doesnt tell you until after you have filled out a full bug report so you end up losing all your work

the easy integration with Jira, its mostly simple to configure.

missing better planning and the ability to dictate different configuration in which each test execution should be reported differently. its not fully customizable (the reporting mechanism as well)

- few steps to create and execute tests
- few boilerplate jira objects (execution are on zephyr side, not on jira side)
- the "blocked" status

- Really slow to use, the integration with JIRA leads to data loss
- Hard to link snapshot, zip and other precondition or result artifacts and access it on execution