Overview
Explore a case study on the time investment required for writing automated tests in software development. Delve into the challenges of balancing early delivery pressures with the long-term benefits of comprehensive testing. Examine the difficulties in measuring time spent on testing, especially in test-driven development scenarios. Learn about an alternative approach where functionality is developed first and unit tests are written afterwards, providing clear insights into time allocation between main code and test writing. Analyze the implications of this method and gain valuable perspectives on optimizing the testing process in software development projects.
Syllabus
How much time does it take to write tests? A case study - presented by Antonis Christofides
Taught by
EuroPython Conference