sparkecoder 0.1.72 → 0.1.73

package/dist/skills/default/qa.md

@@ -627,15 +627,19 @@ document.addEventListener('keydown',function(e){if(e.key==='Escape')closeLightbo
 
 ## Best Practices
 
+
 1. **Screenshot + upload every finding** -- take a screenshot, `read_file` to review it, `upload_file` to get a URL, then link it in the report
-2. **Re-snapshot after every navigation** -- element refs go stale when the page changes
-3. **Test the happy path first** -- verify core functionality works before edge cases
-4. **Note severity levels** -- 🔴 High = broken functionality, 🟡 Medium = usability issue, 🟢 Low = cosmetic
-5. **Be specific** -- "Submit button overlaps footer at 375px" is better than "layout issue on mobile"
-6. **Use descriptive screenshot names** -- `qa-issue-nav-overlap.png` not `screenshot3.png`
-7. **Close the browser when done** -- always run `agent-browser close` at the end
-8. **Save the report as HTML** -- write the final report to `.sparkecode-artifacts/qa/qa-report-<date>.html` (not markdown)
-9. **Upload the report** -- after writing the HTML file, `upload_file` it so the user gets a clickable link that opens as a styled webpage
-10. **Return the URL** -- give the user the uploaded report URL so they can share it
-11. **Never return local paths in final output** -- return only `downloadUrl` links for screenshots and report files
-12. **Include a written summary with the links** -- provide a concise summary in addition to the uploaded report/screenshot URLs
+2. **Inline screenshots with each test case** -- every test case in the report must have its screenshot placed directly next to the result (pass/warning/fail), not grouped separately at the bottom or top
+3. **Include steps to reproduce** -- each reported test case must include numbered steps to reproduce the issue (e.g., "1. Navigate to /login, 2. Enter valid credentials, 3. Click Submit, 4. Observe error message"), so anyone reading the report can replicate the finding
+4. **Re-snapshot after every navigation** -- element refs go stale when the page changes
+5. **Test the happy path first** -- verify core functionality works before edge cases
+6. **Note severity levels** -- 🔴 High = broken functionality, 🟡 Medium = usability issue, 🟢 Low = cosmetic
+7. **Be specific** -- "Submit button overlaps footer at 375px" is better than "layout issue on mobile"
+8. **Use descriptive screenshot names** -- `qa-issue-nav-overlap.png` not `screenshot3.png`
+9. **Match screenshots to verdicts** -- when a test case is marked 🔴 Fail, 🟡 Warning, or 🟢 Pass, the corresponding screenshot should visually support that verdict and appear immediately after the status line and steps to reproduce
+10. **Close the browser when done** -- always run `agent-browser close` at the end
+11. **Save the report as HTML** -- write the final report to `.sparkecode-artifacts/qa/qa-report-<date>.html` (not markdown)
+12. **Upload the report** -- after writing the HTML file, `upload_file` it so the user gets a clickable link that opens as a styled webpage
+13. **Return the URL** -- give the user the uploaded report URL so they can share it
+14. **Never return local paths in final output** -- return only `downloadUrl` links for screenshots and report files
+15. **Include a written summary with the links** -- provide a concise summary in addition to the uploaded report/screenshot URLs