2.3Annotation: What Makes These Tests Good

1. Fixture-Based Setup and Teardown

The seed_product fixture creates test data and cleans up afterward. This ensures test independence -- no test depends on state from a previous test.

2. Multi-Layer Assertions

Good tests check more than just the status code:

# Not just: assert response.status_code == 200
# But also:
assert body["id"] == seed_product["id"]    # Correct resource returned
assert body["category"] in [...]           # Valid enum
assert body["price"] >= 0                  # Business constraint

3. Parametrized Boundary Tests

Instead of writing separate test functions for each boundary value, parametrize combines them into a compact, maintainable structure.

4. Both Valid and Invalid Boundaries

Note that there are TWO parametrized tests for name length:

• test_update_name_boundary tests INVALID values (expect 400)
• test_update_name_valid_boundaries tests VALID values (expect 200)

This ensures both sides of the boundary are covered.

5. Every Documented Status Code Has a Test

The schema documents 200, 400, 401, and 403. Each has at least one test that triggers it.