ตรวจสอบเส้นทางและ JSON

A good route test checks two things: the right status code and the right body. If both match, you know the endpoint behaves as promised.

The response carries a status_code attribute. A healthy page returns 200, so assert on it to confirm the route loaded without error.

The full response body lives in resp.data as bytes. Decode it to text when you want to search for words inside an HTML page.

To confirm a page shows the right content, check that a phrase appears in the body. The simple in operator is perfect for this.

For API routes, call resp.get_json(). Flask parses the body into a Python dict or list so you can assert on real values.

Once you have the parsed dict, check individual keys and values. This proves your serializer returned exactly the fields you expect.

A JSON endpoint should advertise itself. Assert that resp.content_type includes application/json so clients parse it correctly.

Error paths deserve tests too. Request a missing URL and assert the status is 404, proving your app fails gracefully.

Send data with client.post and a json argument. Then assert the created status code, usually 201, and the returned body.

Collection endpoints return a list. Parse it, then assert its length or inspect items by index to verify the payload shape.

Keep each test focused on a single behavior. Small, named tests make failures obvious and your suite far easier to read.

You hit a JSON API route in a test. How do you read its body?

You now assert on status codes, page text, and parsed JSON. With these moves you can pin down any route's behavior with confidence. ✅