VS Code Test and Coverage Workflow Audit
Check how tests are run and what they cover.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit the testing workflow in VS Code. Test framework and commands: [TEST_FRAMEWORK]. How developers run tests today: [CURRENT_PRACTICE]. Coverage numbers if known by module: [COVERAGE_DATA]. Flaky or slow tests: [PROBLEMS]. Check whether tests can be run and debugged from the editor, whether the editor's test command matches the continuous integration command, whether results are visible quickly, whether coverage is measured and interpreted sensibly, and whether slow tests are separated. Calculate the share of modules under target coverage (6 of 20 under 60 percent is 30 percent). Worked example (invented): billing 41 percent, auth 78, reporting 63, utilities 90; billing is below target (1 of 4 under 60 percent), but check which lines are uncovered and how critical they are, and review five billing tests to see whether they assert behaviour or merely run code. Coverage shows which lines ran, not whether the assertions are meaningful, and a target needs a discussion of what it protects. Feedback time: a full suite of 6 minutes run 8 times a day is 48 minutes. Recommend splitting fast and slow tests and running the relevant tests on save [VERIFY], keeping continuous integration as the final gate. One-week experiment measuring feedback time before and after, and a one-month plan to add tests for the highest-risk uncovered paths. Return a table (Issue, Evidence, Fix, Effort). Mark settings and extension names [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.