Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie TDD with phpspec2
Ähnlich wie TDD with phpspec2 (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
TDD with phpspec2
- 2. Who I am • Anton Serdyuk • email/jabber: anton.serdyuk@gmail.com • skype: serdyuk.anton • twitter: @anton_serdyuk • facebook: anton.serdyuk
- 3. Overview
- 4. Auto-tests forms • Functional tests (+BDD) • Integration tests • Unit tests
- 5. Functional tests • Use full deployed application instance • Test business expectations • Use the same UI interactions as real user
- 6. Functional tests with phpunit example
- 7. BDD (or story BDD) • Story-driven functional tests • BDD ⊂ Functional tests
- 8. BDD with behat example
- 9. Integration tests • Use integrated parts of applications • Can use database, filesystem etc. • Can test API, Doctrine repositories etc.
- 10. Integration tests with PHPUnit example
- 11. Unit tests • Use small parts of code • Can not use database • Can not use filesystem • Extremely fast
- 12. Consider using appropriate tools for tests phpunit behat phpspec codeception Functional + + + Integration + + (sometimes) + Unit + + +
- 13. My personal preference • behat for functional and API integration tests • PHPUnit for integration tests • phpspec for unittest
- 14. phpspec basics
- 15. Installation
- 16. Create test for class WowHero
- 17. Run tests phpspec will create classes for you
- 18. Run tests generated class WowHero
- 19. Run tests Run tests again, now with generated class
- 20. Matchers (assertions) Every hero has level
- 21. Matchers phpspec will generate code for you
- 22. Matchers phpspec will generate code for you
- 23. Matchers Red
- 24. Matchers Green
- 26. Matchers • Identity (return, be, equal, beEqualTo) - === • Comparison (beLike) - == • Throw (throw -> during) - exceptions • Type (beAnInstanceOf etc.) - type • Custom matchers • http://www.phpspec.net/cookbook/matchers.html
- 27. Matchers Use source code for more matchers
- 33. Mocks Every Hero has race and class
- 34. Mocks Generate
- 35. Mocks Generate
- 36. Mocks Generate
- 37. Mocks Red
- 38. Mocks Green
- 40. Mocks Green
- 41. Mocks Refactor - let() / letgo()
- 42. Mocks Refactor - let() / letgo()
- 43. Mocks Refactor
- 44. Predictions
- 45. Predictions Red
- 47. Predictions Red
- 49. Advanced topics
- 51. Public Property Mock Sometimes you want to mock public properties
- 52. Promises and Predictions Order 1) Promises -> 2) Predictions -> 3) Call
- 53. Promises and Predictions Order 1) Promises -> 2) Predictions -> 3) Call
- 54. Promises and Predictions Order 1) Promises -> 2) Predictions -> 3) Call
- 56. Predictions Argument Wildcarding • Argument::exact($value) • Argument::type($typeOrClass) • Argument::which($method, $value) • Argument::that(callback) • Argument::any() • Argument::cetera() • https://github.com/phpspec/prophecy#arguments-wildcarding
- 59. Array Mocks Red
- 62. Get Mock Object
- 63. Get Mock Object
- 65. Get Mock Object Generate (whoops!)
- 66. Get Mock Object This is PHP, baby ???
- 67. Get Mock Object Right way
- 69. Do not use TDD in simple CRUD applications (IMHO) • High cost • Slow (in terms of development time) • Zero profit • Use functional and integration tests instead
- 70. Do not mock 3rd party code • Large complicated tests • You actually test not how your code works with this library, but how your code works with your understanding of this library
- 71. Do not mock 3rd party code Use interfaces instead of 3rd party dependent code
- 72. Consider using appropriate DI library • symfony/di and Pimple are not well suited for TDD because of large amount of small classes • you must define rule for every class, which is very boring • There are some DI containers which will create most objects without explicitly defined rules by just reading constructor arguments type hints through reflection
- 73. Consider using appropriate DI library • zend-di • Laravel IoC Container - http://laravel.com/docs/ioc • PHP-DI - http://php-di.org/
- 74. phpspec at CI