Skip to main content

Changelog

What each TestChimp platform release shipped, newest first. A machine-readable copy is at /changelog.json.

1.0.48 - 2026-11-13​

Highlights​

Batch test execution durations match the real run time again, and named test-run and plan lists give more room to scenario titles.

Improvements​

  • Test runs: Named test-run detail shows only the latest five executions per scenario, keeps the Executions column narrow, and gives the Title column more space. Adding a coverage record is a compact icon control.
  • Plans: Story and scenario titles in list and insights views ellipsize instead of crowding trailing status icons.
  • Test runs: Long execution titles in the viewer ellipsize with a tooltip so header actions stay on one row.
  • Docs: New guide on alpha vs beta testing, and a clearer title on the mabl alternatives page.

Bug fixes​

  • Test runs: Per-test duration in a batch uses the reporter-measured run time instead of wall clock derived from timestamps that move after completion (for example release sync), so individual durations no longer look far longer than the batch.

1.0.47 - 2026-11-12​

Highlights​

New users who arrive from an OAuth consent flow keep that destination through onboarding, and docs plus search indexing get clearer published URLs and several new how-to guides.

Improvements​

  • Docs: Canonical URLs and llms.txt point at the final published paths instead of redirecting URLs. Non-HTML feeds are noindexed, and thin pages are linked from the site footers.
  • Docs: New guides cover spec-driven testing, acceptance test examples, flaky tests, GitHub pull request checks, Claude Code with Playwright, and the Playwright Trace Viewer. Several alternatives pages use clearer titles.
  • Site: App and API hosts serve disallow-all robots.txt and noindex headers so sign-in and API surfaces stay out of search results.

Bug fixes​

  • Onboarding: New users who sign in from an OAuth consent flow (such as the Claude MCP connector) keep that destination through team setup and return to the consent screen instead of the home dashboard.

1.0.46 - 2026-11-08​

Highlights​

CI test runs can keep a full video recording, and the execution viewer is rebuilt around clearer verify actions, failure context, and faster playback. Performance runs can store timeseries metrics for charts, and onboarding email matches the current product.

New capabilities​

  • Test runs: Playwright CI uploads can include a full video of the run. Open it from the execution viewer. Videos older than the project retention window are removed automatically.
  • Agents: Coding agents can set a scenario's verification strategy (auto or manual), including from plan markdown frontmatter. Values that were previously ignored now persist.
  • Performance tests: Perf run ingest can attach optional timeseries metrics so result charts use stored series data instead of only the live run state.

Improvements​

  • Email: Welcome, trial, and product tip emails are rewritten for the current product framing, with a clearer early setup nudge for new signups. Transactional mail sends through Amazon SES for more reliable delivery.
  • Test runs: In a batch execution, search tests by name, scenario title, or scenario id across the whole batch. Changing page size (including 100 per page) updates the list correctly.
  • Test runs: Automated runs pin the screenshot pane to the latest shot (Last Screenshot). Manual sessions with multiple screenshots follow the selected step.
  • Test runs: The execution viewer header uses a clearer Verify / Re-verify flow with an anchored confirm, compact facts and scenario chips, a failure summary that selects the failing step, and icon-only archive/delete.
  • Test runs: Video playback adds 2x and 5x speeds.
  • Test runs: Soft-skipped Playwright runs that include a reason show as Partial (amber) instead of Skipped, with the reason behind an info control.
  • Test runs: Long scenario titles in named test-run tables wrap inside the column instead of overflowing.
  • Performance tests: The list Test column uses a fixed width with ellipsis, When shows the date only, and only the latest batch stays expanded by default.
  • Plans: Long story and scenario titles wrap inside kanban cards instead of spilling past the card edge.
  • Docs: Quick start covers /testchimp init per teammate and /testchimp project-init once per project. Qase and mabl alternatives pages use clearer titles.
  • Docs: New guides cover Playwright MCP and commonly used test credit card numbers.

Bug fixes​

  • Agents: Asking product questions through the docs helper no longer fails with a generic "Could not answer question" error on consecutive calls.
  • Integrations: Enabling Slack notifications no longer errors when Slack identity is not connected; settings prompt you to connect first.
  • Performance tests: Stored timeseries cannot be overwritten across projects.

1.0.45 - 2026-11-06​

Highlights​

Creating a team finishes without waiting on the sample project, and a progress dialog prepares that project in the new workspace. Completing a CI batch no longer fails after the results are saved, when API coverage is still being queued.

Improvements​

  • Workspace setup: After you create a team, a progress dialog prepares the sample project in your workspace. Creating the team no longer waits on that copy, so the step no longer times out.
  • Projects: The create-project wizard no longer asks you to set up site and UI testing configuration, so starting a project takes fewer steps.

Bug fixes​

  • Test runs: Completing a CI batch no longer errors once the results are saved. API coverage for that batch is queued separately, so a problem queueing coverage does not reject the completed batch or send it back for retry.

1.0.44 - 2026-11-06​

Highlights​

Admin and feature services that write structured Cloud Logging JSON start again on the current runtime.

Improvements​

  • Docs: The TestRail alternatives card on the guides hub uses a 2026 title and a summary aimed at teams that keep plans and Playwright tests in Git.

Bug fixes​

  • Platform: Admin and feature services that write structured Cloud Logging JSON start again on the current Spring Boot 2.7 runtime.

