TestChimp

Troubleshooting: fetch logs for a BunnyShell workflow job.

Return the project's BunnyShell (Environment-as-a-Service) settings. Secrets are never returned. Skill connectivity check: prefer this over ephemeral-environment action=CONFIG.

Fetch SmartTest execution history for a testId (top 5 recent runs), an optional platform-rooted folder/file scope, or a scenario when scenarioId is set. Prefer testId when you have it from fetch-execution-report. Typically omit environment to avoid env scoping. Use branchName and scope.filePaths as for coverage. Optional platform (web|ios|android) and dimensionFilters narrow results. Set aggregate=true for suite timing stats (testCount, timedTestCount, sumSuccessMeanSecs, slowTestCount) instead of per-test history.

Return git provider, repository, mapped plans/tests folder paths, and plans branch (empty = repository default) for the project.

Fetch a TestChimp issue (bug) by ordinal id. Accepts flexible issueId formats: #B-123, B-123, #B123, B123, or plain 123. Returns title, description, status, linked entities, artifact references, and short-lived signed URLs for GCS attachments/screenshots.

Fetch a manual test session by id. Returns project id, title, environment, steps (playwright commands, signed screenshot URLs, notes), and linked scenario ordinal ids. Use when authoring a SmartTest from a recorded manual session.

Fetch a cloud-synced Meeting Bots transcript by meeting id (calendar event id, or URL hash for ad-hoc meetings). Returns title, start time, post-meeting summary, and transcript. Use summaryOnly to fetch just the summary (much smaller) and pull the full transcript only when the summary is not enough. Prefer local ~/.testchimp/data/meetings/<meeting-id>/transcript.md when present on Studio / the recording machine.

List a team member's open QA work in this project: manual test scenarios assigned to them in test runs (with testRunUrl), issues assigned to them (status, severity, due date, issueUrl), and SmartTests they authored that still await verification. With an OAuth token the user is the token's user; with an API key pass userId. Use for daily reminders and 'what should I work on' questions.

Fetch the organization's enabled capabilities (e.g. TRUE_COVERAGE, API_CONTRACT_COVERAGE), freeTrialActive / trial, planLabel, and chimphandsCredits. Call before relying on TrueCoverage / API contract coverage / ChimpHands features so playbooks can soft-skip gated insights instead of failing. Authenticated via project API key.

Fetch a file under the mapped plans root from the platform by relative path (no git required). Primary use: load a workflow execution plan named in a Continue Locally / implement prompt before falling back to the repo copy. filePath is relative to the plans mapped root (leading plans/ is stripped). Under workflow_plans/, filenames are coerced to *.plan.md. Response: found (false if missing), supportFileId, filePath (canonical), filetype, content.

Fetch or list workflow policy files from the platform POLICY_FILE store. Pass policyFileName (e.g. run-qa.policy.md, coerced to *.policy.md) to fetch one file. Omit policyFileName to list (optional workflowId). List marks isDefault when filename is <workflow-id>.policy.md.

Normal (non-bot) OAuth connections: fetch the project key local test runners (Playwright reporter, CLI, k6) need. Returns {projectId, projectName, projectApiKey, userId, backendUrl, ingressUrl} for the connection's project (the MCP URL's ?projectId= when set, else the one picked on the consent page). To persist the runner key without putting it in a shell command: local stdio MCP should call save-workspace-creds; hosted / plugin agents should write <repo>/.testchimp/mcp.json themselves (mode 0600, dir 0700) from this response and never print projectApiKey. This tool still returns projectApiKey…

Return project-init progress for the current project (platform comms, folder mapping, test env, CI, optional imports).

Project-wide QA posture snapshot: releases (version, lifecycleStatus, due date, passed / failed / blocked / not-attempted counts), issues (active, inProgress, blocked, openBySeverity), activeTestRuns with result counts, and testsAwaitingVerificationCount. Use for weekly QA digests and release-health questions; summarise for the reader's role rather than dumping raw JSON.

Fetch or list releases in the current project. Pass version for one release; set detail=GATE for gate-oriented details (scope, per-environment priority×status test stats, open issue stats, scan summaries, in-scope scenario/issue records). Omit version to list: optional environment, pageSize, pageToken, excludeArchived. Authenticated via project API key.

