Testing persistence in PHP with DbUnit
Download as PPT, PDF3 likes5,511 views
The document discusses different strategies for testing persistence in PHP applications, including unit testing with mocks and dependencies, integration testing using DbUnit to insert test data and assert expected results, and techniques for setting up common initial states across tests. It also covers the benefits and downsides of different types of tests, such as layer crossing tests that test interactions across layers but may be more brittle, versus end-to-end black box tests that test through the public API but are harder to debug.
![Test case init class RemoverDaoTest extends DatabaseTestCaseBase { /** * @return PHPUnit_Extensions_MultipleDatabase_Database[] */ protected function getDatabaseConfigs () { return array ( $this -> getDbConfigBuilder () -> connection ( $this -> getCentralDbConnection ()) -> dataSet ( $this -> createXmlDataSet ( 'init.xml' )) -> build () ); }](https://image.slidesharecdn.com/testingpersistencephpunitdbunit-120118032934-phpapp01/85/Testing-persistence-in-PHP-with-DbUnit-12-320.jpg)
![[email_address] twitter.com/pepov](https://image.slidesharecdn.com/testingpersistencephpunitdbunit-120118032934-phpapp01/85/Testing-persistence-in-PHP-with-DbUnit-29-320.jpg)
Testing persistence in PHP with DbUnit
- 1. Testing persistence (in PHP) PHPUnit & DbUnit
- 2. Our story by unit testing classes Started from inside to the outside
- 3. Tools and principles Using PHPUnit with Mock objects to isolate the SUT Design for testability (SOLID) Use the front door first One condition per test http://xunitpatterns.com/Principles of Test Automation.html http://en.wikipedia.org/wiki/SOLID_(object-oriented_design)
- 4. PHPUnit class TestClass extends PHPUnit_Framework_TestCase { public function setUp () {} public function testMethod () {} public function tearDown () {} }
- 5. Problems No integration guarantees Not effective for refactoring legacy code Does not ensure external quality
- 6. Need for integration tests To ensure external quality from top to bottom
- 7. Unit testing DAOs with DI and mocks $connection = createMockExpecting( " INSERT INTO table SET field = 'value' " ); $dao = new Dao( $connection ); $dao -> insert ( 'value' ); Tells nothing about the database interaction
- 8. Testing DAOs - injected connection $connection = createLocalTestConnection(); $dao = new Dao( $connection ); $dao -> insert ( 'value' ); assertInsertedValueMatches( 'value' ); Hard to replace in end to end tests
- 10. Testing DAOs - dependency lookup $dao = new Dao(); $dao -> insert ( 'value' ); assertInsertedValueMatches( 'value' ); http://xunitpatterns.com/Dependency Lookup.html
- 11. DbUnit + Etsy extensions
- 12. Test case init class RemoverDaoTest extends DatabaseTestCaseBase { /** * @return PHPUnit_Extensions_MultipleDatabase_Database[] */ protected function getDatabaseConfigs () { return array ( $this -> getDbConfigBuilder () -> connection ( $this -> getCentralDbConnection ()) -> dataSet ( $this -> createXmlDataSet ( 'init.xml' )) -> build () ); }
- 13. Datasets user: - id: 1 name: Ingrid <dataset> <table name= "user" > <column> id </column> <column> name </column> <row> <value> 1 </value> <value> Ingrid </value> </row> </table> </dataset> MySQL XML YAML
- 14. Assertions public function testRemoveNoProblem () { $remover = new RemoverDao(); $remover -> removeUser ( 1 ); $this -> assertDataSetsEqual ( $this -> createYamlDataSet ( 'empty.yml' ), $this -> getCentralDbConnection () -> createDataSet ( array ( 'user' )) ); }
- 15. Datasets user: - id: 1 name: Ingrid created_at: 2012-01-16 <dataset> <table name= "user" > <column> id </column> <column> name </column> <column> created_at </column> <row> <value> 1 </value> <value> Ingrid </value> <value> 2012-01-16 </value> </row> </table> </dataset> MySQL XML YAML
- 16. Dataset filter $datasetFilter = new PHPUnit_Extensions_Database_DataSet_DataSetFilter( $dataset ); $datasetFilter -> addIncludeTables ( array ( 'user' ) ); $datasetFilter -> setExcludeColumnsForTable ( 'user' , array ( 'created_at' ) );
- 17. Datasets user: - id: 1 name: Ingrid created_at: ##TIME## <dataset> <table name= "user" > <column> id </column> <column> name </column> <column> created_at </column> <row> <value> 1 </value> <value> Ingrid </value> <value> ##TIME## </value> </row> </table> </dataset> MySQL XML YAML
- 18. Replacement dataset $replacementDataset = new PHPUnit_Extensions_Database_DataSet_ReplacementDataSet ( $dataset , array ( '##TIME##' => TimeService::time ()) );
- 19. Implicit setup Common initial state, extended test-by-test Hard to share
- 20. Inline setup Define only the tables being used in common setup Insert all the necessary data inline in the test method Still messy to share common datasets with xml or yml Minimal fixture!
- 21. Inline datasets with PHP Value objects + builders Convert to dataset for: inserting into database using in assertions
- 22. Setup $user = UserBuilder :: create () -> build (); $video = VideoBuilder :: create () -> owner ( $user ) -> private () -> build (); TestDataInserter :: create (getCentralDbConnection()) -> add ( 'user' , $user ) -> add ( 'video' , $video );
- 23. Excercise VideoPublisherDao :: create () -> publish ( $video -> id ); Http service DAO HttpClient :: create () -> call ( 'Video::publish' , $video -> id );
- 24. Verify assertDataSetsEqual( $this -> createDataSet ( 'video' , $video ), $this -> getCentralDbConnection () -> createDataSet ( array ( 'video' )) );
- 25. Layer crossing tests - where we use it Http services Daemons Cron jobs Ajax calls
- 26. The power of layer crossing tests Refactoring (legacy) code Increasing code coverage
- 27. There are downsides too We use the back door => risk of overspecification Empty initial state hides concurrency problems parallel testing more difficult
- 28. Concurrent end-to-end black box tests Uses only the front door (public api) Isolation with unique identifiers & Δ assertions Tests real concurrency Harder to track bugs & intermittent tests http://engineering.imvu.com/2011/01/19/buildbot-and-intermittent-tests/