We always write tests, and can't imagine working without them. But is there ever a time where it might make sense to delay writing some tests until later in the project? Let us tell you a story about a recent project where we made that decision.
- (00:00) - Our secret podcast agenda
- (01:00) - Project setup
- (02:30) - Tests are good, but they do add time
- (03:15) - Some ambiguity on "is this what the user needs/wants?"
- (06:00) - Discussing the decision to delay tests as a team
- (07:15) - Conclusion - it's the audience, not the timeline
- (08:10) - Side benefit of knowledge sharing
- (09:15) - Silly bit
Become a more confident Laravel developer. Sign up for practical tips at
masteringlaravel.io