Fetch requirement (scenario) coverage under an optional platform-rooted folder scope (tests/... or plans/...). Use scope.filePaths or scope.folderPath (platform tests/plans roots). Omit branchName for cross-branch coverage (aggregates branch copies; execution jobs deduped by stable hash of tests-root-relative path + test name). Pass branchName only when results must be limited to one Git branch. Optional platform (web|ios|android) filters rollup. For top-N gap recommendations: set scenarioLifecycleStatuses, considerScenarioPriority / considerSemanticCoverage, and limit; prefer response rankedS…

Fetch the stored requirement quality report (metrics + findings with user states) for a user story or test scenario. Use before local DeFOSPAM to dedupe: do not re-report findings already IGNORED or APPLIED (match by fingerprint). Pass subjectType STORY|SCENARIO plus subjectEntityId or ordinalId (numeric part of US-<n> / TS-<n>). When no prior report exists, response still includes report.subject with resolved subjectEntityId.

Fetch security scan config by scan id (detail.dastCheckConfig / detail.sastCheckConfig / detail.depsCheckConfig / detail.leaksCheckConfig, release label, status). Pass scanId (id is accepted as an alias). Used by /testchimp run security scan. For DAST honour allowActiveScan / useEphemeralSandbox / scope on dastCheckConfig.