1.0.43 - 2026-11-06​

Highlights​

CI results attached to a test run now finish saving, so those runs show up instead of being dropped after repeated failures.

Improvements​

  • Docs: Comparison and alternative guides say a SOC 2 Type II report is available on request. The TestRail alternatives guide adds a short section on how to evaluate an alternative.
  • Website: Footers include a Featured on Dealpuffin badge.

Bug fixes​

  • Test runs: Completing a CI batch attached to a test run no longer fails while saving results. Those reports were retried until they were dropped.

1.0.42 - 2026-11-04​

Highlights​

Guides hub includes a Proof Points API walkthrough, and SaaS backend logging is structured in Cloud Logging so incidents can be triaged faster.

Improvements​

  • Docs: Guides hub adds a Proof Points API guide for restricted project keys and integrations such as Dealpuffin.
  • Platform: Backend services write structured JSON logs with request context to Cloud Logging. Cloud Run image rolls during upgrade resolve digests correctly, and the unused VM ingress container stays off.

1.0.41 - 2026-11-04​

Highlights​

Creating a team during signup no longer hangs forever when something goes wrong; you get a clear error instead of an endless spinner.

Bug fixes​

  • Onboarding: Create Team times out and shows an error if the request stalls. New organizations get default job roles, and creating an organization is safe to retry if the first attempt already succeeded.

1.0.40 - 2026-11-03​

Highlights​

You can create restricted project API keys that only allow selected programmatic tools, including a Proof Points readout for release pace, scenario coverage, and scenario count.

New capabilities​

  • Project API keys: Create a restricted key from Project Settings with templates for Proof points, Read-only, or Read-write, or pick tools yourself. Restricted keys can only call the tools you allow. Full-access keys keep working as before.
  • Programmatic API: get_proof_points returns releases in the last 30 days, scenario coverage percent, and test scenario count for integrations that need a small QA posture snapshot.

Improvements​

  • Project setup: The Bitbucket option in create-project now shows the Bitbucket logo with the other providers.

1.0.39 - 2026-11-02​

Highlights​

Performance testing, API coverage, and observability are available without a Growth plan. Only TrueCoverage stays on Growth.

Improvements​

  • Website: The homepage customer strip includes Dealpuffin, and FindMyHelp links to its site.
  • Docs: The Tiden alternative guide uses Tiden's November 2026 pricing. Docs use the same type as the main site. An old blog address redirects to the current post.

Bug fixes​

  • Plans and product access: Performance testing, API coverage, and observability no longer ask you to upgrade to Growth. That includes release performance tests, the API coverage Configure button, observability settings, runtime charts, and the project-setup API contract option. TrueCoverage remains a Growth plan feature.
  • Plans: The upgrade dialog is centered in the window, and the Recommended tag on Growth is fully visible.

1.0.38 - 2026-11-01​

Highlights​

TestChimp has completed a SOC 2 Type II audit. The website now shows that, with a trust center where you can request the report.

Improvements​

  • Website: The homepage has a trust section for the SOC 2 Type II audit. The AICPA badge and a Trust center link appear in the site footer and in docs, and a new FAQ answers whether TestChimp is SOC 2 compliant.

1.0.37 - 2026-11-01​

Highlights​

Signing off a release is clearer, and changing who verifies tests lets you choose which existing assignments to update.

Improvements​

  • Releases: Add approval asks for confirmation and stays a secondary action. Each approval shows the person's photo with their job role. When no deploy webhook is saved, the release page shows a banner you can dismiss for that project.
  • Verified Tests: Changing who verifies lets you choose how existing assignments update: all of them, only tests awaiting verification, awaiting plus unassigned, or new tests only.
  • Docs: Comparison guides for a VibeQA alternative, app audits versus ongoing QA, and human testers versus ongoing QA lead with the 14-day free trial.

Bug fixes​

  • Project settings: The deploy webhook example follows the app theme. Browsers no longer fill the webhook URL or authorization header from saved passwords, and Remove sits at the end of each webhook.

1.0.36 - 2026-10-31​

Highlights​

People can sign off a release in their job role, and a deploy webhook fires when the roles and people you require have all approved. Verified Tests can assign who reviews each test, and they get one notice when a run still needs a first check or a re-check.

New capabilities​

  • Releases: Add your own approval on a release. The tag is your organization job role (default dev), set once in Team settings and snapshotted when you approve. A deploy webhook in Project Settings fires when every required role and every required person has approved.
  • Verified Tests: Choose who verifies: the test author, or a set of teammates who share new assignments evenly. The home For you card lists tests awaiting your verification. After a CI or local run, you get one email covering new tests and tests that need re-verification. Agent-only runs do not send that email.
  • Website: HAR Playground analyzes a HAR file in the browser, groups failing, slow, and insecure requests, and can export to Playwright or curl. Share links are redacted and encrypted.

Improvements​

  • Website: HTTP now redirects to HTTPS. Docs pages load their analytics script again, product pages share one app entry for search results, and in-site links go to the final URLs.

Bug fixes​

  • Plans: When an agent creates a story or scenario, the recorded action now points at that new item.

1.0.35 - 2026-10-30​

Highlights​

