Test Data and Fixture

You might say

Prepare fixed user and product data for the order test, and create it before every run and clean it after so the next run starts identically.

Test data are input and state samples; a fixture is a reusable setup and cleanup mechanism.A fixed user and order JSON are test data. Creating an account and order before a test, then deleting or restoring state afterward, is a fixture. Together they give each case the same start. One random input or yesterday’s leftover record is not stable evidence.

Know first

Test Case Database

Test FixtureFixture

How fixed orders are prepared before and cleaned after a test

test_dbusers

setup()

idemailcart_itemssource

U-TEST-04member@trip.test2fixture

Create fixed account
Case uses this row
Remove test account

Test data is the row value; the fixture makes it appear on time and disappear afterward.

What data and fixtures each own

Test data supplies clear input and state: A registered user, cart with two items, and valid coupon are starting conditions. Fixed readable data makes failures reviewable instead of randomly different every run.

A fixture restores the same starting point: Fixtures organize account creation, order setup, dependency startup, and cleanup into a reusable mechanism. Cases write less duplicated setup and do not contaminate each other with leftovers.

Quick checkChoose the best answer

“Create a regular user and a pending-payment order before the test, then delete both afterward” is most accurately what?

A fixture, because it defines setup before and cleanup after a caseOnly test data, because it contains a user and orderProduction seed data that needs no cleanup

You can say this to an AI Agent

Create an order-test fixture: before each test make a fixed user and pending-payment order, then clean up afterward. Keep concrete test data separate from setup/cleanup steps; run twice and confirm the second run is not affected by the first.

Learn next

1Test Case→2Flaky Test→