Archived

This repository has been archived on 2026-06-16. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Files

T

Chris Farhood 629261625c Remove antipattern content from UAT skill

Strip "What UAT Is NOT" section per board feedback on PRI-1487.
Focus skill on positive guidance only.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-14 05:09:28 +00:00

2.6 KiB

Raw Blame History

name, description

name	description
uat	Functional UAT procedures for Privileged Escalation Headlamp plugins. Delegates per-plugin testing procedures to UAT_PLAYBOOK.md in each plugin repository.

UAT Procedures

Purpose

This skill defines functional User Acceptance Testing for all Privileged Escalation Headlamp plugins. UAT validates that plugins work correctly in the deployed environment — by loading plugins in a running Headlamp instance and exercising their features.

Pipeline Stage

UAT is the final promotion gate before production: uat → main. Pixel Patty (UAT agent) validates the deployed application via Playwright browser testing before merging.

Per-Plugin Testing Procedures

Detailed, up-to-date testing procedures for each plugin are maintained in the plugin's own repository at UAT_PLAYBOOK.md. This is the authoritative source — do not copy procedure details into this skill.

Plugin	Repository
headlamp-polaris-plugin	`polaris`
headlamp-sealed-secrets-plugin	`sealed-secrets`
headlamp-intel-gpu-plugin	`intel-gpu`
headlamp-kube-vip-plugin	`kube-vip`
headlamp-tns-csi-plugin	`tns-csi`
headlamp-rook-plugin	`rook`
headlamp-argocd-plugin	`argocd`

Each plugin's UAT_PLAYBOOK.md contains:

Access path (sidebar entry or app bar location)
Step-by-step test actions
Expected results for each step
Pass/fail criteria
Artifact requirements (screenshots, console errors, environment info)

General Process

For every uat→main promotion:

Open the Headlamp UAT instance in the browser
Confirm the plugin appears in the sidebar or app bar
Retrieve the plugin's UAT_PLAYBOOK.md from its repository
Execute the test steps in the playbook
Capture screenshots of the running plugin at each verification step
Check the browser console for errors
Post a structured test report (see Artifacts section)

UAT Artifacts

For each plugin tested, the UAT report must include:

Screenshots of the plugin running in Headlamp — sidebar entry visible, main view loaded, at least one detail view
Test checklist — each step from the playbook marked pass/fail
Console errors — any browser console errors observed (attach screenshot if present)
Environment — Headlamp version, plugin version, browser used

Decision Criteria

Approve the uat→main PR when all applicable test steps pass
Request changes with specific failing steps and failure screenshots
Block if the plugin fails to load entirely — escalate to CTO as a deployment issue

2.6 KiB Raw Blame History