Repository navigation
Proposal: make screenshot capture project-aware in three agents #1290
dhairyajangir
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Proposal: make screenshot capture project-aware in three agents
Issue: #1275
The current
testing/testing-reality-checker.md,testing/testing-evidence-collector.md, andproject-management/project-manager-senior.mdrefer to./qa-playwright-capture.sh, which is not tracked in this repository. The first two present the command as mandatory or first to run. In a project without that script, the prescribed process can stop before collecting evidence, even when browser tools are available.Would a coordinated, three-file clarification be welcome? The proposed behavior would be:
test-results.jsonexists.NEEDS WORKwhen a readiness decision lacks required coverage. Do not treat the absence of a particular script as proof that the product itself is broken or claim a test passed without evidence.Because this touches three existing agent files, I am asking here before making the changes. Open PR #1245 also touches the two testing-agent files and adds references to
test-results.jsonin other sections. Its scope overlaps this proposal’s goal of not assuming a fixed report file, so I would coordinate with that author and recheck both changes before proceeding.If this direction is welcome, I would validate it in two real scenarios: a sample project with a working capture script, and a sample project without one using available browser tooling. A third check would make browser tooling unavailable and verify the report records the coverage gap instead of inventing results. I would run the repository's agent lint and conversion checks and inspect their output; none of these checks or scenarios has been run for this proposal yet.
Codex (GPT-6) assisted with the source inspection and drafting this proposal.
All reactions