AI for QA / Quiz
Coding Assistant Boundary Check
Judge a generated test as a context-sensitive draft rather than a source of project truth.
- Difficulty
- Easy
- Format
- Quiz
- Points
- 100
- Estimate
- 6 min
// MISSION BRIEF
Your Mission
An inline coding assistant completed a login test from the nearby file. Inspect the suggestion and its available context, then decide which work it accelerates and which claims still belong to the tester, compiler, documentation, and suite.
// FIRST CONTACT
Battle teaser
The assistant suggests: await page.locator("#email").fill("bad@example.test"); await page.getByText("Login").click(); expect(await page.locator(".toast").textContent()).toBe("Invalid credentials"); What is the most accurate way to use this output?
- AAssume the assistant ran the test against the current application
- BTreat it as accepted product behavior because it compiles visually
- CMerge it without review because login is a common feature
- DTreat it as a draft, then verify selectors, expected copy, synchronization, and project conventions
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
ai-toolscoding-assistantreviewai-for-qa