How would you verify a coding agent's web feature beyond a passing build and a screenshot?

Instruction: Describe observable browser checks for interaction, persistence, accessibility, and failure states.

Context: Validate generated web features through user actions and state changes rather than visual plausibility alone.

Updated

Example Answer

I'd turn the requirement into a short browser journey with observable assertions. For a settings form, I'd change a value, save it, verify the confirmation, reload, and check that the value persisted. I'd also exercise invalid input and a failed request, because a success-looking screen can hide missing behavior.

I'd use stable, accessible locators and wait for the expected state rather than add arbitrary sleeps. I'd check keyboard navigation and relevant narrow-screen behavior, with API or stored-state checks where the requirement needs them. Screenshots help inspect layout, but they don't prove a button works. I'd record the tested artifact and any states I couldn't verify.

Concrete example

A save button that only changes its label can look convincing. A reload-and-read assertion catches missing persistence. Run the journey with a controlled test account and fixture so it does not change a real customer's settings.

Follow-up to practice

Which checks would remain manual even after browser automation passes?

Reference

Playwright: browser assertions and accessibility testing limits

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

1. Start with the foundations

Build the vocabulary and explain the core decisions.

  1. When is a coding agent the right tool instead of autocomplete or manual engineering? Free sample
  2. What information should a coding agent persist between steps? Free sample
  3. Why do tests matter differently for coding agents than for chatbots? Free sample

2. Apply it to a real workflow

Practice diagnosis, validation, and everyday tradeoffs.

  1. What makes a patch proposal safe enough to apply automatically? Free sample
  2. The agent can find the bug, but its patches are hard for humans to review. What would you change? Member answer
  3. How would you verify a coding agent's web feature beyond a passing build and a screenshot? Free sample

3. Prepare for senior discussions

Explain failure boundaries, recovery, and production choices.

  1. A coding agent can modify infrastructure, app code, and data access layers in one task. How do you constrain it? Member answer
  2. Two coding agents change an API and its client in parallel. How would you integrate their work safely? Member answer
  3. A coding-agent hook runs before the repository trust prompt. What is wrong with that design? Member answer

Related Questions