Fetch lifecycle_fields for user stories and/or test scenarios by ordinal id (DB only; no markdown). Pass scenarioIds / storyIds as lists of bare ordinals (canonical) or prefixed forms (TS-107, #US-12). Use after identifying scenarios in scope for create-tests to read verification_strategy (auto|manual) and skip manual ones.

Fetch test scenarios from the TestChimp platform by ordinal id (numeric part of TS-<n>) and/or external TMS ids (e.g. C12345, PROJ-101 — server strips prefixes and matches numerical part). Returns full plan markdown content, title, platform file path, linked user story ordinal ids, and external_source / external_system_id when present. Use when plan files are not yet synced to the repo, or when linking imported tests to scenarios by TMS id.

TrueCoverage next-event tree after an event (ListChildEventTreeRequest). Requires eventTitle, baseScope (environment + timeWindow); optional coverageScope for PRESENT/ABSENT. Note: metadataFilters on scopes are ignored for transition stats. Field names are baseScope/coverageScope (not baseExecutionScope).

TrueCoverage drill-down for one event (GetEventDetailsRequest). Requires eventTitle plus baseExecutionScope (environment + timeWindow). Optional comparisonExecutionScope for coverage columns (automationEmitsOnly on comparison). Same timeWindow / platform rules as get-truecoverage-events.

List metadata keys for a given event title (ListEventMetadataKeysRequest). Pass eventTitle (CLI: --event-title or json-input).

TrueCoverage daily time series for one metric (EventTimeSeriesRequest). Requires baseExecutionScope (environment + timeWindow). Optional eventTitle and metricType: SESSION_COUNT | RELATIVE_FREQUENCY | PERCENTAGE_TERMINAL_EVENT | SESSION_POSITION | TIME_TO_NEXT_EVENT | REVERSE_INDEX | TIME_FROM_START | TIME_TO_END | TIME_SINCE_PREVIOUS_EVENT.

TrueCoverage detailed transition stats between two events (GetDetailedEventTransitionSummaryRequest). Requires eventTitle, nextEventTitle, baseScope (environment + timeWindow); optional coverageScope. metadataFilters on scopes are ignored. Uses baseScope/coverageScope field names.

TrueCoverage event funnel summaries (ListEventsRequest). baseExecutionScope is the real-user / primary environment; optional comparisonExecutionScope for coverage (set automationEmitsOnly:true on comparison for test-tagged emits only). Each scope needs environment + timeWindow: { relativeWindow: "604800s" } or { fixedWindow: { startTime, endTime } } (RFC 3339). Optional platform: web|ios|android or WEB_/IOS_/ANDROID_EXECUTION_PLATFORM. Prefer list-rum-environments first.

List session-level metadata keys observed in RUM for TrueCoverage filters.

Fetch user stories from the TestChimp platform by ordinal id (numeric part of US-<n>). Returns full plan markdown content, title, and platform file path for each found story. Use when plan files are not yet synced to the repo.

List or fetch workflow executions. Omit identity args to list (optional workflowId, limit, offset, pendingApprovalOnly, assignedToMeOnly). Pass workflowExecutionId for one execution (includeActions defaults true). Pass workflowId + latestOnly=true for the last run on an optional branch / userId (since-last-run scoping).

Record a scenario execution result (manual or imported). Provide scenarioOrdinalId and/or externalId, plus result (SMART_TEST_EXECUTION_*). Optional release, testRunLabel, environment, platform, notes. Response is the ingested execution record.

Invite teammates (by email) to the TestChimp organization so they can access this project. Each invitee joins as a Viewer and gets a sign-up email. Needs an OAuth user session whose user is an org admin: QA bots call this MCP tool through the connector with their binding arguments (the CLI's --bot key can't invite). Returns a per-email outcome (INVITED, ALREADY_MEMBER, ALREADY_INVITED, FAILED with failureReason) and teamSettingsUrl for role changes / seats. Only call with emails the user explicitly confirmed.

List recorded API operation interactions. Requires testId and/or operationId. Defaults to REAL interactions; limit is capped at 100.

Troubleshooting: list BunnyShell platform events for an environment.

Troubleshooting: list BunnyShell workflow jobs for an environment.

List distinct execution-job dimension values (platform, device family, OS version, screen resolution, orientation) for filtering get-execution-history. Optional scenarioId, environment, release, timeWindow, branchId, branchName, dimensionFilters, dimension.

Search / filter TestChimp issues in the current project. Optional filters: searchText, statuses, severities, assignee, assignees, labels, release, limit, offset, ordinalIds. Use get-issue-details for one issue by ordinal. Authenticated via project API key.

List / search cloud-synced Meeting Bots meetings, newest first, like the Meetings page filters + search. Team-wide meetings only (visibility: all team members). Filters: from / to (YYYY-MM-DD, ISO datetime, or epoch millis; inclusive), labels, participantKeys (user id or email), participantDomains, searchText (full-text over title + transcript; hits include a searchSnippet with matches wrapped in ⟦ ⟧). Returns meetingId, title, startMillis, labels, participants, summaryStatus; page with nextPageToken. Set includeFilterOptions=true for exact label / domain / participant catalogs. Pass meetingSe…

List promoted performance baselines, optionally filtered by TestChimp id.

List performance runs, optionally filtered by TestChimp id, JOURNEY/COMPOSITE kind, branch, profile, dataset, LLM mode, or environment. Pass runId to fetch one run (optional includeRaw for the raw payload).

Find JOURNEY and, by default, COMPOSITE performance tests related to scenario titles and/or TestChimp ids.

List distinct RUM environment tags for this project. Call this first to choose environment values for TrueCoverage ExecutionScope.environment (e.g. QA, production).

Fetch the project's screen/state vocabulary (relational atlas) for SmartTests and traces. Optional environment field is accepted for forward compatibility; v1 may be project-global.

List semantically nearby entities across types (Story/Scenario/Test/Issue/Event). TEST uses TestLocator; STORY/SCENARIO/ISSUE use sourceOrdinalId; EVENT uses sourceEventTitle. Response TEST hits include TestLocator (never platform test_id).

List semantically similar SmartTest pairs in scope using TestLocators (no test_id). Pairs are deduped (A→B only when A.testId < B.testId). Distinct-marked pairs are excluded.

Time-series test-planning trends for a release/environment/branch. Optional coverageScope, scenarioId[], userStoryId[], userStoryIdInScope[], platform, timeWindow, branchId.

List in-scope test scenarios (ordinalId + title only) for exactly one locator: a named test run, a release label, or a platform plans folder/file path. Does not return markdown — use get-test-scenarios for detail by known ordinal. Use when executing tests for a plans path, release, or named test run.

List SmartTests whose latest executions still need human verification before they earn a verified badge (testId, testName, filePath, scenarioId / scenarioOrdinalId / scenarioTitle, verificationStatus NOT_VERIFIED or VERIFIED_STALE, reportedAtMillis, workflowExecutionId). Optional userId narrows to tests authored for that user (defaults to the OAuth token's user); optional limit. Use after writing E2E tests to prompt the user to verify the executions.

List supported TestChimp workflows with Active / Disabled / Missing Config status for the project.

Create or update a named test run. Omit id to create (release required). Optional title, environment (server defaults QA), dueDate, status (ACTIVE|COMPLETED|ARCHIVED), batchInvocationIds, and commitRange: FIND (discover batches in the prior-release-cut to current-cut SHA range without attaching) or LINK (attach the unlinked ones). Response includes id, summary, created, link counts, commit SHAs, discoveredBatchInvocationIds and unlinkedBatchInvocationIds.

Mark user stories and/or test scenarios implementation-complete in platform lifecycle (DB only; does not rewrite plan markdown). Use scenarioOrdinalIds / userStoryOrdinalIds (numeric parts of TS-<n> / US-<n>).

Report existing SmartTests that an agent patched so humans can re-verify. Always send per-test confidence 0–100 (higher = less need for human review). Do not read project config. Call only from fix-test-execution after test-incorrect patches (never from run-qa / create-tests; never for product-broken cases). Optional agentTraceability / workflowExecutionId / gitCommitSha / branchName.

Promote a performance run as the baseline for an environment class (runId + envClass).

Register or replace this QA bot's profile and event subscriptions atomically (mutating — confirm with the user first). role: QA_LEAD | PM | QA_ENGINEER | DEVELOPER. responsibilities: the user's own words. capabilities: REQUIREMENTS_UPDATE, E2E_AUTHORING, ISSUE_FIX, MANUAL_TEST_COORDINATION, TEST_BATCH_FIX, QA_POSTURE. subscriptions: [{eventType, filters:[{field, op:'eq', value}]}] where value may be 'me' (e.g. git-push author=me, issue-assigned assignee=me, e2e-batch-completed). Derive subscriptions from capabilities per the testchimp skill's bot onboarding guide. botId defaults to the bot-id …

Report a mutating agent action under a stable workflow-execution-id (ULID). First call for an id creates the workflow_executions row; later calls append Activity timeline rows (AGENT_WORKFLOW_ACTIVITY). Actions land on the entity's Activity timeline (plans, issues, SmartTest file). entityType: USER_STORY | SCENARIO | SMART_TEST | POLICY | ISSUE | TEST_EXECUTION | TEST_INVOCATION_BATCH | EXPLORATION | EVENT | WORKFLOW. actionType: CREATED | UPDATED | DELETED | ANALYZED | IMPLEMENTED | ACTION_COMPLETED | ACTION_FAILED. Identity: SMART_TEST uses `test` (TestLocator: folderPath/fileName/testSuite/…

Upload a DeFOSPAM / requirement quality analysis report for a user story or test scenario (local-agent path). Pass full RequirementQualityReport JSON via --report-file or --json-input {"report":{...}}. report.subject.subjectEntityId is required; use --subject-type + --ordinal-id to resolve via get-requirement-quality-report, or set subjectEntityId explicitly. Backend merges IGNORED/APPLIED findings carry-forward on re-report.

Upload a scanner JSON report for a security scan. Pass --id, --scanner (DAST|SAST|DEPS|SECRETS), and --report-file. DAST = ZAP Traditional JSON; SAST = Semgrep CLI JSON; DEPS = Trivy JSON; SECRETS = Gitleaks JSON. Backend parses, dedupes by bug hash, and inserts new SECURITY bugs linked to the scan. Optional markCompleted=true sets the scan COMPLETED after a successful ingest; otherwise the playbook calls update-scan-progress COMPLETED.

Save the project API key for local runners in <folder>/.testchimp/mcp.json (Studio format: mode 0600, dir 0700, .testchimp/ gitignored) and map the folder in ~/.testchimp/projects.json. Fetches the key with the current MCP auth — do not pass the key, and the response never includes it. Local stdio MCP only (omitted on hosted mcp.testchimp.io). Hosted / plugin agents: call get-project-credentials and write <repo>/.testchimp/mcp.json with a file-write tool (never put the key in a shell command).

Select a SmartTest smoke subset from relatedTests / taggedTests / suiteCandidates with optional includeTags, maxTimeBudgetMins, maxTests, suitePercentage, branchName, environment.

Send feedback to the TestChimp team ("contact us" for agents). Use when you hit a TestChimp bug or confusing error, the user struggles with or complains about TestChimp, a capability is missing, or the skill / docs were wrong or unclear. category: BUG | USER_STRUGGLE | FEATURE_REQUEST | DOCS_GAP | OTHER. message: what happened, in plain words. context: what you were doing (workflow, tool or command, error text, CLI / skill versions). agentName: your host, e.g. Cursor, Claude Code, Grok QA bot. Never include secrets, API keys or tokens. Mention to the user that you sent it.

Mark or unmark two same-type entities as distinct (distinct defaults true). TEST uses TestLocators (focusTest + otherTest or distinctTest); STORY/SCENARIO/ISSUE use ordinals; EVENT uses titles. Set distinct=false to remove a mark.

Update mapped plans/tests folder paths (and optional repository / plans branch) on the platform. Agent scaffolds folders in a PR; this records platform mapping.

Update lifecycle_fields.status for one user story or test scenario (DB only; does not rewrite plan markdown). entityType: story | scenario; ordinalId: numeric US-/TS- ordinal; status: draft | ready | in progress | blocked | done | archived. Used after /testchimp implement to set status to ready (unless policy overrides).

Merge project-init progress fields for the current project. Pass a `status` object with snake_case keys (platform_comms, folder_mapping, connect_to_test_env, ci_wiring, and optional import_plans, import_tests, smoke_validation). The server recomputes overall_complete when required items are DONE — do not send it (overallComplete / overall_complete are ignored). Legacy camelCase keys from older skills are forwarded to the backend.

Update a scan's status. status must be one of: QUEUED, IN_PROGRESS, COMPLETED, EXCEPTION. Call IN_PROGRESS when starting. Each scan is a single checker type: the category playbook sets COMPLETED after a successful report-scan-findings (or EXCEPTION on hard failure).

Sync a test scenario markdown file to the platform after local edits. Requires frontmatter id: TS-<n> and story: US-<n>. Missing either returns an error telling you to call create-test-scenario first. Parses frontmatter and updates linking if story changes. Optional agentTraceability records UPDATED Activity inline.

Sync a user story markdown file to the platform after local edits. Requires frontmatter id: US-<n> (platform-issued). Missing id returns an error telling you to call create-user-story first. Parses frontmatter (id, title, priority) and updates the linked support file and entity. Optional agentTraceability records UPDATED Activity inline.

Change the assignee and/or CC list of a workflow execution. The caller (OAuth user, or the bot's owner with --bot) must be the current assignee or an org admin (admin override needs OAuth, not --bot); anyone on the team may assign an unassigned execution, and a CC'd user may remove themselves. 409 means someone else changed it: re-read with get-workflow-executions and retry. Assignee / CC accept team member user ids or emails. New assignees and CC'd users get a workflow-execution-assigned bot event plus email/Slack per their notification settings. Only call after the user explicitly approved t…

Upload a file (e.g. agent screenshot evidence) to explore-snaps and return a stable view URL. Pass --file <path>; optional --filename and --content-type. Response includes viewUrl to paste in chat.

Create or update a TestChimp issue in the current project. Omit issueId and pass title to create. Pass issueId (same flexible formats as get-issue-details) plus patch fields to update — including status (ACTIVE | IGNORED | FIXED | DUPLICATE | IN_PROGRESS_BUG | ARCHIVED_BUG | BLOCKED) and optional ignoreReason. For /testchimp implement TASK_ISSUE creates: set labels=["TestChimp Implement"] (not source), severity from task priority, category (e.g. FUNCTIONAL), and linkTargets for STORY and/or SCENARIO ordinals. For /testchimp fix issue: set IN_PROGRESS_BUG after applying a code fix; set FIXED on…

Create or update any file under the mapped plans root on the platform by relative path (no git commit/push required). Primary use: upload workflow execution plans at knowledge/workflow_plans/<workflow-id>/<workflow_execution_id>.plan.md after the Plan phase. filePath is relative to the plans mapped root (leading plans/ is stripped). Under workflow_plans/, filenames are coerced to *.plan.md and stored as WORKFLOW_EXECUTION_PLAN. Response includes supportFileId, filePath (canonical), filetype, created. Blocking step before Execute for cloud agents.

Create or update a workflow policy file on the platform (plans/knowledge/policies/*.policy.md). policyFileName is coerced to *.policy.md (same as get-policies). Prefer after writing the file locally so the policy is available immediately (git sync also works later).

Create or update a release catalog entry. version is required. Optional gitCommitSha, priorReleaseVersion, releaseType (MAJOR|MINOR|HOTFIX), lifecycleStatus, environment (create only), dueDateMillis and branchId (update only, int64 strings). Response is { release, created }.

Merge screen names and state strings into the project's relational atlas (idempotent upsert). Body uses camelCase screenStates: [{ screen, states: string[] }, ...] per UpsertScreenStatesRequest.