UX Checks (ExploreChimp)
Short answer
UX Checks launch ExploreChimp for a release: an agent runs exploratory analysis along SmartTests that cover the release delta. Findings (perf, layout, accessibility, console, network, and more) appear on Release Checks with links to the exploration and bugs—so exploratory UX risk sits beside functional and security evidence on one page.
Why run UX Checks on a release
Functional test runs prove scenarios pass. ExploreChimp looks for quality and usability issues along real pathways—screen states via markScreenState, console/network noise, layout/a11y problems—scoped to what this ship candidate changed. That beats a standalone exploration that is hard to tie back to the version under review.
How it works
-
Release Checks → Run Release Check… → UX Checks (ExploreChimp).
-
A modal shows an agent prompt (auto-copied), for example:
/testchimp run explorechimp targeting release '<version>' -
Paste into your TestChimp-upskilled agent. The agent loads the release, selects covering UI tests for the prior→cut SHA range, stamps
TESTCHIMP_RELEASE, and runs Playwright/Mobilewright with ExploreChimp enabled. -
The Release Checks list shows the exploration (status, severity counts). Use View Exploration or View Bugs when finished.
There is no config wizard in the UI for UX Checks—knobs such as ExploreChimp sources or network filters live in project/agent config, not the release modal.
What you get
| Outcome | Where |
|---|---|
| Exploration row on Release Checks | Status and severity counts for the release |
| View Exploration | ExploreChimp exploration detail |
| View Bugs | Atlas / Issues filtered by exploration |
| Release intelligence | ExploreChimp findings panel also summarizes exploratory risk in the commit range—see Release intelligence |
UX Checks appear alongside DAST, SAST, secrets, and dependency scans in the same list—one queue for ship-candidate QA activity.
Prerequisites
- Release with git commit lineage (prior release when selecting tests for the delta)
- SmartTests covering the affected UI (ExploreChimp rides those journeys)
- TestChimp skill / ExploreChimp-enabled agent environment
- See How to run ExploreChimp and Git branch exploratory runs for broader ExploreChimp setup
Related documentation
- Release Checks overview
- ExploreChimp intro
- UX bug traceability
- DAST · SAST · Secrets · Dependency scan
- How issues get created
- Release intelligence
Frequently asked questions
What are UX Checks on a TestChimp release?
UX Checks run ExploreChimp against SmartTests covering the release delta. You copy an agent prompt from Release Checks; findings roll up on the release list with links to the exploration and filed bugs.
How do I start UX Checks from a release?
Open the release, click Run Release Check, choose UX Checks (ExploreChimp), and paste the copied /testchimp run explorechimp targeting release prompt into your upskilled agent. No scanner config wizard is required in the UI.
How are UX Checks different from security release checks?
Security checks (DAST, SAST, secrets, deps) queue a scan id and run ZAP, Semgrep, Gitleaks, or Trivy with a typed report viewer. UX Checks run ExploreChimp exploratory analysis on UI pathways and open exploration/Atlas flows instead of a ZAP-style JSON report.
Do UX Checks create issues?
Yes. ExploreChimp findings become issues with artifact and screen-state context. From Release Checks, View Bugs routes into Atlas or Issues filtered by the exploration; they also feed release intelligence ExploreChimp panels.
Why target ExploreChimp to a release instead of ad-hoc?
Release targeting selects tests for the commit range of the ship candidate and stamps the release so findings and explorations are attributable to that version on the release page and in analytics.
Can I configure ExploreChimp options when starting UX Checks?
The release modal is prompt-only. ExploreChimp environment settings (sources, network filters, and so on) come from your project/agent configuration, not from knobs on the Run Release Check wizard.
Add exploratory UX evidence to every release
Launch ExploreChimp from Release Checks, run the prompt with your agent, and triage UX findings next to security scans and test runs.