Every app release starts with a version. In TestApp.io, a version is the central container that organizes everything related to one release cycle of your app — tasks, builds, quality metrics, and store submissions. This guide walks you through how versions work and how to move them from initial planning all the way to release.

What Is a Version?

A version represents a single release cycle of your app (for example, v2.1.0). It brings together all the work needed to ship that release: the tasks your team is working on, the builds uploaded for testing, quality metrics like blocker counts, and the launches that track store submissions.

Think of a version as your release hub — one place to see the full picture of where a release stands.

Creating a Version

  1. Open your app in TestApp.io.
  2. Navigate to the Versions tab.
  3. Click New Version.
  4. Enter a version name (e.g., v2.1.0 or Sprint 14 Release).
  5. Your version is created in Planning status, ready for you to start defining scope.

Version Statuses

Each version moves through a defined lifecycle. Here is what each status means:

  • Planning — You are defining the scope of this release. Create and link tasks, outline what will be included, and set goals. No builds are expected yet.
  • Development — Active coding is underway. Your team is working on the tasks linked to this version, and builds are starting to be created and uploaded.
  • Testing — QA is in progress. Builds are being distributed to testers, feedback is being collected, and blockers are being reported and resolved.
  • Ready — All blockers have been resolved, and the version is cleared for release. This status signals that the build is approved to ship. Note: you cannot move a version to Ready if there are open blockers.
  • Released — The version has been shipped to one or more stores. Your launches track the details of each store submission.
  • Archived — The version is no longer active. Archived versions are preserved for historical reference but are hidden from day-to-day views.

The Version Dashboard

Every version has a dashboard with five tabs that give you full visibility into the release:

Overview

A summary of the version's current state. See the current status, key metrics at a glance, and a high-level snapshot of progress across tasks, builds, and quality.

Planning

View and manage all tasks linked to this version. This is where you define what work needs to be completed before the version ships.

Releases

Browse all builds that have been uploaded for this version. Each build includes its upload date, platform, and distribution details. This tab gives you a clear history of every build your team has tested.

Quality

Track the quality health of your version. See the current blocker count, test completion rates, and other quality metrics. This tab helps you decide whether the version is ready to ship.

Settings

Configure version-level settings such as the version name and other properties specific to this release.

Moving Through the Lifecycle

Advancing a version through its lifecycle is straightforward:

  1. Open the version you want to update.
  2. Click the current status indicator.
  3. Select the next status in the lifecycle.
  4. The change is applied immediately and recorded in the audit trail.

Every status change is tracked automatically, so your team always has a complete history of when the version moved through each stage and who made the change.

Quality Gates

TestApp.io enforces quality gates to prevent premature releases:

  • Open blockers prevent moving to Ready. If any blocker is still unresolved, the version cannot be advanced to the Ready status. This ensures that known critical issues are addressed before you approve the release.
  • Resolve all blockers first, then move the version to Ready when your team is confident the build is ready to ship.
Tip: Use the Quality tab on your version dashboard to monitor blocker counts throughout the testing phase. Catching and resolving blockers early keeps your release on track.

Tips for Managing Versions

  • Create your version early in the release cycle — even during planning — so all related tasks and builds are linked from the start.
  • Use the Planning tab to connect tasks so your team has a clear view of what is in scope.
  • Monitor the Quality tab regularly during testing to stay ahead of blockers.
  • Once released, review the version dashboard for a complete record of the release cycle before archiving.

Need help? Contact us and we'll get back to you shortly.