Scenario coverage and linked-test views ignore deleted automation, so removing a test no longer leaves a false “covered” signal. The upgrade plan modal and in-product tutorial links are cleaner too.

Improvements​

  • Plans: Upgrade modal drops the Enterprise card and tightens column alignment
  • Tutorials: Product tutorial links point at the current video URLs

Bug fixes​

  • Coverage / linked tests: Soft-deleted or missing automation no longer counts as covering a scenario for linkage and named-test-run coverage, and deleting a test clears its scenario mappings

1.0.34 - 2026-10-30​

Highlights​

Shipping a release is now a first-class agent workflow: /testchimp create release creates the catalog entry, runs the QA actions your policy allows for that release type, and summarises GATE posture. Day-to-day guidance is clearer too: run QA after each PR, create release when you ship.

New capabilities​

  • Workflows / releases: /testchimp create release (major, minor, or hotfix) locks release QA policy on first run, creates the release and a named test run, drives suite / ExploreChimp / performance / security actions per type, and reports release GATE posture. Agents can create a queued security scan on a release, then run the matching release check.
  • Docs: New Create Release playbook and updated Quick Start / Workflows intro so the recommended loop is run QA per PR and create release when shipping; Upkeep stays as suite maintenance.

Improvements​

  • Workflows UI: Popular composites are Run QA and Create Release; Upkeep lives under Functional testing. The How TestChimp Works tip matches that DevX. Releases list offers a copyable create-release prompt.
  • Website: Product and pricing pages keep tightening copy and motion (Studio, verified tests, Bonobi, MeetBots, UX posture, security and performance); Blog is in the header; How it works can play the explainer over the page.

1.0.33 - 2026-10-30​

Highlights​

API-operation coverage work no longer fans out unbounded jobs that pin FeatureService CPU. The Tests overview widget shows how many tests are Verified, and testchimp.io product and pricing pages keep getting clearer.

New capabilities​

  • Dashboard: The Tests overview widget shows a Verified count with good / ok / bad ranges based on the share of tests that are verified.

Improvements​

  • API coverage: Coverage denormalization runs through a durable, bounded job queue with at most one running job per project, so overlapping updates retry instead of stampeding the database.
  • Website: Product pages use still heroes and one idea per section image; pricing explains pay-as-you-go for ChimpHands credits and MeetBots hours; MeetBots covers platforms; the homepage shows production scale numbers and clearer Studio workflow copy.

Bug fixes​

  • Reliability: Stuck or overlapping API-operation coverage updates no longer keep FeatureService at full CPU or take it down under load.

1.0.32 - 2026-10-29​

Highlights​

testchimp.io’s product marketing is on the new Web design system across the homepage and product pages. Large Named Test Runs are much less likely to take FeatureService down under concurrent coverage load.

New capabilities​

  • Website: Product pages for meaningful coverage, UX posture, security and performance, release governance, verified tests, Studio, agent orchestration, Bonobi, ChimpHands, test planning as code, MeetBots, and AgentWatch, with matching tours and stills on the homepage product map.

Improvements​

  • Website: Homepage and product pages use the TestChimp Web design system (titles reveal on scroll, approved illustrations, trackers after load, responsive polish). Analytics goes through GTM.
  • Named Test Runs / releases: Coverage rollups coalesce overlapping requests, reuse short-lived results, and load mappings with project-scoped queries so large plans and release viewers share one pass instead of stampeding the database.

Bug fixes​

  • Reliability: Concurrent Named Test Run coverage and API-operation coverage updates no longer exhaust the connection pool or deadlock FeatureService into an unhealthy state under heavy release-viewer and ingest load.

1.0.31 - 2026-10-28​

Highlights​

testchimp.io now serves docs, guides, blog, tools, and marketing pages on one site. Agents fixing coverage gaps can list uncovered plan scenarios even when no SmartTests are linked yet.

New capabilities​

  • Website: Docs, guides, and blog live on testchimp.io (with redirects from the old docs subdomain). Open-source tool pages and marketing pages (including pricing and the homepage) ship from the new Next.js site behind Cloudflare.
  • Docs: New and retargeted guides and blog posts for teams comparing TestChimp and reviewing agent-written tests, including how to ship AI-written code you do not fully understand.

Improvements​

  • Release viewer: Creating or updating scenarios only refreshes stats for recent active releases, so large plan imports no longer hammer the database.

Bug fixes​

  • MCP / CLI: get-requirement-coverage with a plans folder scope (including the plans root) returns ranked uncovered scenarios when SmartTests are missing, instead of an empty result. Ranked and limit modes include non-covered plan scenarios for gap recommendations.

1.0.30 - 2026-10-25​

Highlights​

Ingress, MCP, and the public site are watched for downtime, and the production servers warn before a disk fills up.

Improvements​

  • Reliability: If ingress or MCP stops answering for a few minutes, that pages as critical. The public site is watched as a warning. Disk use on the production servers warns above 80% and pages above 90%.

1.0.29 - 2026-10-25​

Highlights​

Session recordings can be matched to the user and organization they belong to, including the visit where someone signed up.

New capabilities​

  • Docs: A Tiden comparison page for teams looking at a per-change verification gate. It describes how TestChimp keeps the product definition current from meetings and coding-agent sessions, measures scenario, API contract, and real-user coverage, and leaves the release decision with people.

