prestashop-pr-qa
QA a PrestaShop pull request
Run the pull request's own test steps against a running environment twice: once on the code as it was before the PR, once on the PR's code. Record both runs. The deliverable is one verdict (approved, not approved or not reproducible) with the recording that backs it up.
How the environment is observed depends on what the PR changes. Three probes, one set of rules:
| Probe | For a PR that changes | Evidence |
|---|---|---|
browser |
what a page shows: templates, JS, CSS, forms, the back office | paired screenshots and a video |
cli |
what a command does: console commands, module CLIs, install and upgrade scripts | paired transcripts, exit codes, files touched |
http |
what the server answers: the webservice, JSON controllers, status codes, redirects | paired requests with status and body |
Everything after the probe is identical, and that is the point: two phases in the same order, the same scenario in both, the same flake rule, the same reasons to refuse a verdict.
Terms used in this skill
The left column is what the files and the code call things: before/ is a real directory, --phase=before is a real argument, flaky is a real field in phase.json. Renaming them in prose only would leave the words and the data saying different things.
The right column is what they mean, and the right column is what you say out loud. Never make the person you are talking to learn this table.