My main use case for Zebrunner Testing Platform is to add test cases, prepare test cases, develop a test plan, and execute test cycles.

In my recent project for Cipo, I used Zebrunner Testing Platform to execute the test cases manually and I need to add the results over Zebrunner; the same data I need to share with my client and in Slack.

My daily routine with Zebrunner Testing Platform involves creating test runs with the milestones and creating workspaces for different sub-projects under the main pillar.

Zebrunner Testing Platform offers great features such as easy usage of the tool, allowing for creating, removing, or editing test cases; everything is user-friendly, and sharing results through Zebrunner Testing Platform is also valuable, including linking Jira tickets.

The Jira integration helps my team because if any failed test case appears during execution, we file bugs in Jira and can link the respective ticket with Zebrunner Testing Platform, making it easy for the client to understand the bug's context and from which test case it has been caught.

Zebrunner Testing Platform positively impacts my organization as we usually use it as a repository to store test cases and results, similar to TestRail; previously, we used Zephyr and TestRail tools, and now we also use Zebrunner Testing Platform.

To improve Zebrunner Testing Platform, we need to include more statuses during execution, such as passed, failed, and blocked; we usually have these cases, but we want more statuses in progress, reviewing of test cases, or test cases in development, which helps the testers easily identify whether a test case is executed manually or automated, or whether the feature is implemented or not.

Zebrunner Testing Platform is stable.

The scalability of Zebrunner Testing Platform is good.

I have not tried the customer support for Zebrunner Testing Platform.

I didn't previously use a different solution; I have not used any.

Before choosing Zebrunner Testing Platform, I did not evaluate other options; there are no other options I looked into.

I didn't purchase Zebrunner Testing Platform through the AWS Marketplace since it's client-provided software.

I don't know about the pricing, setup costs, and licensing because I have not researched those aspects.

My daily routine with Zebrunner Testing Platform involves creating test runs with the milestones and creating workspaces for different sub-projects under the main pillar.

I don't have any idea about return on investment related to Zebrunner Testing Platform; I haven't seen metrics such as fewer employees needed or money saved.

I didn't purchase Zebrunner Testing Platform through the AWS Marketplace since it's client-provided software.

I don't know about the pricing, setup costs, and licensing because I have not researched those aspects.

Since switching to Zebrunner Testing Platform, I notice a positive outcome in terms of time saving.

When comparing our previous tool to Zebrunner Testing Platform, I estimate that my team saves about one hour, allowing us to easily complete our assigned tasks one hour earlier.

My advice for others looking into using Zebrunner Testing Platform is to explore the whole platform and know its features; then only can they easily use the software.

My company does not have a business relationship with this vendor other than being a customer.

I have no additional thoughts about Zebrunner Testing Platform before we wrap up.

I rate Zebrunner Testing Platform around eight out of ten because, as I've mentioned, we need some more improvements in Zebrunner Testing Platform, such as adding a few more statuses.