Downloaded 31 times
Uploaded byAnton Serdyuk
TDD with phpspec2
This document provides an overview of test-driven development (TDD) using the phpspec2 framework. It discusses the different types of tests - functional tests using phpunit or behat, integration tests with PHPUnit, and unit tests with phpspec. It provides examples of writing unit tests with phpspec, including using matchers, mocks, predictions, and advanced features like array mocks. It also offers best practices advice, such as not mocking 3rd party code and considering dependency injection libraries that are well-suited for TDD.
More Related Content
TDD with phpspec2
- 1.
- 2. Who I am •Anton Serdyuk • email/jabber: anton.serdyuk@gmail.com • skype: serdyuk.anton • twitter: @anton_serdyuk • facebook: anton.serdyuk
- 3.
- 4. Auto-tests forms • Functionaltests (+BDD) • Integration tests • Unit tests
- 5. Functional tests • Usefull deployed application instance • Test business expectations • Use the same UI interactions as real user
- 6. Functional tests withphpunit example
- 7. BDD (or storyBDD) • Story-driven functional tests • BDD ⊂ Functional tests
- 8. BDD with behatexample
- 9. Integration tests • Useintegrated parts of applications • Can use database, filesystem etc. • Can test API, Doctrine repositories etc.
- 10. Integration tests withPHPUnit example
- 11. Unit tests • Usesmall parts of code • Can not use database • Can not use filesystem • Extremely fast
- 12. Consider using appropriate toolsfor 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.
- 15.
- 16. Create test for classWowHero
- 17. Run tests phpspec willcreate classes for you
- 18. Run tests generated classWowHero
- 19. Run tests Run testsagain, now with generated class
- 20. Matchers (assertions) Every herohas level
- 21. Matchers phpspec will generatecode for you
- 22. Matchers phpspec will generatecode for you
- 23.
- 24.
- 25.
- 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 codefor more matchers
- 28.
- 29.
- 30.
- 31.
- 32.
- 33. Mocks Every Hero hasrace and class
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41. Mocks Refactor - let()/ letgo()
- 42. Mocks Refactor - let()/ letgo()
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51. Public Property Mock Sometimesyou want to mock public properties
- 52. Promises and PredictionsOrder 1) Promises -> 2) Predictions -> 3) Call
- 53. Promises and PredictionsOrder 1) Promises -> 2) Predictions -> 3) Call
- 54. Promises and PredictionsOrder 1) Promises -> 2) Predictions -> 3) Call
- 55.
- 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
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65. Get Mock Object Generate(whoops!)
- 66. Get Mock Object Thisis PHP, baby ???
- 67.
- 68.
- 69. Do not useTDD in simple CRUD applications (IMHO) • High cost • Slow (in terms of development time) • Zero profit • Use functional and integration tests instead
- 70. Do not mock3rd 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 mock3rd party code Use interfaces instead of 3rd party dependent code
- 72. Consider using appropriate DIlibrary • 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 DIlibrary • zend-di • Laravel IoC Container - http://laravel.com/docs/ioc • PHP-DI - http://php-di.org/
- 74.
- 75.
- 76.