Skip to content

QA.md

Latest commit

 

History

History
37 lines (23 loc) · 2.3 KB

QA.md

File metadata and controls

37 lines (23 loc) · 2.3 KB
Raw

Verification

Automated baseline

Run npm run check, npm test and npm run build before publishing.

The inherited suites cover editor behaviors, layer properties, recording regressions and message/export contracts. Some suites aggregate their assertions, so Node's top-level test count differs from the number of named checks. Contract tests include source-level checks and VM-based functions; they do not substitute for full browser integration.

Packaging includes only extension runtime files, icons, license and installation instructions. Tests and mocked harnesses are excluded from the downloadable extension. SHA-256 checksums are generated alongside releases.

Real-extension smoke check

Use a synthetic page with the unpacked extension loaded:

  1. Toggle the extension, select an element and hover another element to measure spacing (no modifier required).
  2. Preview one style change, switch elements, undo it and confirm original styles return.
  3. Start a review; press R, type while screenshots settle, save and locate the resulting issue.
  4. Refresh the page and confirm records persist.
  5. Export HTML, XLSX and ZIP; verify screenshots, text and element location in each supported format.
  6. Test keyboard focus, Escape, Space pass-through and reduced-motion behavior.
  7. Try a blocked Chrome page and confirm the extension fails clearly.

extension/test-harness.html is useful for visual inspection and UI logic, but uses mock capture/storage/export and does not prove these browser APIs work. The current audit and acceptance matrix are in 2026-09-04 audit; installation paths and shortcuts are in the README.

Source / loaded extension parity

After reviewing and applying changes to a separately loaded development copy, run:

npm run check:installed -- /absolute/path/to/loaded-extension

This is read-only and compares runtime code, manifest, icons and preview images. It fails on missing or different files. A matching version number alone does not prove identical builds. Do not overwrite one copy before reviewing its differences.

Website

Verify desktop and phone widths, check all local asset links, switch the three demo steps, edit the example issue, download Markdown, and confirm the extension ZIP contains a loadable manifest. All example data must remain fictional.