Run ExploreChimp
In brief: Run ExploreChimp along UI SmartTests to surface non-functional UX issues and refresh Atlas—optional scope.
When to use
When exploration / UX analytics is the primary goal—or as a subflow of Run QA / Upkeep. Requires UI SmartTests with markScreenState checkpoints for best results. See Exploratory testing and Screen-state annotations.
Prompt
/testchimp run explorechimp
/testchimp explore checkout
/testchimp run explorechimp for settings page
Synonyms: /testchimp explore, /testchimp run explorechimp → run-explorechimp.
Scope
Optional. Feature branch → UI touched by the branch. Default branch → since last ExploreChimp run (or ask). Or name a focus area / journey.
Policy
Optional policy for focus areas, cost gates, and when Atlas updates are required. Can be toggle-disabled per project in the Workflows UI.
Prerequisites
Depends on connect-to-test-env. Runtime: EXPLORECHIMP_ENABLED, API key, batch correlation via @testchimp/playwright.
What it does
Runs ExploreChimp on selected UI specs, analyzing DOM, screenshots, console, optional network and metrics along scripted journeys—surfacing non-functional issues scripts miss.
See also
FAQ
Do I need SmartTests before exploring?
SmartTests with markScreenState checkpoints give the best GPS for journeys; Screen-State Discovery recipe helps when no tests exist yet.
What bugs can ExploreChimp find?
Non-functional UX issues—visual regressions, broken assets, harsh layouts, console errors, network failures, and performance threshold breaches.
How is this different from /testchimp test?
Explore prioritizes analytical journeys and bug surfacing; test balances functional SmartTest authoring and infra with optional exploration.