domains / families / science / assay

assay

authentic

Run assay on a web page you just wrote or changed. It opens the page in a real browser, drives every control, and reports where the page contradicts itself. Deterministic, no API key, no network.

When to use

• Use when you have just created an HTML page and want to know whether its controls work before you move on.
• Use when you changed a page, or the JavaScript or CSS that a page loads, and want to confirm the page still holds together.
• Use when the user asks you to check, QA, or smoke-test a local web page.
• Run it once at the end, after the last edit, on each page you changed. Do not run it while you are still making changes.

When not to use

• assay will not build your project. Point it at built output. Given a source tree, it says so and names the command to run, and it will not run `npm install` for you, because installing dependencies executes their setup scripts.
• assay checks one page. It does not crawl, so run it on each page you changed.
• assay cannot check intent. A control that runs but does the wrong thing usually is not caught, because assay presses what the page offers and reports what followed without knowing what the page is for.
• A finding is a place to look, not a confirmed bug. A control can correctly do nothing in the state it was pressed in, and a value can be limited on purpose.

Skill page

Source