A presentation about test driven development in php world

1. TEST DRIVEN DEVELOPMENT
Think first, code later, php way

2. Schema

3. 3 Factors
1. Test
2. Code
3. Refactor
Result:
1. Readable code
2. Managed code

4. First Implement?

5. Second Implement?

6. Are you sure?

7. Source Code Tested?

8. How?
User Stories:
As a guest, i want to go to homepage and want to see “hello
World” message

9. Test Code
<?php //cakephp way
$msg = $this->testAction(‘/’, array(‘return’ => ‘contents’));
$this->assertEquals(‘hello World’, $msg);
======================================================
==
<?php //laravel way
$msg = $this->call(‘GET’, ‘/’);
$this->assertEquals(‘hello World’, $msg);

10. Result?
remember: source code not exists yet! so it must be fail!

11. Implement Feature ~ CakePHP
<?php //file: app/Controller/HomeController.php
class HomeController extends AppController {
public function index() {
$this->autoRender = false;
echo ‘hello world’;
}
}

12. Implement Feature ~ Laravel
<?php //file: app/routes.php
Route::get(‘/’, function() {
return ‘hello world’;
});

13. Result?

14. Programmer

15. Why?
‘hello world’ != ‘hello World’

16. Fix it!
Replace : ‘hello world’ with ‘hello World’

17. Test it!

18. Programmer

19. It’s just a simple test!
Simple doesn’t mean not to fail!

20. Complex? (example 1)

21. Complex ? (example 2)

22. Then?

23. Your boss?

24. the question is...

25. Good Quality
Good Quality == Good Business
Good Quality == More Happy Customers
Good Quality == More Happy Programmers
Happy Programmers == Readable Source Code
Readable Source Code == Good Quality

26. Time Management
CODE FIRST, TEST LATER == TIME LOSS
TEST FIRST, CODE LATER == TIME INVESTMENT

27. Time Loss
1. We don’t know bug
2. We don’t know errors
3. We don’t know fail validations!
Question: If you don’t know anything, are you sleeping or coding?
4. Test features? just open the browser!
It’s 2014 now!!

28. Time Investment
1. More fast we detect a bug, we can fix it
faster!
2. More fast we know an error, we can fix it
faster!
3. We control the code, not controlled by code!
4. Test all features? One single hit => Enter!

29. Test All Features (cli)
$ phpunit

30. Test Sub Features (cli)
$ phpunit --testsuite FeatureA
$ phpunit --testsuite FeatureB

31. Tools
PHPUnit
http://phpunit.de
PEAR
http://pear.php.net

32. MVC Framework Unit Test
1. Controller
2. Model
3. View
4. Library / Vendor /Package
5. Helper

33. Forbidden Framework
1. Developed not by test
2. Not integrated with unit test
3. Cannot test their own self!

34. Suggested Framework
1. Laravel >= 4.1
2. CakePHP >= 2.4.5

35. Unit Test Environment
1. OS: Linux Base (Ubuntu)
2. PHP Error Level: error_reporting(-1) *all

36. Refactor

37. Programmer Assumptions
The real problem is not whether machines think but whether men do.

38. END - Happy Hunting