Assertions about shape, not about values

A collection asserting that the total is 4900 fails whenever the seed data changes, which is every sprint — and gets deleted rather than fixed.

pm.test('order has the expected shape', () => {
  const body = pm.response.json();

  pm.expect(pm.response.code).to.equal(200);
  pm.expect(body).to.have.property('id').that.is.a('number');
  pm.expect(body).to.have.property('total_cents').that.is.a('number');
  pm.expect(body.status).to.be.oneOf(['pending', 'paid', 'shipped']);
});

Asserting on presence and type rather than value is what makes the test stable — the data changes and the contract must not. The oneOf check is the middle ground for an enumerated field and is worth having, because a new status value appearing is exactly the change a client needs to know about. Anything asserting a specific total belongs in the application’s own test suite where the fixtures are controlled.