Skip to content

docs(ai): add test-placement skill for the plugin testing strategy (RHIDP-13501)#2726

Open
gustavolira wants to merge 2 commits into
redhat-developer:mainfrom
gustavolira:rhidp-13501-test-placement-skill
Open

docs(ai): add test-placement skill for the plugin testing strategy (RHIDP-13501)#2726
gustavolira wants to merge 2 commits into
redhat-developer:mainfrom
gustavolira:rhidp-13501-test-placement-skill

Conversation

@gustavolira

@gustavolira gustavolira commented Jul 2, 2026

Copy link
Copy Markdown
Member

Summary

Adds a test-placement Claude Code skill (.claude/skills/test-placement/): when a developer asks "where should I test this?", the assistant gathers the context and proposes the right repo (rhdh-plugins / rhdh-plugin-export-overlays / rhdh), the right test layer (L1 unit → L4b cluster e2e), the location, and how to scaffold the test.

It encodes the per-repository testing responsibility split consolidated on epic RHIDP-13501: artifact bugs belong here (native smoke #2714 — install from OCI + startTestBackend boot, workspace mode, bundle presence) · source bugs → the plugin's source repo · integration/UI-render bugs → the rhdh cluster-free harness (rhdh#5005; this repo has no app to render into) · platform bugs → cluster e2e. Guiding rule: the cheapest environment that catches the bug wins. Includes the researched dead-ends (catalog-extending modules in minimal startTestBackend, local-path artifacts, standalone Scalprum host) so devs don't burn time on them.

Sibling PRs add the same skill to rhdh (rulesync-generated) and rhdh-plugins.

Related

Epic RHIDP-13501 · #2714 · rhdh#5045 · rhdh#5044 (layer matrix) · rhdh#5005

🤖 Generated with Claude Code

Tooling note (review follow-up)

This lands for Claude Code only (.claude/skills/) on purpose: this repo has no rulesync setup (unlike rhdh, where the sibling PR generates Claude/Cursor/OpenCode copies from one source), and hand-maintaining parallel copies invites drift. Adopting rulesync here is the right follow-up if broader tool coverage is wanted.

… ecosystem

Adds a Claude Code skill that, given the context of a change or bug,
proposes the right repository (rhdh-plugins / rhdh-plugin-export-overlays /
rhdh), the right test layer (L1 unit -> L4b cluster e2e), the location, and
how to scaffold the test. Encodes the per-repo testing responsibility split
consolidated on epic RHIDP-13501: artifact bugs belong here (native smoke,
overlays#2714), source bugs in the plugin's source repo, integration/render
bugs in the rhdh cluster-free harness, platform bugs in cluster e2e.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gustavolira gustavolira requested review from a team, gashcrumb and kadel as code owners July 2, 2026 19:41
…tion, path prefixes

- Mark harnesses that are still in review and instruct the assistant to
  verify paths exist on main before recommending them.
- Describe the overlays native smoke's real interface: yarn smoke
  --dynamic-plugins <file> [--out] (no --workspace flag; the harness does
  not read workspaces/*/metadata — a workspace run is a dp.yaml listing its
  oci:// refs).
- Replace the fork-only RHIDP-13235 branch pointer with the closed PR
  rhdh#4864; prefix every path with its repo (rhdh:/overlays:/plugins:) and
  use full URLs for cross-repo docs; fix the skopeo-on-macOS claim; name the
  Docker smoke location; move PR numbers to a References section with
  status; add trigger phrases to the frontmatter description.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sonarqubecloud

sonarqubecloud Bot commented Jul 2, 2026

Copy link
Copy Markdown

@github-actions github-actions Bot added the non-workspace-changes PR changes files outside workspace directories label Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

non-workspace-changes PR changes files outside workspace directories

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant