Skip to content

Latest commit

 

History

History
44 lines (33 loc) · 3.18 KB

Module-06.md

File metadata and controls

44 lines (33 loc) · 3.18 KB

Module 6: Test Driven Development (TDD)

Getting Started

Prior to completing the module below it is highly recommended that you look at the following learning material:

Completing the Module

  1. Create a new branch in your php-final Git repo called TDD and commit all the work from this module there.
  2. Be sure to write your code to conform to the PSR-2 spec.
  3. Use Composer to install Mockery, PHPUnit and fzaninotto/Faker. Your composer.json and composer.lock files should be part of this project.
  4. Add a folder called tests where all your test code will go.
  5. Add a test class for your previous model.
  6. Add a method to the test class to test model validation; use Faker to set properties:
    • Create a new instance of your model and assert that validation initially fails.
    • Assert that an error exists for each particular property where validation is failing.
    • One by one, set each required property correctly and assert that the error does not exist.
    • When all required properties are set, assert that validation passes.
  7. Add a method that tests that the model's save() and destroy() methods are inserting, updating and deleting in the database correctly:
    • Assert that the model's database table is empty, or note the number of records. Do this before your actions to save or delete to help ensure that the data in your database is actually changing correctly.
    • Create a new instance of your model, populate the properties with Faker and call save(); assert that the record was inserted into the database.
    • Update the object and call save(); assert that the data in relevant table row has been updated correctly AND that no additional records were inserted.
    • Call the destroy() method on the model and assert that the record has been removed from the database table.
  8. Refactor your code to use dependency injection and the Repository pattern:
    • Create a Repository interface. This should require a model as a dependency and will interact with the database through the model. This should define the crud methods that you’re already using on the model.
    • Create a Repository class that implements the Repository interface.
    • Refactor your controller(s) to use the Repository instead of your model.
  9. Add a new test that tests your Repository. Create a mock of your model and pass it into your Repository as it’s dependency. Test the create, find, update and delete functionality of your Repository without actually hitting the database.

Wrapping Up

When you are done, push your code to GitHub. Please create a tag called v1.4 with a message of "ready for review". Be sure your tags are pushed to the remote repository and are visible in GitHub.

Create an issue titled Review Module 6 - Testing Driven Development and assign it to @generationtux-helmsmen.