Improvements​

  • Session recordings: Recent sessions can be listed for one organization, or across organizations for the last 7 days. Each row shows the user, organization, and signup date, and you can copy the user id or session id to open that recording. A visit that starts before signup stays linked once the account is created.

1.0.28 - 2026-10-25​

Highlights​

Planned platform upgrades no longer treat the brief service restart as an outage.

Improvements​

  • Reliability: During an upgrade, availability alerts stay quiet while services restart, so a short burst of errors is not opened as an incident. An alert that has stopped firing closes on its own after 30 minutes.

1.0.27 - 2026-10-23​

Highlights​

Test Planning can import user stories and linked test cases from Azure DevOps. The Bots page gives MeetBot a logo and clearer actions, and marks Bots as new in the sidebar.

New capabilities​

  • Test planning: Import user stories and scenarios from Azure DevOps Services. Connect with an organization URL, a personal access token that can read work items, and a project. Choose the work item type that is a story (User Story, Product Backlog Item, Requirement, or Issue). Test Case work items linked with Tested By become scenarios, including their steps and shared steps. An optional WIQL filter narrows which stories are included. Tags, Area Path, Iteration Path, and similar fields can become labels. File names and folders use the same choices as a Jira import: external id, TestChimp id, or AI for names, and a field or AI for folders. Area Path and Iteration Path become nested folders.

Improvements​

  • Bots: MeetBot has its own logo. Join Meeting, View Past Meetings, and Settings sit on one row; Settings opens the menu for calendars and instructions. When no meetings are coming up, connect a calendar opens the calendars page. Bonobi links to the QA bots article and is described as a per-person QA bot that coordinates work for each team member.
  • Navigation: Bots in the sidebar is marked New and sits above Workflows. ChimpHands no longer shows a Beta label.

1.0.26 - 2026-10-23​

Highlights​

Projects can connect Bitbucket Cloud and sync SmartTests and plans. Automations can start from a GitHub pull request, and a cloud agent can pause to ask someone a question before it continues.

New capabilities​

  • Git: Connect a Bitbucket Cloud repository with a repository or workspace access token. TestChimp syncs SmartTests and plans through pull requests, and applies inbound repository-push and merged-pull-request webhooks.
  • Automations: Choose Pull Request as the trigger, then Opened, Pushed, Merged, or PR Comment. A comment trigger can match the comment body (starts with, contains, or does not contain); choosing PR Comment starts with “starts with /testchimp”. The run can be run QA, create tests, explore, upkeep, instrument TrueCoverage, smart smoke, cleanup, or create or run performance tests. Opened and pushed skip drafts until they are marked ready for review, and skip pull requests opened from a fork.
  • Automations: When a cloud agent asks a question and nobody has the session open, TestChimp emails and Slacks the people set on the automation. ChimpHands opens that conversation. Other agents open the workflow execution, where you pick a choice or type an answer and the run continues. Until you reply, the execution status is Waiting for you.
  • Bots: Meeting Bots in the sidebar is now Bots. The page lists MeetBot and Bonobi. MeetBot joins Meet, Zoom, Teams, or Webex as the team's QA manager—join a meeting, review past meetings, manage calendars, and edit its instructions. Bonobi shows Install until it is set up for the project you are viewing, then Configure, which opens My Bots with that project selected.

Improvements​

  • QA bot: The dashboard tip invites you to get Bonobi, your personal QA bot. It listens to git pushes and assignments and coordinates the QA work on your behalf.
  • Plans: Indie includes 250 ChimpHands credits a month.
  • ChimpHands: On a GitLab or Bitbucket project, ChimpHands in the sidebar stays visible and explains on hover that it is only supported for GitHub-connected projects.

1.0.25 - 2026-10-22​

Highlights​

New projects can be set up with Bonobi, the TestChimp QA bot on Grok. Programmatic API 2.0.0 gives agents a smaller tool set for plans, releases, test runs, and issues.

New capabilities​

  • QA bot / MCP: Agents can read plan, trial, and ChimpHands credits from get-org-capabilities, create or update a release with upsert-release, and create a test run, change its status, and find or link commit-range batches with manage-test-run. get-release lists the catalog when version is omitted.
  • QA bot / MCP: Programmatic API 2.0.0 consolidates overlapping MCP tools (ephemeral environments, scan findings, workflow executions, policies, API operations, meetings, distinct marking, execution report/history, perf runs, and release gate details) and adds list-issues plus upsert-issue. See the MCP API v2 migration.
  • Projects: Creating a project offers Via local agent (Cursor, Claude, and similar), Via Bonobi, and Via ChimpHands. Bonobi opens the Grok install page for the TestChimp QA bot, which then guides project setup. The same page is available at /bonobi. ChimpHands is labeled as TestChimp's cloud agent and shown with its own logo.

Improvements​

  • QA bot / MCP: API 2.0.0 advertises get-eaas-config as the connectivity check for ephemeral environments.
  • Review prompt: The in-app review card asks for a G2 review and notes that it takes only a few minutes.

1.0.24 - 2026-10-21​

Highlights​

TrueCoverage is a Growth plan feature. New demo projects show API contract coverage with gaps left on purpose, and moving to a smaller plan lets you choose which people and projects to keep.

