DiscoverNo CompromisesWhy we have a separate test suite for external services
Why we have a separate test suite for external services

Why we have a separate test suite for external services

Update: 2024-07-23
Share

Description

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.
Comments 
00:00
00:00
x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

Why we have a separate test suite for external services

Why we have a separate test suite for external services

Joel Clermont and Aaron Saray