There are two types of tests a developer can write, ‘test to work’ and ‘test to break’. Both are essential to robust development, but many developers only use the former and not the latter. This talk explains why ‘test to break’ principles are essential to ensure robust application development.
The talk aims to highlight the importance of testing, why developers must spend more of their time testing, how testing generates more robust applications and why testing makes developers’ lives easier.
The talk is based around a live coding demo.
The talk will:
- Explain the difference between tests that prove an application works and tests which aim to break the application logic.
- Highlight how test to break principles force developers to introduce logic to handle unexpected behaviour.
- Show how test to break principles result in more robust applications as developers write code that can only be used in one way.
- Encourage developers to apply test to break principles to all types of tests, including manual tests.
This talk is based on a blog post found on my personal site: https://rbrt.wllr.info/2018/01/15/why-you-must-test-to-break.html
There is also a GitHub library which will form the basis of the demo: https://github.com/RobDWaller/test-to-break
- PHP UK
- PHP Dorset
- PHP Hants
There are two types of tests a developer can write, 'test to work' and 'test to break'. Both are essential to robust development, but many developers only use the former and not the latter. This talk explains why 'test to break' principles are essential to ensure robust application development.