Skip to main content

Tips & FAQ

Keyboard shortcuts​

KeyWhereWhat it does
tImage and text viewersSwap new and reference in place, to flip between them. Applies to all viewers on the page.
hImage viewersHide or show the new/reference labels above images.
cImage viewer (after clicking it)Start or stop selecting a region, to see its histogram. Enter confirms the selection.
Ctrl / Shift + clickOutput Files, Artifacts & ConfigsSelect several files to diff.
EscDialogs, What's newClose.
↑ ↓ EnterBatch selector, filter suggestionsPick an item without the mouse.

Shortcuts are ignored while you type in a text box.

Tricks worth knowing​

  • Click a run's name on a card to see the history of that input.
  • Hover almost anything: metric names show their description, values show their exact number, ≠ tags explain reference mismatches, run names show metadata and paths to copy.
  • Fullscreen: each card has a fullscreen button at its top right, great for large images.
  • Compare two batches of the same commit: in the commit bar's Change menu, Also Select as Reference, then pick another batch in the reference bar.
  • Compare across projects: Change Project in the same menu, e.g. to compare two sub-projects of a monorepo.
  • Sort by a metric in the controls panel to see the worst regressions first.
  • Filter with negatives and regexps: -night, 2X5|GW1, threshold:0.5, fail. See the filter syntax.
  • Search the batch selector: type failed, running, local, tuning or a user name.
  • Short hashes work everywhere you type a commit.
  • Copy an image with the Copy button above image viewers, and paste it straight into a chat.
  • Share the exact view: everything is in the URL, see Sharing.

FAQ​

I can't find my commit​

  • Widen the date range of the commit list: by default it only shows the last 3 days.
  • Only commits with results are listed. If your CI didn't run QA-Board yet, the commit doesn't exist for QA-Board.
  • Paste its hash in the Filter... box and choose Go to commit.
  • Check you're in the right project: in a monorepo, each sub-project is a separate project.

The page says "No results" or "Error"​

  • No results: the commit's CI batch has no finished runs. Check the CI pipeline, or pick another batch in the batch selector (the commit may only have tuning or local runs).
  • An Error tag next to the commit: hover it. A 404 usually means a wrong commit hash, or runs saved in another project. A 500 is a server error: contact your QA-Board admins.

Why is the reference not what I expected?​

By default it's the latest commit with results on the project's reference branch, when you opened the page. Check the ref bar, and change it as explained in Picking a reference. Also check the reference batch and filter.

Some runs are compared with the wrong reference run​

Look for yellow ≠ tags: the best match used another configuration, platform or tuning parameters. Make the reference filter match the new filter, or choose a reference batch with the same tests. See How runs are matched.

A run is stuck as pending​

If it's really dead (e.g. killed by the cluster), use Mark as Failed in the run's ☰ menu, then Redo it. See Running from the web app.

My local runs don't show up​

Runs started from your workspace only appear in QA-Board with qa --share, see QA CLI tips. They show up in a batch named after you (you 🏠 label), with a warning that they may not match the committed code.

Why does the "What's new" dialog show up again?​

"Seen" release notes are remembered by your browser. A new browser, another computer or a private window doesn't know you've seen them. See What's new.

Where are the files?​

On a shared storage. Copy the paths from the ☰ menus, or see Where is the data saved?.

I'd like a new feature, or I found a bug​

Tell your QA-Board admins, with the URL of the page. See Sharing.