The QAvenue

🐝Buzzing Around APIs: When 404 Not Found Hides the Nectar

“Buzzing around, I tried to get an order that didn’t exist
 and got 404 Not Found. Honey, if it’s not in the hive, you won’t find it!”

Type of testing: Endpoint Testing

Status: Code 404

Step to Reproduce (Mock Server):

  1. Open Postman
  2. Send GET request to /orders/9999 (ID that does not exist)
  3. Observe 404 Not Found and the error message in the body

Added screenshot of request & response

Fail : 404 Not Found

Edge Case : 404 Not found(Invalid EndPoint)

What This Shows:

  • Useful for testing client behaviour when resources are missing
  • API correctly handles non-existent resources
  • Demonstrates that you’re checking error handling for edge cases

Pro Tips:

  • Include in automated tests to ensure consistent error handlingTest other endpoints for missing resources
  • Combine with auth checks: 404 vs 401/403 for unauthorized access

Lesson:

“if it’s not in the hive, you won’t find it. always validate your endpoints!”