Console
What each page of the Power BI Lab console shows: suites, test packages, runs, coverage, baselines, schedules, issues and settings.
Overview
Overview is the start page. Until setup is done, a notice at the top says the next step: connect Power BI, create a test package, approve a first baseline.
- Pass rate, 7 days: runs that passed among those that passed or failed this week; canceled runs do not count.
- Failing suites, Changes to review and the Next scheduled run.
- Needs attention: packages whose last run failed, visual changes nobody decided on, stale data, schedules that could not start, open high-severity issues and changes in Power BI that affect a package, each with a link to where you deal with it.
- Insights: the pages flagged over the last 30 days, and how many suggestions of what to test next are open (see Insights).
- Running now and the latest finished runs.
Suites
Suites lists every suite with its test packages: the reports they check, their schedules and their latest runs. Search by suite, report or owner, and filter by Failing, Scheduled or Manual.
A suite page lists its packages and lets you Run each one. Edit renames the suite or changes its owner; Delete removes it and moves its packages to the Trial suite, which is never deleted.
Test packages
A test package page shows what the package checks: one row per page and one column per check. Turn a check off for a single page there and save. It also lists the package schedules, its run in progress and its recent runs, and the changes in Power BI that affect it, such as a removed or renamed page.
- Run now queues a run; a package runs once at a time.
- Edit opens the wizard to change the pages and checks.
- Move puts the package in another suite.
- Delete removes the package and its schedules; its runs and their evidence are kept.
Runs
Runs lists runs in progress, with how many pages they checked so far, and the history of finished runs, newest first. Filter the history by result (Failed, Changes to review), by suite and by trigger (manual or schedule). Runs are numbered per organization: run #20 is at /app/runs/20.
A run
A run page says how the run went and lists its results: one row per check, page and report, grouped by tabs (Visual, Data, Accessibility, Performance).
- Visual review compares the screenshot with the baseline: Side by side, Overlay with a divider you drag, or Difference with the changed pixels highlighted.
- Open in Power BI opens the report page that was checked.
- Create issue on a result tracks it until someone resolves it.
- Technical details holds the log, every step and the fingerprint of the exact package that ran.
- Run again queues the same package; Download evidence saves the run as JSON.
Coverage
Coverage lists every report page a test package checks, with the result of each configured check in the latest run that checked it. A check added after that run shows Not run. Select a result to open its run.
Baselines
Baselines shows the approved screenshot of each page with a visual check, and its earlier versions. Pages are marked Change to review when the latest run found a difference nobody decided on, and Missing when no screenshot was approved yet.
Schedules
Schedules lists when test packages run on their own, with their next and last run. Add one with New schedule, pause it with its switch, or change and delete it. Times are in UTC. If a run was missed, for example while no worker was available, it is caught up once. Packages without a schedule are listed below.
Issues
Issues follows problems found in runs until they are resolved. Each issue links to the run it was found in. Resolve closes it, Reopen brings it back, Delete removes it.
Settings
- Profile
- Your account, the language of the console (English or French; until you choose one, it follows your browser) and your Connect as me sign-in.
- Organization
- The organization connection (service principal), the check thresholds and the time the Power BI inventory syncs every day.
- Members
- Who has access, and with which role.
- Billing
- The plan, its billing period, and the run minutes and seats used. An owner chooses a paid plan here and pays by card through Stripe; Manage billing then changes or cancels it, updates the card and lists invoices. When the trial ends or a payment fails, the organization is read-only: everything stays visible, but nothing new runs or changes.
- Notifications
- A webhook that is called when a run finishes, and what was sent.
- Audit log
- Who did what in the organization, newest first.