Skip to main content

Releases

In brief: Releases and environments let teams tag every execution and exploration with the deployment context insights and TrueCoverage filters require.

For the full release management workflow—test runs, manual and automation evidence, and release intelligence—see the Release Management documentation. This page covers admin settings for environments and the legacy current-release tag used by explorations.

Setting the Current Release Being Tested​

Releases allow you to track which version of your application you're currently testing.

Setting a Release​

  1. Navigate to Settings → Project Settings → Releases tab
  2. Click "Set Current Release" or "New Release"
  3. Enter release details:
    • Release name: Version number or release name (e.g., "v1.2.0" or "Q1 2024 Release")
    • Release date: When the release is scheduled or was released
    • Description: Optional description of what's in this release
  4. Click "Set as Current" to make this the active release

Active Release​

The active release is the one currently being tested:

  • All new bugs found during explorations are automatically tagged with the current release
  • Release tracking: Easily see which bugs belong to which release
  • Release management: Switch between releases as you progress

All Bugs Tagged with Current Release​

When you run explorations:

  • Automatic tagging: All bugs found are automatically tagged with the current release
  • Release context: Bugs include release information for tracking
  • Filtering: Filter bugs by release to see what's in each release

Release Management and Tracking​

Viewing Releases​

The Releases section shows:

  • All releases: List of all releases in the project
  • Current release: Clearly marked active release
  • Release details: Name, date, description for each release
  • Bug counts: Number of bugs found in each release

Switching Releases​

  1. Navigate to Settings → Project Settings → Releases tab
  2. Find the release you want to activate
  3. Click "Set as Current"
  4. All new bugs will be tagged with this release

Release History​

View the history of releases:

  • Past releases: See all previous releases
  • Bug distribution: See how bugs are distributed across releases
  • Release timeline: Understand the progression of releases

Benefits​

  • Organized testing: Keep track of what you're testing
  • Release-specific bugs: Know which bugs belong to which release
  • Better planning: Plan testing efforts around releases
  • Historical tracking: Maintain a history of releases and their bugs

Releases help you organize your testing efforts and track bugs by the version of your application you're testing.

FAQ

Default environment?

TestChimp creates a default QA environment and release; add mirrors for staging and production as you mature.

How do releases affect dashboards?

Execution scope filters all QA Intel widgets to environment + release + time range.

PR previews?

Map preview URLs via environment config and branch-specific execution docs—not always separate release records.

Related documentation