Zephyr organizes your testcases

Organize All Your Testcases

Re-use, Schedule, Assign and Execute

Zephyr allows you to organize and re-use testcases across your various Projects, Releases or Sprints with easy drag-n-drop capability. Have your Test Leads plan out the Execution cycles and assign manual and automated test cases to the testing team members in an easy to see, visual format. Assigned testcases are readily available to testers in the Test Execution view from which they can also log and map defects to testcase executions and ultimately back to Requirements for end-to-end traceability.

Write your manual test cases

Open your Test Case Creation application and the areas or test cases assigned to you are right there, all neatly organized for you to start writing them. Or tweak existing ones. Or add Custom Fields. Or find that one test case you remember from 9 months ago in an old forgotten Release that you can now easily navigate the Global Test Case Repository to find and copy over, saving you tons of time. And when you realize that something got screwed up, rollback to a previous testcase version - they are all being tracked!

Track your automated scripts

Zephyr allows you to track all your manual and automated scripts from one place. Use any automation tool(s) of your choice - Commercial, Home-grown or Open Source. Create a manual test case (or a placeholder) and add information about your automated script and how to kick it off. It will then keep track of what % of your test cases are automated, allow you to schedule them for execution and kick them off when its time to execute them.

Execution Scheduling and Assignments

Build a dynamic and visual schedule, define software builds and test environments, quickly grab the test cases to be run in each phase and assign them to your testers - all from a single, intuitive screen. And tweak this constantly as your Execution Cycle progresses, because we know, it is going to change. We've been there.

Visually line up the groups of tests to be run (e.g. Functionality, Regression, Integration etc.) and assign them to your individual testers or to the whole group . These show up instantly on a Tester's Desktop in their Test Case Execution application with the right build and test environment information so they can get crackin'. Quickly load-balance if a tester is lagging behind or absent or just needs additional help. As a Lead you have instant feedback on the progress of the individual test runs or the overall test execution cycle and can make appropriate tweaks and changes to it. With the flexibility of many different ways to set up testcase execution, there's bound to be one that works exactly they way you do.

Execute rapidly and file Defects

Focus the tester on what needs to be run and fast. Based off of the test run created by the Execution Scheduling and Assignment application, the Test Case Execution application displays all the relevant information that a tester needs to rapidly run test cases and update their results. Test step level status, test data, expected and actual results, contextual documentation, attachments - all within in easy reach in an optimized UI. A flick of a wrist and test results are updated. And when a testcase fails (or observed behaviour is just odd) a quick click right there, a defect screen pops up, enter details quickly while they are still fresh in your mind, automatically copy the test steps over and you've just filed a defect directly in JIRA, Bugzilla or the in-built defect tracker. Get back to running the next test case!

Everybody gets instant status

How much have you completed? How many are failing? Where? How is the overall quality? Which areas are most buggy? When will you be done?

Now the instant you update the status of the test case or file a new defect, all the metrics get updated automatically. This works across both your manual and automated tests so everybody is getting a comprehensive view of all test execution. And as a Lead or a Manager, you do not have to spend many hours in the evenings getting on conference calls, collating information from various team members and systems, formatting it and sending out status to everybody in the project team (sound familiar?)