Episode 105
Why we have a separate test suite for external services
No Compromises · Joel Clermont and Aaron Saray
July 23, 202418m 3s
Audio is streamed directly from the publisher (media.transistor.fm) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
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.
Topics
laravelphp