New capabilities​

  • Demo project: A new demo project includes a sample messaging API and partial test coverage, so the APIs page shows which operations, fields, and response codes a test has exercised and which gaps remain.
  • Plans: Moving to a smaller plan asks you to choose the people and projects to keep, up to that plan's limits. Your own seat stays selected. Anyone you don't keep is suspended and can be restored from Team settings if you don't finish checkout.

Improvements​

  • Plans: TrueCoverage is included on Growth and the free trial (10 million events per project a month on Growth). Indie and Teams include API contract coverage, performance testing, observability, and meeting transcription. Teams organizations that already have TrueCoverage keep it.
  • API coverage: With no OpenAPI spec connected, the APIs page explains that a green suite can still leave endpoints, response codes, and fields untested, and that agents see the same gaps and can turn one into an issue or a test.
  • Billing: The plan you are on stays in place until payment succeeds. Leaving checkout unfinished does not change it. Meeting transcription hours that were included before a plan change are not billed as extra usage.

Bug fixes​

  • Billing: Completing checkout applies the plan you selected, including a move to Indie, instead of staying on the plan you already had.

1.0.23 - 2026-10-21​

Highlights​

The Indie plan is back for two-person teams, with API contract coverage, performance testing, TrueCoverage, and meeting transcription included. Atlas screen health scores now reflect bugs already found on that screen's states.

New capabilities​

  • Plans: Indie is available again for up to 2 people and 2 projects. It includes API contract coverage, k6 performance testing, TrueCoverage (1 million events a month), observability, 500 ChimpHands credits a month, and 5 meeting transcription hours a month. Extra ChimpHands usage and transcription are pay-as-you-go.
  • Plans: Teams includes the same product set as Indie, with higher limits, including 10 million TrueCoverage events per project a month. Existing Teams organizations receive API contract coverage, performance testing, TrueCoverage, and observability. Growth stays the plan for unlimited users and projects.

Bug fixes​

  • Atlas: The screen-level Overall Health Score shows a number when that screen's states already have visual, localization, performance, or accessibility bugs, instead of staying on NA. Critical bugs count the same as high-priority bugs in the score and in the priority breakdown.

1.0.22 - 2026-10-20​

Highlights​

Agents can ask open-ended questions about TestChimp from the docs knowledge base, and Semantic Canvas can paint scenario pass/fail borders from a batch the same way it already does for tests.

New capabilities​

  • MCP / agents: A new Ask about TestChimp tool answers open-ended questions about the platform from the documentation knowledge base, so coding agents can clarify philosophy and intended workflows without guessing.
  • Semantic Canvas: Execution status from a batch now applies to scenarios as well as tests—scenario nodes show pass/fail borders from linked tests in that batch (including feature-branch copies).

Improvements​

  • Navigation: Back on the test execution viewer (and related viewers) follows in-app history like the browser Back button, so opening an execution from a release test run returns there instead of jumping to the automation batch view.
  • API coverage: The Actions column header on the operation detail field list stays on one line instead of wrapping awkwardly.

1.0.21 - 2026-10-20​

Highlights​

Semantic Canvas shows scenarios and stories again after a remapping bug left the map empty, and the dashboard nudges you to set up a personal QA bot when you have not connected one yet.

New capabilities​

  • Dashboard: A new action tip invites you to get a personal QA bot—connect Grok to hear about pushes, assignments, and test runs, then approve the next QA step.

Bug fixes​

  • Semantic Canvas: Scenarios and stories with standard TS- / US- ids render on the similarity map again instead of disappearing after remapping.
  • Semantic Canvas: Viewing execution status from a batch paints pass/fail borders correctly when the batch ran feature-branch copies of your tests.
  • Git / feature branches: Ingesting tests on a feature branch creates the branch copy instead of wrongly reusing the default-branch test id.

1.0.20 - 2026-10-18​

Highlights​

Project setup status updates from Claude and other MCP clients that send short status values now apply correctly instead of silently doing nothing.

Bug fixes​

  • Project setup: Updating project-init status via MCP accepts short values such as DONE, SKIPPED, INCOMPLETE, and NOT_APPLICABLE (any case). Unrecognised values now return a clear error instead of succeeding with no change.

1.0.19 - 2026-10-18​

Highlights​

OAuth consent is smarter for bot and MCP connectors, and project setup from older CLI clients no longer fails on status updates.

Improvements​

  • Integrations: When authorizing a connection, the consent screen skips the demo project and picks your first real project if your last-used project was the seeded demo.
  • Integrations: "Use this connection as my QA bot" is pre-checked only for Grok Bot (Cursor) connectors—not for Claude or other MCP clients that reject bot scope.

Bug fixes​

  • Project setup: Updating project-init status via MCP works again with older @testchimp/cli clients that send camelCase field names.

1.0.18 - 2026-10-17​

Highlights​

Getting started is clearer when you only have the demo project, and Smart Smoke selection works again for coding-agent workflows that send suite or folder locators as plain strings.

Improvements​

  • Getting started: When your organization only has the demo project, the dashboard Quick Actions pane offers Create Project instead of the usual story, workflow, and release shortcuts.
  • Git integration: If a repository is connected but the plans or tests folder is not mapped, Plans and Sync say so and link you to map the folder—instead of claiming no repository is connected.
  • Meetbots: Meeting bots use the updated TestChimp profile picture in calls.
  • Documentation: New alternatives and comparison pages cover Meticulous, Autosana, TesterArmy, and TestChimp vs Klarent.

