Skip to the editor

Prove a contact was actually saved

Waiting & flakiness · level 3 of 5 · PipelineHQ

A confirmation message is not proof that data changed. Good tests wait for the persistent result and the user feedback that follows it.

The problem

Create Ada Lovelace in PipelineHQ.

Saving has a short delay. Your test must prove both of these:

  1. A new contact row appears with Ada's name.
  2. The app confirms the save to the user.

Do not add a fixed sleep. The framework should wait for the state you care about.

Done when

  • Ada Lovelace appears in the contacts table after saving.
  • A confirmation message tells the user that the contact was created.

Bugs we plant

  • Saving a contact silently does nothing
  • No confirmation toast after saving

We break each one in a copy of the app. Your test has to fail on every copy.

Loading the editor…