You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal\nMake the README unambiguous for a junior who has never used AQA: start the application backend, start AQA's admin/backend, run the first test, and understand how to author a real scenario.\n\n## Changes\n- Two-process explanation with Terminal 1/Terminal 2 commands\n- Bundled Bun API absolute-beginner path\n- Concrete executable idempotency API scenario\n- Explicit risk-to-invariant-to-scenario linkage\n- Progress/lesson updates\n\n## Verification\n- README markdown link check passed\n- git diff --check passed\n- Commands compared against CLI and bundled example scripts\n\n## Review policy\nOperator has opted out of Copilot review for this side-project phase; all technical/documentation checks remain mandatory.
Clarifies beginner onboarding for starting the application and AQA backends, running the first test, and authoring scenarios.
Changes:
Adds two-terminal startup instructions.
Documents the bundled Bun API walkthrough.
Adds an idempotency scenario and updates progress and lessons.
File
Summary
Final review findings
README.md
Beginner setup, backend usage, and scenario guidance.
7 moderate findings: initialize/build from the correct directory and use the generated profile; configure sut.base_url; provide valid risk references; authenticate supported preconditions; add stronger duplicate-prevention assertions; fix heading structure. One nit concerns the walkthrough ordering.
docs/PROGRESS.md
Records onboarding progress.
1 nit: update the entry because the documented example flow currently fails before execution.
Place terminal block after initialization and base URL configuration
README.md:410
This block is placed before the walkthrough's aqa init step, so a junior following the documented order gets .aqa/project.yaml not found before any test runs. Also, init leaves sut.base_url unset unless the user configures it, which disables the HTTP driver. Make this terminal block explicitly follow initialization and base-URL configuration.
`QA_TOKEN=... bunx aqa run --profile smoke` (PowerShell:
`$env:QA_TOKEN='...'; bunx aqa run --profile smoke`). A risk map entry without
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal\nMake the README unambiguous for a junior who has never used AQA: start the application backend, start AQA's admin/backend, run the first test, and understand how to author a real scenario.\n\n## Changes\n- Two-process explanation with Terminal 1/Terminal 2 commands\n- Bundled Bun API absolute-beginner path\n- Concrete executable idempotency API scenario\n- Explicit risk-to-invariant-to-scenario linkage\n- Progress/lesson updates\n\n## Verification\n- README markdown link check passed\n- git diff --check passed\n- Commands compared against CLI and bundled example scripts\n\n## Review policy\nOperator has opted out of Copilot review for this side-project phase; all technical/documentation checks remain mandatory.