QA report: external/crit.md at hosted
The application is functional and stable across core workflows, with one medium usability issue involving missing visual feedback on clipboard copy actions.
Testing covered 12 scenarios across the application, evaluating interactive review demo features, comment navigation and submission, session user naming, table of contents toggling, agent prompt generation, platform tab switching, theme toggling, and documentation navigation.
Eleven scenarios passed without issue. The single failure occurred when copying an installation command, where the button lacked visual confirmation such as a label change, icon update, or toast notification to confirm that the text was copied.
The core interaction and navigation capabilities operate reliably, meaning the sole confirmed issue is a cosmetic and feedback defect that does not block core user journeys.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 12 |
| Passed | 11 |
| Failed | 1 |
| Blocked | 0 |
| Findings raised | 1 |
| Issues after the audit | 1 |
| Withdrawn by the audit | 0 |
| Critical / high / medium / low | 0 / 0 / 1 / 0 |
Target: https://crit.md · Testing level: deep_feature · Stack: unknown
Issues
Medium severity
F1 · Copy to clipboard button provides no visual feedback upon clicking
Severity: medium · Type: ux · Verdict: confirmed · Scenario: S9
The evidence supports the lack of visual feedback on the installation copy button (inconsistent with the 'Copy prompt' button in S7), though this cosmetic UX issue warrants a low severity rather than medium.
Expected: A temporary visual indicator such as 'Copied', a checkmark, or confirmation message should appear when clicking the Copy button.
Actual: No visual feedback is provided upon clicking; the button remains as 'Copy to clipboard' without a 'Copied' state, checkmark, or toast.
Steps to reproduce:
- Navigate to https://crit.md/
- Locate the 'Connect your agent' code snippet block
- Click the 'Copy to clipboard' button
Evidence: screenshots/S9-9.png
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S1 Load interactive review demo | high | pass | none |
| S2 Navigate comments via controls | high | pass | none |
| S3 Toggle table of contents | high | pass | none |
| S4 Set user name for session | high | pass | none |
| S5 Reject empty comment reply | high | pass | none |
| S6 Submit valid comment reply | high | pass | none |
| S7 Generate agent prompt | high | pass | none |
| S8 Switch installation platform tab | medium | pass | none |
| S9 Copy installation command | medium | fail | F1 |
| S10 Select agent integration | medium | pass | none |
| S11 Toggle application theme | low | pass | none |
| S12 Navigate to review mode guide | low | pass | none |
The audit
The Critic reviewed 1 finding and re-verified 0 of them live in the browser, replaying the reported steps on a fresh page.
- Finding F1 captures a valid cosmetic inconsistency, but its severity should be downgraded to low.
- The test execution achieved clean coverage of the core features, including demo navigation, comment interactions, and theme switching, with no environment or harness blocks.
What to fix first
- F1: Update the copy to clipboard button to provide immediate visual feedback, such as changing the label to 'Copied' or displaying a checkmark when clicked.
Coverage and caveats
In scope: Interactive web review viewer features and navigation; Inline comment threading and prompt generation; Landing page interactive elements (platform selectors, copy buttons); Theme switching and agent integration guides.
Not covered: GitHub OAuth Login, because it requires a third-party account which is out of scope for a hosted run..
- Replying to the demo artifact may be blocked for unauthenticated users on the backend; displaying an auth prompt in this case is considered a success.
- The 'Set your name' functionality relies on local/session storage rather than a backend profile since authentication is not required.
By the numbers
| Metric | Value |
|---|
| Scenarios | 11 passed, 1 failed, 0 blocked of 12 (36 planned steps) |
| Browser actions | 166 (27 clicks, 3 inputs, 42 navigations, 94 snapshots) |
| Screenshots | 40 (4 explore, 36 scenario, 0 critic), 36 captioned |
| Coverage | 15 pages, 2 forms, 3 flows, 0 console errors |
| Audit | 1 findings, 0 re-verified live, 1 confirmed, 0 promoted, 0 withdrawn |
| Model calls | 156 |
| Tokens | 2,085,284 input, 8,625 output, 13,073 thinking |
| Time | 10 min |
| Stage | Calls | Input | Output | Thinking | Seconds |
|---|
| explore | 27 | 327,422 | 2,318 | 974 | 110 |
| plan | 1 | 4,418 | 1,915 | 1,781 | 28 |
| test | 126 | 1,746,931 | 3,997 | 7,564 | 438 |
| critique | 1 | 5,037 | 181 | 2,439 | 20 |
| report | 1 | 1,476 | 214 | 315 | 5 |
