Is it ever ok to delay writing tests?

<p>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.</p><p></p><ul> <li>(00:00) - Our secret podcast agenda </li> <li>(01:00) - Project setup </li> <li>(02:30) - Tests are good, but they do add time </li> <li>(03:15) - Some ambiguity on "is this what the user needs/wants?" </li> <li>(06:00) - Discussing the decision to delay tests as a team </li> <li>(07:15) - Conclusion - it's the audience, not the timeline </li> <li>(08:10) - Side benefit of knowledge sharing </li> <li>(09:15) - Silly bit</li> </ul><br>Become a more confident Laravel developer. Sign up for practical tips at <a href="https://masteringlaravel.io?ref=podcast">masteringlaravel.io</a>