Bug fixes​

  • Smart Smoke: Selecting smart-smoke tests via the agent API no longer fails with HTTP 400 when the coding agent sends testSuite or folderPath as a string instead of an array.

1.0.17 - 2026-10-14​

Highlights​

Git sync now handles GitHub and GitLab rate limits gracefully: when a busy repository hits its API limit, TestChimp pauses and finishes the sync automatically after the limit resets instead of silently skipping files.

Bug fixes​

  • GitHub and GitLab integration: Large or frequent pushes no longer leave tests and plans partially synced when the Git provider's API rate limit is reached. Sync waits for the limit to reset and then completes, and a repository connected to several projects downloads each changed file only once per push, so busy repositories stay well within their limits. Connecting a repository or creating a project is never held up by a pause from background sync.

1.0.16 - 2026-10-14​

Highlights​

GitHub sync is more dependable: large or bursty pushes are now processed reliably in the background instead of occasionally being dropped, and new users can watch a short intro video right from the dashboard.

Improvements​

  • Getting started: The "Learn More" link on the How TestChimp Works tip now plays the TestChimp intro video in-app instead of sending you to the docs.

Bug fixes​

  • GitHub integration: Pushes that touch many tests, plans, or a newly created branch now sync reliably. Heavy updates are processed in the background, and simultaneous pushes to a new branch no longer fail with a conflict.

1.0.15 - 2026-10-14​

Highlights​

ExploreChimp now runs on your machine through your coding agent instead of TestChimp cloud, and joining a team from an invite is smoother—especially when you are re-invited or already signed in in the browser.

Improvements​

  • ExploreChimp: Run ExploreChimp locally via your coding agent. The app gives you a ready-to-copy prompt from SmartTests and onboarding; cloud-hosted exploration wizards and the older UI Test Studio and Test Tree Map surfaces are retired.
  • Team invitations: Accepting an email invite keeps the verification from the invite link, so you are not asked to verify again. Re-inviting a teammate who was removed earlier sends them a fresh invite.

Bug fixes​

  • Team invitations: Opening an invite or signup link while a stale browser session is still signed in no longer fails with a server error.

1.0.14 - 2026-10-10​

Highlights​

TestChimp is now more resilient: services that stall recover on their own within minutes, and merging pull requests in large, many-branch projects no longer puts the platform at risk of going offline.

Improvements​

  • Reliability: stalled platform services are now detected and restarted automatically, keeping outages short.
  • Team invitations: invite emails now include a link to set up the TestChimp QA bot on Grok Bot.

Bug fixes​

  • Git integration: merging a GitHub pull request or GitLab merge request in a project with many branches and test files no longer causes runaway memory use that could make TestChimp unavailable.

1.0.13 - 2026-10-07​

Highlights​

The automation batch list now honors your platform filter, and QA Bots have a dedicated documentation section covering how the bot swarm works and how each role on your team can put it to use.

Improvements​

  • Documentation: a new QA Bots section explains how a swarm of QA bots works alongside your team, with a how-to guide for installing and using bots as a team lead, developer, or QA engineer.

Bug fixes​

  • Executions: changing the platform selection in the automation batch list now updates the results immediately and shows only batches that ran on that platform.

1.0.12 - 2026-10-07​

Highlights​

ExploreChimp UX analysis works again for local and agent-driven Playwright runs: screen states marked during your tests are analyzed and their bugs are surfaced again.

Bug fixes​

  • ExploreChimp: screen states marked with markScreenState during local and agent-run Playwright tests were rejected before analysis. Explorations still completed, but no screens were analyzed, no credits were used, and no UX bugs were reported. They are now analyzed and charged credits as normal, with no client update needed.

1.0.11 - 2026-10-06​

Highlights​

A polish release: handing a story or scenario from the Plans tab to ChimpHands in TestChimp Studio now reliably opens the plan file, and the Grok QA bot setup now links straight to the published bot.

Bug fixes​

  • Plans: sending a story or scenario to ChimpHands from the Plans tab now opens the plan file in Studio's editor. Previously, the file could fail to open when it wasn't on your machine yet or when the plans folder path was doubled. Local edits to existing files are never overwritten.
  • QA bots: the Add bot screen's Grok option now links to the published TestChimp QA bot instead of a placeholder page.

1.0.10 - 2026-10-06​

Highlights​

Every workflow execution now has a clear owner. An assignee and an optional CC list show who needs to review or unblock a run, and the assignee is notified in the app, by email, or in Slack, whichever they prefer.

New capabilities​

  • Workflows: each workflow execution now has an assignee and an optional CC list. When a run needs plan approval, TestChimp assigns it automatically to the person who started it, if there is one. A new pane under the execution title shows the assignee and CCs as profile pictures, and an Update button lets you reassign the run or change who is CC'd. The executions list has a new Assignee column.
  • Notifications: a new Workflow execution assigned notification lets you know when a run is assigned to you. It's on by default, and you can choose whether it also reaches you by email or Slack in your notification settings. QA bots can subscribe to the same event.
  • AI agents: coding agents and QA bots connected through TestChimp's MCP server can now invite teammates to a project and update a workflow execution's assignee and CC list.

1.0.9 - 2026-10-05​

