The trade-offs of automated testing

Automated testing is a topic that sparks debate among developers. While some argue that all code should be thoroughly tested, others believe that the context and goals of a project should determine the need for testing. The discussion delves into the trade-offs of automated testing, highlighting how it can be time-consuming and may not always align with business objectives. The speakers mention examples from their own experiences, such as the challenges of testing non-deterministic APIs and the potential benefits of allowing small bugs to provide touchpoints with customers. Ultimately, it is important for developers to consider the context, customer impact, and business goals when deciding on the level of testing necessary for a project.