Teams that integrate their mabl results with Zephyr can now link their mabl plans to a specific test cycle in Zephyr. Until now, mabl either created a new test cycle for every plan run or sent every plan's results to one shared test cycle. By reporting to specific test cycles, teams can plan a cycle in Zephyr as usual and let mabl fill in the results.
Choose a test cycle for a plan
- Open the plan and click on the pencil icon to open the Edit plan page.
- In The basics, click on the Zephyr button.
- In Zephyr test cycle, search for the test cycle by key or name and choose it.
- Click Save.
Plans without a test cycle keep using the Default test cycles setting of the Zephyr integration, so you can move plans over one at a time.
Results land on the rows you planned
When a plan run syncs, mabl records each linked case's result on the row your team planned for it. A planned row is one in your project's default status, usually Not Executed, that mabl hasn't written to yet.
- The row keeps the environment and assignee your team set.
- Later runs add their results to the same row, so its history lists every run. The exception is a row for an older version of the case, where a later run replaces mabl's earlier result.
- mabl doesn't change a result someone recorded by hand. If a case has only a manual result in the cycle, mabl adds its own execution next to it.
The plan run page lists each test cycle that received results, and marks the one the plan chose.
Clearer result comments
Result comments in Zephyr and TestRail now start with the outcome, the mabl test linked to its run, and the plan linked to the plan run. For a failure, the comment shows the step and flow where the test failed, the error, and mabl's failure analysis, labeled as automated. When several mabl tests cover one case, the comment lists each test with its outcome, and the case takes the worst one.