Skip to main content

The Zephyr tab in Context

What Context's Zephyr tab shows, how each figure is counted and how to filter, hide or duplicate its cards.

With Zephyr connected, Context has a Zephyr tab, right after the QA tab, with the tests your team keeps in Zephyr Essential: which Jira tasks they cover and how each test went, the test cycles and who ran them. Every figure is compared with the previous period. Connecting Zephyr adds the tab after QA in every view that has the QA tab, and adding QA to a view brings it along; you can also add it from +. Without Zephyr connected, the tab is not offered. To connect Zephyr, see Zephyr integration.


​

The cards


​

  • Tasks with tests — the Jira tasks whose tests ran in the period. Show the tasks lists each task with its tests below it, and how each test went the last time it ran.

  • Tests run — the test cases run in the period, each counted once, with its last result.

  • Tests with no task — the tests run in the period that are not linked to any Jira task. Link them in Zephyr and they count for their task.

  • Test execution results — every run that finished in the period, by result, with the names and colors you use in Zephyr.

  • Bugs found in testing — the Jira issues linked to the period's runs that your organization classifies as bugs, as in the QA tab.

  • Progress by cycle — each test cycle planned in the period or with runs in it: its runs, how many are not run yet and how they went.

  • By tester — how many runs each person made and how much time they logged.


​

How it is counted


​

  • A test counts once in a period, with its last result in it.

  • A run still in its project's default result («Not Executed», unless you renamed it) has not been run: it only counts in Progress by cycle, as not run.

  • The results keep Zephyr's names and colors. Zephyr does not say which result means passed, so no pass rate is shown.

  • A test belongs to a task when Zephyr links it to that task as coverage.

  • The view's Jira boards narrow these cards to their projects in Zephyr, and the view's people to the runs they made.


​

Show details and filters


​

  • Every Show … link opens the rows behind it, with a filter on each column and Export to CSV.

  • Filtering the tasks, the tests, the tests with no task, the results or the bugs from their Show details measures that figure with the filter for everyone who opens the view; Remove filter goes back.

  • To hide or show any of these cards, use the Zephyr tab's ⋮ › Edit metrics.

  • On any card, ⋮ › Duplicate by project, Duplicate by test cycle or Duplicate by tester makes copies measured over the projects, cycles or testers you tick, in a tab of their own.

  • The cards can also go into a tab of your own.

  • An AI report reads Zephyr too: ask for Zephyr's test cases by project and by type — as your team types them: by folder, label, a field of your own or the Jira component — or by status, priority or label, or for its runs by result, and the report is written from Zephyr.


​

Who sees them


​

  • Anyone who can see the QA tab sees the Zephyr tab.

  • They are not shown in public links, because they name testers and tasks.


​

Related articles


​


​

Did this answer your question?