Changelog

Import tests from a spreadsheet

The tests you already have no longer need retyping. Import tests in the Library takes a CSV or TSV file exported from a spreadsheet or another tool — download the template if you are starting fresh — lets you map its columns onto a test's fields, and shows every test validated and grouped before anything is created. Rows that share a test ID become one test with a step each, even when they are not next to each other; a row without one becomes a single-step test. Tests can cover Jira issues from the same file, and they land in the project and folder you choose. A file can hold up to 500 tests and 10,000 steps.

An import can be stopped and picked up again, even after a reload or a closed tab, for seven days; tests that finished stay, and a retry never creates the same test twice. A test only appears in the Library, its counts and the coverage field once all of its steps are in. Anything that could not be imported comes back as a downloadable error report that names the row and the reason, in your language. Importing the same file again asks whether you meant to, rather than quietly making a second copy.

The Library is also easier to move around on a large site: the folder tree, the test list and the test's details now scroll independently, so picking a test near the bottom of a long list no longer leaves its details out of sight.

Five languages

Calibro Test now speaks German, Spanish, French and Portuguese (Brazil), alongside English. The whole app is translated — the library, the editor, a run step by step, the Tests panel on a story, the Coverage tab and its CSV headings, Settings — and so are the messages the app sends back, so a refused step or a folder that cannot be deleted explains itself in the same language as the button that was pressed. The Test coverage field's name and the Tests panel's title follow along in Jira's own chrome.

There is nothing to configure: each person sees the app in their own Atlassian language, two people on one site can read the same run in two languages, and any language we don’t ship yet falls back to English. European Portuguese reads the Brazilian catalog before falling back. Your tests are untouched — this is the app’s own wording, never the steps you wrote or the drafts the model wrote from your story, which come out in whatever language the story was written in; and the coverage field’s values stay English, so "Test coverage" = Failing is the same JQL on every site. More languages follow where the requests point.

First release

A library of tests with steps, folders four deep and shared steps, stored by the app on your own Jira site and never as issues. Runs of a test one step at a time — pass, fail or blocked per step, what actually happened, a pasted screenshot attached to the story, and a Bug filed from the failing step with the steps so far, the expected and actual result and the evidence already in it. A Test coverage field on every story, kept in sync by the app after every change that can move it, so "Test coverage" = Failing works in JQL, saved filters and board swimlanes; and a Coverage tab that is the same rule over a fix version, grouped by epic, component, assignee or status and exportable as CSV. Tests drafted from a story's description and acceptance criteria by Atlassian-hosted Claude, shown as drafts until somebody adds one. A Rovo agent — press Ask Calibro — and twelve tools any agent built in Rovo Studio can carry, every one of them running as you. Runs entirely on Atlassian Forge, with no external egress.

What comes next is on the roadmap.