Skip to main content

Frontend Engineer

How do you test a component that fetches data and shows loading and error states?

TechnicalMid levelTests: Frontend testing
Drill this questionCreate a free account to answer out loud with Ava and get feedback.

What the interviewer is looking for

  • This question tests frontend testing. Tests user-visible behaviour, mocks network calls sensibly, and balances component tests with a few end to end tests.
  • Strong answers: Mocking the network layer, testing what the user sees rather than internals, covering loading, success, empty and error states, and avoiding flaky timing.
  • Likely follow-up: When would you add an end to end test on top of that?

Another way it may be asked: You've built a user profile card that loads from an API. How would you write tests that check it behaves properly in every case?

A structure to follow: Answer, explain, example, limits

  1. Step 1

    Answer

    Give your direct answer in the first sentence so the interviewer knows where you are going.

  2. Step 2

    Explain

    Say how it works or why you would do it that way, in plain words before jargon.

  3. Step 3

    Example

    Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

  4. Step 4

    Limits

    Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

  • Reciting a definition without showing you have applied it.
  • Using terms you cannot explain if asked a level deeper.
  • Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Browse all questions

How do you test a component that fetches data and shows loading and error states? | How to answer