This document discusses the benefits of test-driven development (TDD) and unit testing over traditional approaches to coding without tests. It notes that coding without tests can lead to bugs that are difficult to fix and applications that are hard to update. TDD involves writing tests before production code to specify functionality, then writing just enough code to pass each test. This approach prevents bugs and ensures code quality and performance while improving maintainability. The key principle of TDD outlined is to not write any production code without a failing test first.

1. Test Driven Development
Unit Testing

2. It was satisfying to write code without TESTS
Run it in
browser
or
va_dump() it
Write
code Something went
wrong ?
Yes No
Next
>>

3. FLASH IN THE PAN
● Couldn’t Agile.
● Fixing one bug will result alot more.
● Unoptimizabel.
● Couple line of code can break the whole application ( Break Code ).
● Can’t updatable.
● Increase Costs and Times.

4. SOLUTION TDD Test Driven Development
Unit Testing
1. You are not allowed to write any production code without
first writing a test that fails because the production code
does not exist.
1. You are not allowed to write more of a test than is sufficient
to fail; including failure of compilation.
1. You are not allowed to write more production code than is
sufficient to pass the currently failing test.
● Prevents long hours of
debugging and rework
● Ensure our performance
● 100% Coverage feels so
good
● Better maintainability

5. “You are not allowed to write any
production code without first writing a
test ”
- From Uncle Bob