Changelog

New features, improvements and fixes to Pie.

September 2026

Loops run your suites without anyone starting them

New Test runs

Copy link

A regression suite only protects a release if someone runs it. In most teams that someone is a calendar reminder and a person who is busy.

A loop runs the suites you choose without anyone starting it. Name it, pick the suites, and choose what fires it:

  • A schedule you set.
  • A new build upload.
  • A call to the API, once API access is enabled on the loop.

Each loop has its own page, with its triggers, its settings and every run it has produced. In run history one firing is one card, even when it ran five suites, so a night of testing reads as one line rather than twenty. A firing that found nothing to do says so. One that failed to start says what went wrong instead of leaving an empty card.

What it changesNobody has to remember to run the suite on Friday.

Read the docs

Improvements and fixes, September 2026

Improved Test runs

Copy link

Test runs

  • Creating a suite lands you on it, and saves stick.
  • A credential can be set as the app default.
  • A custom test can be added to one or more suites as you create it.
  • Discovery failures surface before the first step rather than after the run.
  • A coverage scan can be published as a single notification, and has an instructions editor.
  • Android OS versions in the suite dialog are grouped by form factor.

Fixes

  • The test case detail page no longer returns early and renders nothing.

August 2026

Describe the test. Pie writes the draft.

New Pie Chat

Copy link

Most test authoring starts with a blank editor and a step list. This one starts with a sentence.

Describe the test you want in Pie Chat. Pie navigates your app to understand the journey, then writes the test case back to you as a draft: the objective, the steps it will take, and what it will verify at the end. Then it stops.

Nothing runs until you say so. Cancel and the draft goes no further. Confirm and the screenshots panel opens and fills as the run goes, so you watch the test you asked for happen.

The draft is the point. It is the test written out in plain language, before a single step has run, for you to read and correct.

What it changesYou review the intent before the run instead of the result after it.

Read the docs

Scan up to a commit you pick

Improved Test runs

Copy link

Choose the commit a scan should pin to, from a list, instead of always taking the tip of the branch.

Useful when the tip is mid rework and the commit you actually want checked is two behind it.

Read the docs

Rotate mid-test. Landscape bugs included.

New Mobile

Copy link

Some bugs only exist sideways. A form that fits in portrait clips its button in landscape, and nobody rotates the phone in the middle of a test.

A test can now rotate the screen mid-run and carry on from where it was. Add the turn where your users would make it, and the landscape layout gets checked in the same run as the portrait one.

The run viewer shows the screenshots from a rotated step the right way up, so reading the evidence does not mean turning your head.

What it changesLayouts that only break in landscape get tested in the same pass as everything else.

Improvements and fixes, August 2026

Improved Pie Chat

Copy link

Pie Chat

  • The new chat screen was redesigned, and the chat list collapses when you want the space.

Test runs

  • Run history can be filtered by test suite.
  • The builds table shows where each build came from and the runs it produced.
  • Run history shows the OS version a run actually ran on.

Turn automatic reruns off

Improved Test runs

Copy link

Automatic reruns are a setting now, and you can switch them off. Leave them on and the limit is three attempts.

Fixes1

  • Disconnecting the Slack integration actually disconnects it.

    Integrations

July 2026

Report a bug and Pie tries to reproduce it

New Test runs

Copy link

Not every bug is found by a test. Someone on support sees it, a customer writes in about it, a PM trips over it on a Friday. Then it sits in a ticket with one screenshot and no steps.

There is a Report issue button on the issues page. Describe what you saw, attach screenshots or a recording, and pick the build and the login Pie should use. Pie then tries to reproduce it.

The issue opens straight away. A banner on it says how far the verification got, with a link into the run and a retry if the first attempt did not get there. If you already raised the ticket in Jira, Linear or Asana, link it at the same time so the two never drift apart.

When Pie reproduces the bug, it has steps, screenshots and a run behind it. When it cannot, you know that too, and you can see what it tried.

What it changesA bug a human found gets the same evidence trail as a bug Pie found.

Roll a test case back to the version that worked

New Test runs

Copy link

Tests drift. Someone tightens a step, a check changes, and three edits later the version that passed is a memory.

