• Profile manager
• Phase 'ListEmptyProfile'
  • Customer
    • Given list profile empty
      • When visit list profile page then
  • Developer
    • Make application skeleton
    • Write specification code for "ListEmptyProfile"
    • Run unit-test
    • Quick & dirty way to write production code
    • Run unit-test
    • Refactoring code
    • Run unit-test again
• Phase 'ListNonEmptyProfile'
  • Customer
    • Given list profile not empty
      • Profile info need display
      • When visit list profile page then
  • Developer
    • Write specification code for "ProfileListPageIntergrateDbTest"
    • Run unit-test
    • Quick & dirty way to write production code
    • Run unit-test
    • Refactoring code
    • Run unit-test again
• Phrase create profile
  • Customer
    • Need Create Profile Page
    • Show form profile when visit
  • Developer
    • Write specification code for 'create-profile-page'
      • When use visit create profile page then show form profile
      • Run Unit-test
    • Quick & dirty way to write production code
      • Run Unit-test again
    • Refactoring code
      • Run Unit-test again
  • Customer
    • User submit invalid profile to system
    • User submit valid profile to system
  • Developer
    • Write specification submit bad profile to 'create-profile-page'
    • Write inject invalid profile form Then isValid() return false
    • Write inject invalid profile form Then getMessages() return all invalid message
• Phase edit profile
• Phase delete profile

Profile manager

Practical TDD - git flow - markdown

Phase 'ListEmptyProfile'

Customer

Given list profile empty

When visit list profile page then

1. I want to see page title 'list profile'
2. I want to see web page display "Empty list profile"

Developer

Make application skeleton

1. Install automation tool
2. Download composer.phar
3. Install composer package

• phing
• phpunit
• zend framework 1

4. Write phing task phpunit

Write specification code for "ListEmptyProfile"

1. Create tests/application/controller/ProfileListPageTest.php
2. When visit list profile page then

• expected response code equals 200
• expected request handler by
  • index action
  • profile controller
  • default module
• expected response content
  • contain title 'Profile list'
  • contain 'empty profile list'

Run unit-test

expected test failed

Quick & dirty way to write production code

1. Create ProductController
2. Create index action
3. add head title
4. add 'Empty list profile' to index.phtml

Run unit-test

expected test success

Refactoring code

add html layout

Run unit-test again

expected test success

Phase 'ListNonEmptyProfile'

Customer

Given list profile not empty

Profile info need display

• Profile id
• Profile fullname
• Profile age
• Profile email

When visit list profile page then

• i want to see all profile list
• table head bold

Developer

Write specification code for "ProfileListPageIntergrateDbTest"

1. Create tests/application/controller/ProfileListPageIntergrateDbTest.php
2. When visit list profile page then

• expected response content
  • contain table with thead tag
  • contain thead > th with 'id'
  • contain thead > th with 'fullname'
  • contain thead > th with 'age'
  • contain thead > th with 'email'

Run unit-test

expected test failed

Quick & dirty way to write production code

1. Find and add phinx to composer.json (require-dev)
2. Create scripts/build/sql/create-database.sql
3. Create script CreateProfileTable in scripts/build/migrations by phinx
4. Add Application_Model_DbTable_Profile
5. Fill code to index action
6. Fill code to index.phtml

Run unit-test

expected test success

Refactoring code

1. in profile/index.phtml switch case to display message 'profile list empty' or display table profile.

Run unit-test again

Phrase create profile

Customer

Need Create Profile Page

Show form profile when visit

Developer

Write specification code for 'create-profile-page'

When use visit create profile page then show form profile

• Expected response code 200
• Expected request handler by create action, profile controller, default module
• Expected response content contains:
  • Hidden field name=id with value blank
  • Text field name=fullname with value blank
  • Text field name=age with value blank
  • Text field name=email with value blank

Run Unit-test

expected test failed

Quick & dirty way to write production code

1. add method createAction to ProfileController
2. create file view/scripts/profile/create.phtml
3. make html form in file view/scripts/profile/create.phtml

Run Unit-test again

expected test success

Refactoring code

Run Unit-test again

expected test success

Customer

User submit invalid profile to system

When user submit invalid profile Then re populate profile form And show error message

Profile form validation requirement

• dob contains date time (yyyy-MM-dd)
• email contains valid email only
• full-name contain alpha characters only

User submit valid profile to system

When user submit valid profile Then system persist profile And system redirect to list profile page

Developer

Write specification submit bad profile to 'create-profile-page'

1. Setup post request, inject invalid data
2. Expected response content contains error area
3. Expected response content contains Profile Form full fill

Write inject invalid profile form Then isValid() return false

Write inject invalid profile form Then getMessages() return all invalid message

Phase edit profile

Stop write step by step here :D ()

Phase delete profile