evidence-driven-testing
/evidence-driven-testing
Records visual proof while testing UI behavior — screen recording with structured test/assertion annotations — then posts the video and a results summary to the PR and tracker issue. Use whenever a UI change needs verifiable evidence that it works, instead of prose claims.
- Author
- The-Utopia-Studio ↗
- Repository
- skills ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Records visual proof while testing UI behavior — screen recording with structured test/assertion annotations — then posts the video and a results summary to the PR and tracker issue. Use whenever a UI change needs verifiable evidence that it works, instead of prose claims.
Original author description
Records visual proof while testing UI behavior — screen recording with structured test/assertion annotations — then posts the video and a results summary to the PR and tracker issue. Use whenever a UI change needs verifiable evidence that it works, instead of prose claims.
How it works
- Inputs
- Instructions
- Guardrails
SKILL.md preview
--- name: evidence-driven-testing description: > Records visual proof while testing UI behavior — screen recording with structured test/assertion annotations — then posts the video and a results summary to the PR and tracker issue. Use whenever a UI change needs verifiable evidence that it works, instead of prose claims. compatibility: Requires a GUI environment with screen recording, an authenticated browser session for the app under test, and gh (GitHub CLI) or equivalent for posting evidence. metadata: version: "1.0" --- # Evidence-Driven Testing Record annotated screen-recording proof of UI behavior, then attach it to the PR and tracker issue. ## Inputs - **Test targets** (required): The behaviors/flows to verify, phrased as testable statements. - **PR / issue** (optional): Where to post the evidence. If omitted, deliver to the requester only. ## Instructions ### 1. Prepare the screen - Maximize the browser/app window; close popups, notifications, and extra panels. - Navigate to the starting state (logged in, correct page) BEFORE recording, unless setup itself is under test. ### 2. Start recording - Begin the screen recording before the first meaningful action. - Add a `setup` annotation describing the starting context, e.g. "Logged in, navigating to connectors page". ### 3. Annotate as you test - At each named test's start, add a `test_start` annotation in Jest style: `It should execute the tool directly when permission is 'always'`. - After each check, add an `assertion` annotation with result `passed`, `failed`, or `untested`. - Rules for assertions: - One assertion per meaningful state change — consolidate, don't annotate per UI label. - Use "Precondition: ..." assertions to establish starting state. - Keep under ~80 characters, high-signal. - If a test cannot run (missing prerequisite, expired auth window), mark it `untested` with the reason — never skip silently. ### 4. Stop and review - Stop recording after the final assertion. - Confirm the recording captured the key moments before sharing. ### 5. Post the evidence - Write a short report: what was tested, environment + exact commit, pass/fail per test, caveats. - Post the video + summary as a PR comment (embed in the PR description if it's your PR). - Attach the same video to the tracker issue (Linear/Jira) with a one-line result. - Send the report + recording to the requester. ## Guardrails - Never record a half-covered or tiled window — maximize first. - When verifying a fix, show or reference the old failure alongside the new success. - Always state the exact commit/branch/deployment tested against.
Versions
The database has no other skills named evidence-driven-testing.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 03c09d8014e1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100prove-work-on-github
Prove that work claimed on a pull request or issue actually landed and is sound, with verifiable evidence a reader can independently re-check. A claim is narrative; a receipt is proof. Use when deciding what evidence a change owes, capturing it (screenshots, GIFs, logs, database… - 100recording
Record evidence of a web app — an operation video, screenshots and a runbook — for a pull or merge request, a report, or a hand-off. Use when someone asks for proof that a change works, hands over an MR/PR link, or describes a page and the steps to capture on it. - 100rust-testing-strategy
HASH Rust testing strategy. Use when writing Rust unit, integration, or snapshot tests, or choosing assertion and test-organization patterns. - 100argos-upload
Upload a screenshot, an image or a screen recording to Argos and get a shareable URL plus ready-to-paste Markdown, so it can be embedded in a pull request, an issue, a changelog or a chat message — or attached to a branch or pull request, where Argos posts and maintains the… - 90dev10x-qa:qa-publish
Publish a finished QA run to the ticket and the PR as a readable verdict with a watchable video and inline screenshots — instead of raw files left in a temp directory, a ticket comment that never reaches Jira watchers, or evidence that silently claims coverage the run never had.… - 100argos-upload
Upload a screenshot, an image or a screen recording to Argos and get a shareable URL plus ready-to-paste Markdown, so it can be embedded in a pull request, an issue, a changelog or a chat message — or attached to a branch or pull request, where Argos posts and maintains the…