Open a test case, open its version history, and pick the version you want back. Pie asks you to confirm, then restores that version in place and reruns the test case from it, so you see straight away whether the rollback did what you hoped.

The restore is admin only. Everyone else can still read the history and see which version is current.

What it changesGetting back to a version that worked takes one confirmation instead of a rewrite.

Launch arguments for your mobile app

New Mobile

Copy link

Set the arguments your app should launch with once, in app settings, and every run picks them up.

The launch configuration fields that used to hide themselves on some platforms now stay where you put them.

Start a check on an open pull request

New Pull requests

Copy link

Open pull requests have a manual trigger now. Ask for a check on the branch as it stands, without pushing a commit to get one.

That helps when the last run went out on a bad build, or when something changed outside the branch.

Read the docs

Improvements and fixes, July 2026

Improved Test runs

Copy link

Test runs

  • Run results can publish automatically, from a toggle in settings.
  • The screenshots panel shows a waiting state while an automatic rerun gets going, then live screens once it produces them.
  • A test case header carries its crash triage verdict.
  • A flagged step records the reason and the result in one standard format.

Issues

  • A tracked issue can be resolved, and its repro history stays visible after you untrack it.

Mobile

  • Android builds that are ARM only show as verified rather than failed.

Fixes

  • The sign in form shows a validation error when a field is left empty.

Fixes4

  • Cancelled runs stay visible in run history, and no longer hide the runs around them.

    Test runs

  • Uploaded builds show their version before the first run, not after it.

    Mobile

  • A key feature saved with no prompt no longer produces an empty suite in silence.

    Test runs

June 2026

Connect GitLab yourself, self-hosted included

New Integrations

Copy link

Where your code lives should not decide who on the team can set Pie up.

GitLab used to be admin only. Now anyone can connect it from Integrations: sign in and pick the projects Pie should watch from a list. Apps that build from more than one repository say so on the connect screen, so you can see the whole set before you finish, and Pie treats those connected projects as one codebase.

GitLab that your team hosts connects the same way. Give Pie the host address and a personal access token instead of signing in to the hosted version. Everything after that is identical.

What it changesTeams on GitLab set themselves up the same way the GitHub teams do.

More detail on a step

Improved Test runs

Copy link

The step card in the viewer shows the action on its own. The timestamp, the page URL and the rest of the detail moved into a meta tab beside it.

A long URL opens in a popover instead of being cut off.

Read the docs

Improvements and fixes, June 2026

Improved Test runs

Copy link

Test runs

  • Archived tests show inline as a collapsed group rather than behind a filter.

Issues

  • Active issues group into buckets by when they were first found.
  • A Created by filter narrows the list to one person.
  • Clear status actually clears, and restoring respects who is looking.

Fixes

  • Recoverable navigation errors stop showing the server error page.
  • An invite opened by a different signed-in account is handled instead of failing.

May 2026

The issues page, rebuilt

Improved Test runs

Copy link

Issues are cards now. Each one carries its severity, the run it came from, and whether Pie is still tracking it.

They group by how long they have been open, so a bug from three weeks ago does not sit in the same block as one from this morning. Filters cover the run, the person who rejected an issue, and the window they rejected it in.

Resolving, acknowledging and clearing a status behave the same way from the list as they do from the detail page.

Read the docs

Cancel a run that is still going

New Test runs

Copy link

Run history has a cancel action on active runs. Start something by mistake and you can stop it rather than wait it out.

Hover a run and a tooltip tells you the environment it is using, so you know what you are cancelling before you do it.

Read the docs

Version history on a test case

New Test runs

Copy link

Every test case keeps a history of its versions. Open the history sheet and you get each version, a summary of what changed in it, and the person who made the change.

The version you are running is marked as the current one, so there is never a question about which one is live in your suite.

Improvements and fixes, May 2026

Improved Test runs

Copy link

Test runs

  • Run history cards link back to the run they came from, and a collapsed key feature stays collapsed.

Mobile

  • Credentials have copy buttons.

Fixes

  • A stale deploy prompts one reload and a reliable toast instead of a loop.
  • A dialog you closed no longer starts a timeout in the background.

