aite report

8 files

Alex Wykoff · fix(engine): a page that did not load fails at once, ambiguous targets fail fast, visibility follows the browser · 1w ago

feat(report): P4-1 static report.html and P4-2 outline of the failed element

feat(schedule): aite schedule, one issue per failing test, budget, kill switch, lock, Chrome flag (P7-3)

feat(verdict): P4-3 verdicts, P4-5 hardened local page, P4-6 throwaway GitLab project

fix(engine): a page that did not load fails at once, ambiguous targets fail fast, visibility follows the browser

scheduleIssue.ts

feat(schedule): aite schedule, one issue per failing test, budget, kill switch, lock, Chrome flag (P7-3)

feat(schedule): aite schedule, one issue per failing test, budget, kill switch, lock, Chrome flag (P7-3)

verdictServer.ts

feat(verdict): P4-3 verdicts, P4-5 hardened local page, P4-6 throwaway GitLab project

verdictService.ts

feat(runner): pre-state failures (balance-at-least), block-separated read, functional page-logic tests

README.md

report/ #

render.ts makes the static report (report.html) from a run.json; generate.ts reads a results folder, embeds the pictures of the steps that need a look and writes the file. aite run calls this at the end of every run; aite report RESULTS_FOLDER does it again for an old one.

The report has no script and a content security policy that allows none: everything from the page under test is escaped text. Tests: test/unit/reportRender.test.ts (including an injection property test), test/unit/reportGenerate.test.ts, test/integration/report.whole.test.ts, test/functional/report.e2e.test.ts (real Chrome). The confirm buttons are on a separate page served by aite verdict (verdictServer.ts, verdictService.ts, verdict.ts, gitlab.ts): see docs/design/data-formats.md (Verdict) and decisions.md (P4-3).