Highlights​

TestChimp's hosted MCP server now works with sign-in from popular AI coding agents and IDEs (Cursor, Claude Code, Codex, Windsurf, Kiro, and others). You can connect without pasting keys into config files, and each QA bot can now work on its own project.

New capabilities​

  • AI agents: connect to TestChimp's hosted MCP server by signing in from your agent or IDE, including apps that return to the agent after sign-in (such as cursor://). Once connected, an agent can fetch your project's credentials to set up local test runs (Playwright reporter and CLI), so it doesn't need a hand-edited config. Existing manual MCP setups keep working unchanged.
  • QA bots: each bot now works on its own project, even when several bots share one TestChimp connection. You connect once, and each bot uses its own project API key. The Add bot and sign-in screens explain this setup.

Improvements​

  • AI agents: sign-in sessions stay active when an agent refreshes its connection from several requests at once. Previously this could sign you out.

1.0.8 - 2026-10-04​

Highlights​

Every team member can now connect their own QA bot (Grok Bot) to a TestChimp project. It hears about their pushes, assignments, releases, and test runs, proposes the next QA step, and acts only after they approve.

New capabilities​

  • QA bots: a new My Bots tab in user settings lets you connect a Grok Bot to any of your projects in a single sign-in step. Pick which events it should hear about, verify its webhook, and remove a bot you no longer need. The bot works with your existing permissions. It can update stories and scenarios from your pushes and meetings, write E2E tests, plan issue fixes, triage failing test batches, and give release go / no-go heads-ups, each after you approve.
  • QA bots on your computer: requirement updates from AgentWatch, folder mapping, and local test runs run on your own machine through the TestChimp CLI. TestChimp Studio doesn't need to be installed.
  • AI agents: coding agents and bots connected through TestChimp's MCP server can now send feedback or report problems straight to the TestChimp team.

Improvements​

  • Team management: inviting a teammate past your plan's seat limit now explains the limit for your plan (free trial, Indie, or Teams) and offers an upgrade, instead of showing a generic error. Growth plans have unlimited seats and never see this prompt.

Bug fixes​

  • API coverage: OpenAPI specs larger than 1 MB now sync from GitHub and GitLab (up to 20 MB). Previously they were skipped, which left API coverage empty.

1.0.7 - 2026-10-02​

Highlights​

Branch search now finds every branch that matches what you type, and picking folders, spec files, and branches is tidier and stays fully on screen, even on smaller displays.

Improvements​

  • Git integrations: mapping a tests or plans folder now opens in a centered dialog that fits smaller screens. The mapped plans folder shows the actual name of your default branch instead of "repository default".
  • API coverage: each OpenAPI spec now shows its branch and file on a single row, with your default branch's real name. Long names are shortened, and you can hover to see the full name. Edit and remove are icon buttons at the end of the row. The file picker opens beside the button and is more compact, so it no longer runs off the screen.

Bug fixes​

  • Branch selection: searching for a branch by name now returns every match, including your own branches whose names start with "testchimp".

1.0.6 - 2026-10-02​

Highlights​

When you map your plans folder in the GitHub or GitLab integration, you can now pick the branch to sync with in the same step, and the branch list loads quickly even on very large repositories.

Improvements​

  • Git integrations: the plans folder mapping dialog now asks which branch to sync with, and the folder browser shows that branch's contents. It starts on the default branch or the branch you already configured, so existing setups are unchanged. Mapped plans folders show their branch next to the folder. You can switch branches from the same dialog without remapping the folder.
  • Branch selection: branch pickers no longer time out on repositories with many branches. They show the default branch, your configured branch, and branches active in the last 30 days, and you can search by name for any other branch.

1.0.5 - 2026-10-02​

Highlights​

Teams can now choose which Git branch TestChimp syncs their plans with, and which branch each OpenAPI spec is read from, instead of always using the repository's default branch. Git sync also stops labelling new plans that are waiting in an unmerged pull request as "deleted in remote".

New capabilities​

  • Git integrations: choose the branch your plans folder syncs with in the GitHub and GitLab integration settings, or through MCP. It defaults to the repository's default branch, so nothing changes until you pick one. Switching branches re-aligns the sync so it doesn't fill up with false changes, and if the chosen branch is later deleted, sync falls back to the default branch and tells you.
  • API coverage: when you add OpenAPI spec files on the API page, you can pick the branch each spec is read from. TestChimp remembers the branch with the file path and reads updates from it. It defaults to the repository's default branch.

Bug fixes​

  • Git sync: plan changes pushed to other branches, such as TestChimp's own sync pull-request branches or your feature branches, no longer count as synced to your plans branch. New plans waiting in an unmerged sync pull request are no longer shown as "deleted in remote", and deleting one in TestChimp is no longer hidden from outgoing changes.
  • Sign-in errors: requests made with an invalid personal access token, for example from TestChimp Studio or the Chrome extension, now get a clear "unauthorized" response instead of a server error.

1.0.4 - 2026-10-01​

Highlights​

AI agents can now search and browse your team's meetings through the TestChimp MCP and API. They get the same date, label, participant, and full-text filters as the Meetings page. Git sync also opens straight to results instead of hanging.

