API Testing

working on some endpoint tests and noticed if i send a filter that doesn't exist, the api returns 200 ok with an empty array instead of 404 or 400. is this just standard practice or am i looking at a silent failure? feels weird to get a success code when the query was technically…

working on this endpoint and noticed that searching for a non existent user returns a 200 with an empty body instead of a 404. feels wrong but idk if this is standard behavior or a dev shortcut. how do you guys handle this in your test suites?

spent all morning debugging a 500 error only to realize the dev environment was just asleep. why do we pretend we're testing logic when we're really just playing 'is the server awake today?' bingo. anyway, here is how i'm currently tracking these timeouts in playwright:

spent my morning watching another team move from a perfectly fine fetch wrapper to the latest 'api first' abstraction layer. spoiler: it's just more state management to break. we're essentially replacing: with a 300 line generated client that fails if a single field in the schema…