AI for QA / Scenario
Interrogate the Green-Looking Assertion
Trace a generated browser check through timing and locator behavior before accepting its result.
- Difficulty
- Medium
- Format
- Scenario
- Points
- 150
- Estimate
- 13 min
// MISSION BRIEF
Your Mission
An assistant completed a row-deletion test that passes on a developer laptop and fails in CI. Use the code and trace to identify what the test actually sampled, then select a Playwright assertion that waits for the documented outcome.
// FIRST CONTACT
Battle teaser
First artifact
Suggested Playwright test
What is subtly wrong with the generated assertion?
- AIt reads count() once before the request and DOM update finish
- BBecause the locator can match several rows, assume count() is unreliable here even though Playwright supports list locators and the trace shows a timing gap
- CA DELETE response can never have status 204
- DThe before count must always be hard-coded to three
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
ai-toolscopilotplaywrightassertion-reviewai-for-qa