April 2026

Read a week of testing without opening a run

New Test runs

Copy link

A run report tells you what one run found. It does not tell you what the week looked like: what Pie found, what got fixed, and what came back clean on the retest.

Coverage stories is that weekly read. Each story card opens to the issue behind it, with the expected and the observed behavior side by side, screenshot evidence, and links to the test cases that already cover it. Stories that need attention sit above the ones that came back clean. Move between weeks from the bar at the top.

It is the page to open on Monday, before anyone asks what testing found.

What it changesStories that need attention sit above the ones that came back clean.

Read the docs

Pie Chat is now in the sidebar for everyone

New Pie Chat

Copy link

Reading a run means opening it, scrolling to the step, and working out what the screenshots are telling you. Sometimes you just want to ask.

Pie Chat used to be limited to admins. It is now in the sidebar for every user with an app, carrying a Beta tag. Ask it about your tests, your runs and your issues and it answers from your own data. Threads are saved, so you can come back to one and keep going.

A handful of actions stay with admins for now. Everything else is open.

What it changesThe fastest way to ask what happened in a run is now a sentence.

See where a credential or a script is used

New Test runs

Copy link

Credentials and execution scripts now show which test cases reference them. Open the side sheet from either list and you get the full set.

Scripts that nothing references are highlighted, so the ones left over from an old flow are easy to find and retire.

Read the docs

Improvements and fixes, April 2026

Improved Test runs

Copy link

Test runs

  • Toasts were redesigned. Success is a green pill, an error is a card you can read, and repeats stack instead of piling up.
  • Every toast says what actually happened rather than Success or Error.
  • Empty states on the test case page say what to do next.

Mobile

  • iOS discovery can connect a hardware keyboard, and can do a full simulator reset per clone.

Fixes

  • Discovery failures explain what went wrong.
  • Comma-separated addresses paste correctly into an invite.
  • The issue card says why an issue was rejected.

March 2026

Did this branch break anything? Now it's a page.

New Pull requests

Copy link

The question every reviewer asks before merging is whether the branch broke anything. The usual answer is a message to whoever ran the tests last.

Every pull request Pie has tested gets a row on a PR Tests page. Open one and you get the branch, the commit, the current status and the test results underneath it. Each result links to the test case that produced it, and you can add that test case to a suite without leaving the page.

The list updates while a run is in flight, so a pull request that is still being checked shows its progress rather than a stale verdict.

A PR Coverage tab sits alongside it and shows what Pie covered on the pull request, with screenshots and live results as the run goes. Coverage scans read from the same place, so what Pie did before the pull request and what it did on it read as one story.

What it changesThe answer lives on a page now, not with whoever ran the tests last.

Read the docs

Pick the OS version your app is tested on

New Mobile

Copy link

An app that passes on the newest OS can still fail for the customer who has not updated in a year. Those are the bugs that arrive as one-star reviews.

The new run form has an OS version picker for mobile apps. Pick the version you care about and the run uses it instead of the default.

The same picker is in the discovery step during setup, so the first run a new account makes can target a specific version too.

What it changesThe bug that only shows on last year's OS gets tested on last year's OS.

Connect GitHub from Settings

New Integrations

Copy link

GitHub has its own panel in Settings. Connect the repository there and Pie can start watching the pull requests that land in it.

The connection is per app, so a team running more than one app connects each one to the repository that builds it.

Read the docs

Issue comments, with mentions

New Integrations

Copy link

An issue you exported to your tracker now shows that ticket inside Pie, with its comments and the people mentioned on it.

You can leave a comment from the issue itself and mention a teammate in it, so the conversation stays next to the evidence rather than in a second tab.

Read the docs

Improvements and fixes, March 2026

Improved Test runs

Copy link

Test runs

  • The new run dialog shows the build ID and the upload date, so you can tell two builds apart before you start one.

Issues

  • Rejecting an issue has keyboard shortcuts and a searchable reason list.

Fixes

  • Cached screenshots no longer leave the loader spinning.
  • URLs in the step viewer read properly rather than truncating mid path.

Not using Pie yet?

See how it tests your app.

How Pie works →