sabinelaurent/nodejs-testing-best-p...

different technically and tricky. The 📗 section 'Message Queues' below delve into this topic **• Observability -** Some things must be monitored, like errors or remarkable business events. When a transaction fails, not only we expect the right response but also correct error handling and proper logging/metrics. This information goes directly to a very important user - The ops user (i.e., production SRE/admin). Testing error handler is not very straightforward - Many types of errors might get thrown, some errors should lead to process crash, and there are many other corners to cover. We plan to write the 📗 section on 'Observability and errors' soon, but the example application already contains examples in the file "createOrder.observabilityCheck.test.ts"  <br/><br/> ## **Section 5: Integrations** <br/> ### ⚪️ 1. Test critical integrations with real services 🏷&nbsp; **Tags:** `#intermediate #strategic` :white_check_mark: &nbsp; **Do:** When testing integrations, the goal is to test the entire interaction, not just the request/response. The test should validate the entire communication with the 3rd party service, including things like authentication, retries,