Skip to content

Skill to set up PR for testing#118

Open
DavertMik wants to merge 9 commits into
masterfrom
feat/setup-pr-for-testing
Open

Skill to set up PR for testing#118
DavertMik wants to merge 9 commits into
masterfrom
feat/setup-pr-for-testing

Conversation

@DavertMik

@DavertMik DavertMik commented May 27, 2026

Copy link
Copy Markdown
Contributor

Updates workflow files to

  • run regression manual tests
  • regression automated tests
  • CI system agnostic

Coverage skills unified into qa-test-coverage-map

Merged manual-coverage + automation-coverage into one skill. Manual and
automated tests of a project now share one coverage map; files are split
per project, not per test kind.

Coverage maps are named by content so CI knows what's inside without opening them:

File Contains
coverage.<slug>.yml manual + automated
coverage.<slug>.manual.yml manual only
coverage.<slug>.e2e.yml automated only

setup-pr-testing reads the suffix to pick the reporter --kind:
--kind manual (manual only), --kind mixed (combined), or none (e2e only),
and creates one regression run per coverage map on merge.

README, testomatio-flow, REPORTER_CONTRACT, and the evals are updated for
the new skill name and naming scheme.

🤖 Generated with Claude Code

DavertMik and others added 4 commits May 20, 2026 10:45
…-remote

- PR open: post a notice comment with affected manual/automated test counts
  (reporter run --filter-list), no runs created, never blocks the PR
- PR merged: create the manual run (pending) and prepare the automated run as
  a shared run titled by commit (reporter start), not executed
- deploy done: launch the prepared run on a Testomat.io CI profile via
  reporter run --remote, replacing cross-repo dispatch
- rewrite REPORTER_CONTRACT.md and evals for the three-phase model

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Comment thread skills/setup-pr-testing/SKILL.md Outdated
tests run there and report back into the same prepared run.
```

Every phase is **change-aware**: a coverage map (`coverage.*.yml`) maps source

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why rows are so short?)

Comment thread skills/setup-pr-testing/SKILL.md Outdated

The big shift from older setups: **execution moved to after merge+deploy**, the
**PR-open step is now just an informational comment**, and **automated tests are
launched through Testomat.io's `--remote` CI profile** instead of this repo

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ca't find info about this in docs...

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's a new feature!

DavertMik and others added 5 commits May 31, 2026 12:03
The deliverable is a working pipeline committed to the project's own CI
system. The skill never executes the reporter, runs tests, or creates runs
itself — every reporter command is written into the pipeline for CI to run.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Aligns the skill with the reporter change: start prints only the run id to
stdout when --format is set, so capture with --format id instead of tail -n1.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Merge manual-coverage and automation-coverage into a single
qa-test-coverage-map skill: manual and automated tests of one project
go in one map. Split files per project, not per test kind.

Coverage maps are now named by content so CI knows what is inside:
  coverage.<slug>.yml         manual + automated
  coverage.<slug>.manual.yml  manual only
  coverage.<slug>.e2e.yml     automated only

Update setup-pr-testing to read the filename suffix and pick the
reporter --kind flag accordingly: --kind manual (manual only),
--kind mixed (combined), or none (e2e only). One regression run is
created per coverage map on merge.

Refresh README, testomatio-flow, REPORTER_CONTRACT, and evals for the
new skill name and naming scheme.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Reconcile the coverage-skill unification on this branch with master's
skill-rename refactor (#126).

Conflict resolutions:
- Keep the unified qa-test-coverage-map skill; drop master's separate
  qa-manual-tests-to-code-coverage and e2e-test-coverage-mapping (the
  unified skill supersedes both).
- README and senior-qa-testing-workflow: adopt master's renamed skill
  names, collapse the two coverage rows into the single qa-test-coverage-map.
- Align qa-test-coverage-map and setup-pr-testing to master's conventions:
  cache dir .testclaw-context/ -> .testclaw/, and renamed skill references
  (project-scan -> scan-automation-project, sync-cases ->
  sync-test-cases-with-tms, generate-cases -> qa-write-test-cases,
  reporter-setup -> qa-e2e-tests-reporting).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants