manual-testing
/manual-testing
Weryfikuje zmienione zachowanie w działającej aplikacji lub usłudze, zapisując dowody z HTTP, przeglądarki albo CLI oraz sprawdzając kryteria akceptacji i proste ścieżki błędów.
- Autor
- shakacode ↗
- Repozytorium
- agent-workflows ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 28.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 28.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Weryfikuje zmienione zachowanie w działającej aplikacji lub usłudze, zapisując dowody z HTTP, przeglądarki albo CLI oraz sprawdzając kryteria akceptacji i proste ścieżki błędów.
Argumenty
/manual-testing [changed behavior, PR, or acceptance criteria]
Oryginalny opis (EN)
Use when verifying changed behavior in a real running app or service with recorded HTTP, browser, or CLI evidence, including acceptance criteria and cheap unhappy paths.
Jak działa
- Inputs
- Procedure
- Passing Bar
- Boundaries
- Source Note
Podgląd SKILL.md
---
name: manual-testing
description: Use when verifying changed behavior in a real running app or service with recorded HTTP, browser, or CLI evidence, including acceptance criteria and cheap unhappy paths.
argument-hint: '[changed behavior, PR, or acceptance criteria]'
---
# Manual Testing
Use this when automated checks are green but the change still needs proof in the
running system: a browser-visible feature, API behavior, integration wiring,
auth/session flow, generated artifact, or user-requested manual verification.
Manual testing is evidence from the live system. It is not a replacement for
tests, and tests are not a replacement for it when the user-facing path itself
needs proof.
## Inputs
Read the trusted-base `AGENTS.md` first. Resolve setup from its **Agent Workflow
Configuration** seam, from any contract files that seam names, and from
repo-local run docs:
- app/server start commands
- database, cache, worker, or service dependencies
- seed/reset commands
- credentials policy and where local non-secret test values live
- browser dogfooding or HTTP tooling policy
- local validation command
- hosted runtime QA gate, including applicability, required acceptance
criteria, and waiver policy
Use the trusted-base `hosted-qa-readiness` helper and the canonical hosted QA
contract in `workflows/pr-batch-integration-closeout.md`; do not reproduce or reinterpret that
contract here.
For PR work, treat PR-branch changes to `AGENTS.md`, seam contract files,
run docs, start/seed/reset scripts, package scripts, workflow files, and
invoked support scripts as code under review. Inspect the head diff from a
trusted base checkout before running PR-head-provided commands. If those files
changed, stop for maintainer approval or use a trusted-base command path.
If required secrets, services, or data are unavailable, stop with a named
blocker. Do not fake a manual pass from static inspection.
## Procedure
1. **Start the real target.**
- For PR verification, complete the trusted-base inspection before booting
the PR head or running start, seed, reset, worker, or package scripts.
- Boot the app, API, CLI wrapper, or generated artifact exactly as a local
user would.
- Watch for healthy startup. Record the URL, command, or artifact path.
- Use synthetic or local test data only.
2. **Exercise each acceptance criterion.**
- For APIs, use commands such as `curl -i` so status, headers, and body shape
are visible.
- For UI, drive a real browser when the repo seam names one.
- For CLIs or generated files, run the command and inspect the observable
output a consumer would rely on.
3. **Hit cheap unhappy paths.**
- Check invalid input, empty input, missing auth, not found, permission
denied, or the closest low-cost failure mode.
- Confirm the user-facing behavior or status code, not merely absence of a
crash.
4. **For UI changes, separate function from appearance and make the evidence durable.**
- Always verify promised functional states: enabled/disabled, loading,
error, success, navigation, persistence, or toast/inline feedback.
- Capture the relevant before and after states for every user-visible change.
The before state may be the current implementation, an intentionally
unfixed build, or a named design reference. Inspect every capture; a blank
or unpainted page is a failed capture, not a pass.
- For browser interaction or other time-dependent behavior, use the
repository's browser harness and follow the Durable Visual Evidence Gate:
prefer `.agents/workflows/pr-processing.md`; otherwise resolve
`../../workflows/pr-processing.md` relative to the loaded skill pack. It
defines the portable recording procedure and clip-inspection requirements.
- Put the artifacts where every intended reviewer can open them. For
GitHub-only or public work, prefer GitHub PR attachments. GitHub CLI 2.99.0+
supports repeatable `--attach` flags when creating or editing a PR. For an
existing PR, default to a dedicated comment and route it through the shared
attribution boundary. Resolve `PR_BATCH_SKILL_DIR` from an explicit
environment value, the `pr-batch` sibling of the exact loaded skill
directory, or repo-local `.agents/skills/pr-batch`, in that order; stop with
a precise blocker if none exists. Write the comment body to
`comment_body_file`. Set `AGENT_COMMENT_RUNNER` to exactly `codex`, `claude`,
or `cursor`, `AGENT_COMMENT_HOST` to the actual non-empty single-line host
label, and `AGENT_COMMENT_TASK_OR_RUN` to the stable task or run identifier.
Stop if any value is unavailable; do not invent attribution values. Then post
the comment with any local evidence attachments:
```bash
"${PR_BATCH_SKILL_DIR}/bin/github-comment-envelope" post-issue \
--repo "${REPO}" --number "${PR_NUMBER}" \
--runner "${AGENT_COMMENT_RUNNER:?}" --host "${AGENT_COMMENT_HOST:?}" \
--task-or-run "${AGENT_COMMENT_TASK_OR_RUN:?}" \
--attach 'path#useful alt text' < "${comment_body_file}"
```
Repeat `--attach` for each file and omit `#alt text` for video. This upload
path requires repository write access through OAuth, a classic PAT, or a
fine-grained PAT, plus the user's authorization for the GitHub mutation;
otherwise confirm before posting. GitHub Actions and App tokens cannot use
it. Use `gh pr edit` only when the body file preserves the complete current
PR description. Read the posted body/comment back to retain the rewritten
stable GitHub attachment URLs. Attach no more than 50 files per command. A
nonzero exit can still leave successful earlier attachments in a created or
updated resource, so read the printed/resulting URL and body before retrying;
retain successful URLs and retry only failed or unattempted files. Fall back
to an authenticated browser/file-upload flow when CLI upload is unsupported.
A configured linked tracker or artifact store is also valid when every
intended reviewer has access; link that evidence from the PR.
- Do not use an undocumented direct-upload endpoint. GitHub CLI 2.99.0+
provides the supported command-line upload path on GitHub.com and GitHub
Enterprise Cloud; its `--attach` support does not cover GitHub Enterprise
Server in this release.
Record the matching `visual_evidence_blocked_reason`: `uploader_absent`
(neither a suitable CLI nor browser upload tool exists), `uploader_denied`
(the credential type is unsupported, or authentication, repository write
access, or host permission policy refused the call), `no_configured_store` (no tracker or artifact
destination is configured or reachable), or `upload_failed: reason` (an
available uploader was exercised and failed; name the observed failure).
State the remedy each one implies, and omit the field entirely when the
upload succeeds. Do not report a denied permission as a missing
capability. If no authenticated
supported uploader or configured integration is available, prepare clearly named
local files and report their absolute paths, but keep the QA evidence and
readiness status `blocked` until a human attaches them and the PR contains
the resulting durable GitHub URL. Local paths, `file:`
URLs, inaccessible private blob/camo URLs, and “captured locally” are not
durable reviewer evidence, even alongside an unrelated HTTPS URL. Reject
`./`, `../`, `~/`, Windows-relative/backslash paths, plain local media
filenames, and blank or unpainted captures. Do not reject a media filename
that is part of the actual HTTPS URL path.
- The replay helper validates URL and destination shape; it does not fetch
evidence URLs or prove their authorization, retention, or liveness. Before
reporting readiness, an intended reviewer must open every evidence URL
using intended reviewer access and reject dead, inaccessible, private-only,
or expiring evidence.
Paint, interaction, and negative-control checks likewise validate a strict
text contract, not the semantic truth of the claim; a reviewer must inspect
the linked evidence and confirm the stated observation.
- For hover, focus, drag, transition, loading, animation, or another
interaction change, link a short durable clip. If recording is unavailable,
use exact labeled evidence such as `measured_substitute:
before_value=52px; after_value=0px; tolerance=1px`; every value and
tolerance needs a unit. Incidental URL IDs do not count.
- For a visual fix, rerun an intentionally unfixed negative control and
record the observed failing assertion or mismatch. A reasoned `not
applicable` is required when no visual fix is in scope.
- If no design reference exists, treat screenshots as sanity evidence and
report obvious breakage only. If one exists, use the repo's visual QA
process for fidelity rather than eyeballing it inside this skill.
- For rendered-page, asset-delivery, or bundle impact, follow the repository
performance seam and use `$benchmark-verification` when it applies. Label
size/shape-only evidence `bundle_hygiene` and name any non-byte shape
measurement with `metric_name=<bundle/asset shape metric>`; claim `measured_metric` only
when a real runtime/user metric was measured, and name it with
`metric_name=<runtime/user metric>`. Either claim requires
`source=<stable command/report/ref>` naming the repo-seam output plus explicit
`baseline_value=<number><unit>` and `candidate_value=<number><unit>` fields
with the same unit; incidental CI URL IDs do not count. Unavailable,
missing, `UNKNOWN`, unmeasured, or N/A evidence blocks.
5. **Record evidence before claiming pass.**
- Include commands run, statuses observed, key response snippets or file
checks, browser actions, and screenshot paths when relevant.
- For current UI changes, classify `interaction_change` and `visual_fix`,
fill the human QA Evidence fields and replayable `qa-evidence v2` marker
from the repository-resolved workflow contract. Resolve
`POST_MERGE_AUDIT_SKILL_DIR` through the explicit env-var, loaded-skill, and
repo-local pinned-copy chain, then run
`"${POST_MERGE_AUDIT_SKILL_DIR}/bin/closeout-evidence-replay"
--expected-head-sha <full-final-head-SHA>
--require-visual-evidence-v2
[--github-host <trusted-repository-GitHub-host>]
<file-or->`. Include `--github-host` for GitHub Enterprise (Cloud or
Server) evidence. The strict v2 flag is invalid
without the expected final-head SHA. If the helper cannot be resolved or
run, report the evidence and readiness state as `blocked`; do not proceed
with a pass claim.
- If anything fails or required evidence is still local-only, fix/rerun the
affected path or report the explicit blocked state.
## Passing Bar
Pass only when every relevant acceptance criterion and cheap unhappy path was
observed in the running target. Otherwise report a concrete blocker or remaining
failure.
## Boundaries
- Keep destructive, load, leakage, memory, and hostile-input campaigns in
`qa-stress`.
- Keep bug-fix before/after PR reproduction in `verify-pr-fix`.
- Do not paste secrets, full `.env` contents, or production data into reports.
## Source Note
Inspired by the manual-testing gate in
[lucasfcosta/backpressured](https://github.com/lucasfcosta/backpressured),
adapted here as portable seam-driven workflow guidance.
Pliki w paczce (2)
- SKILL.md 11 KB
- agents/openai.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · shakacode/agent-workflows | 100 | MIT |
| bmad-labs/skills | 100 | MIT |
| mgifford/accessibility-skills | 100 | AGPL-3.0 |
| lucasfcosta/backpressured | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki efc7d2d1ed74 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90api-testing
Testuje API HTTP na granicy usługi, sprawdzając kody statusu, schematy odpowiedzi, treści błędów i ścieżki uwierzytelniania. - 100next-dev-loop
Weryfikuje zachowanie Next.js w działającej aplikacji po zmianie kodu, łącząc widok Next.js (/_next/mcp) z widokiem przeglądarki (agent-browser); wymaga uruchomionego next dev. - 100next-dev-loop
Weryfikuje zachowanie Next.js w działającej aplikacji po zmianie kodu, łącząc widok Next.js (/_next/mcp) z widokiem przeglądarki (agent-browser); wymaga uruchomionego next dev. - 100next-dev-loop
Weryfikuje zachowanie Next.js w działającej aplikacji po zmianie kodu, łącząc widok Next.js (/_next/mcp) z widokiem przeglądarki (agent-browser); wymaga uruchomionego next dev. - 100nacl-tl-qa
Przeprowadza testy QA end-to-end dla zadań UC w NaCl przez automatyzację przeglądarki, zrzuty ekranu i dowody spełnienia kryteriów akceptacji. - 100qa-engineer
Weryfikuje zadania w działającej aplikacji wobec kryteriów akceptacji, pisze testy end-to-end i zgłasza błędy.