New capabilities​

  • Meetings for agents: agents connected through MCP or the API can list team-wide meetings, newest first. They can filter by date range, labels, participants, or participant email domains, and run full-text search over titles and transcripts, with highlighted snippets. A companion call returns the labels, participants, and domains available to filter on.

Bug fixes​

  • Git sync: starting a sync no longer leaves the page stuck loading until you refresh it. Analysis starts as soon as the project is ready, for both test and plan sync, and the page shows a clear error if it can't work out which branch to sync against.

1.0.3 - 2026-09-29​

Highlights​

The project Overview now reports accurate automation numbers for teams working across many branches, and TestChimp points Studio users to AgentWatch so their QA plan keeps pace with their coding agents.

New capabilities​

  • Action tips: users who haven't turned on AgentWatch in TestChimp Studio see a tip, on web and in Studio, that explains how it keeps user stories and test scenarios in sync with coding-agent sessions and links to the AgentWatch docs. The tip goes away once AgentWatch is enabled.

Improvements​

  • Project overview: the automation widgets load faster on projects with hundreds of branches, and the summary and charts on one page share the same data.

Bug fixes​

  • Project overview: the automation status widget counts each test once across all branches instead of showing only the tests on a single branch. A test whose suite was renamed on one branch is still counted once.

1.0.2 - 2026-09-28​

Highlights​

Meet Bots now do real work after the call. Every meeting gets an AI summary, and bots can read your stories, scenarios, and connected code to update plans or start authoring workflows. A new meetings workspace adds full-text search, filters, and per-meeting privacy controls.

New capabilities​

  • Meet Bots: each finished meeting gets an AI-generated summary, shown in a new Summary tab next to the transcript.
  • Meet Bots: bots work through multi-step tasks during and after meetings. They can read and update stories and scenarios, search related plans, browse your connected git repository, and start plan-authoring workflows from meeting decisions. While a bot works, it posts progress updates in the meeting chat.
  • Meetings: search the full text of titles and transcripts, and filter meetings by date range, participant, or participant email domain.
  • Meetings: control who can see each meeting: participants only, all team members, or participants plus specific teammates. Participants are recorded from calendar invites, so people who joined from a shared meeting room are included.
  • Meetings: save a filtered set of meetings as a meeting set and hand the whole set to agents for follow-up work.

Improvements​

  • Releases: creating or updating a release returns immediately, and release deltas are computed in the background.
  • Releases: the release list hides archived releases.
  • Navigation: Documentation moved into the settings menu to keep the sidebar uncluttered.
  • Getting started: the "Setup local agent" guide has a TestChimp Studio tab with a one-click install. No configuration is needed.

Bug fixes​

  • Workflows: executions whose plan was already approved, or that were started by AgentWatch, now close as completed instead of staying on "Plan ready" with Accept and Reject buttons still showing.

1.0.1 - 2026-09-27​

Highlights​

Meet Bots bring TestChimp into your Google Meet, Zoom, Microsoft Teams, and Webex calls to capture tribal knowledge and turn meeting decisions into QA workflows, while AgentWatch keeps stories and scenarios current by learning from your team's Cursor and Claude Code sessions.

New capabilities​

  • Meet Bots: send TestChimp bots to Google Meet, Zoom, Microsoft Teams, and Webex calls, or schedule them from a connected Google or Outlook calendar. Transcripts land in your project as labelled, organized meeting notes.
  • Meet Bots: mention the bot during a meeting to get answers grounded in your project's stories, scenarios, and test results.
  • Meet Bots: define custom bots with their own policies alongside the built-in QA and Sales bots. Meeting decisions become searchable context for planning and QA workflows.
  • AgentWatch (with TestChimp Studio): watches your local Cursor, Claude Code, and other agent sessions, spots when business rules or UX expectations get refined, and drafts a plan to update your stories and scenarios. Runs on every git push or on a schedule, with an Agent Sessions Explorer to browse, search, and re-run extractions.

Improvements​

  • Planning overview: scenarios are split into manual and automation candidates, so automation coverage insights only count scenarios meant to be automated.
  • Test runs: the test run viewer shows clearer scope tags for what each run covers.
  • Getting started: the "How TestChimp Works" tip links straight to the TestChimp Studio download, and a new tip nudges teams to record their first meeting.

Bug fixes​

  • Manual testing: notes on manual steps without a screenshot now show on a placeholder instead of having nothing to anchor to.
  • Reliability: fixed out-of-memory crashes when ingesting results and resolving coverage for large test suites.

1.0.0 - 2026-09-27​

Highlights​

TestChimp is the AI-native QA workflow layer for fast-moving teams: plans, tests, and quality signals live in your repo, and agents keep them current on every PR.

New capabilities​

  • Agent-orchestrated QA: the /testchimp skill, TestChimp Studio, Automations, and ChimpHands cloud agents plan, write, run, and repair tests on every change.
  • Tests you own: Playwright and Mobilewright SmartTests in your repo, traced to markdown requirements. No vendor lock-in.
  • Performance testing: k6 journeys linked to real scenarios, with baselines and regression comparisons.
  • Coverage intelligence: TrueCoverage matches real-user traffic to your tests, and API contract coverage shows the gaps that matter.
  • Exploratory UX analysis: ExploreChimp walks your app to find UX bugs and route them into issue triage.
  • Release governance: release checks bring manual and automated runs, DAST, and dependency scans into one go/no-go view.