Why We Have A Separate Test Suite For External Services No Compromises podcast

Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

No Compromises »
Why we have a separate test suite for external services

6h ago 18:03

MP3•Episode home

Writing tests that communicate with a third party can be a little tricky, but we've found an approach that balances speed and confidence.

In today's episode, we share that approach and talk through a strategy of how frequently to run tests that talk to the outside world.

(00:00) - Why would your tests ever talk to an external service?
(02:30) - What does it mean to have a separate test suite?
(06:00) - Keeping them separate allows different triggers for running
(07:00) - When should you run external tests?
(08:30) - You can't always know when you'll break an external integration
(11:00) - Check on a schedule?
(13:00) - Silly bit

Would you like to take 2 - 3 minutes each day to learn a little bit about Laravel? Join for free, unsubscribe any time.

105 episodes

#Tech #Joel Clermont #Aaron Saray