Behavioural Driven Development in Zf2
•
10 likes•3,424 views
This document discusses Behavior-Driven Development (BDD) with Zend Framework 2. BDD is an evolution of Test-Driven Development (TDD) that starts with examples in natural language rather than application components. It uses a common language in a specification to communicate between stakeholders and developers. Behavioral specifications are translated into automated tests. The Behat framework allows executing these tests against a Zend Framework 2 application using the Mink extension, which supports headless and browser emulation. PHPSpec is also introduced for testing application components in a BDD style.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Behavioural Driven Development in Zf2
Similar to Behavioural Driven Development in Zf2 (20)
Recently uploaded
Recently uploaded (20)
Behavioural Driven Development in Zf2
- 1. Behavior-Driven Development with Zend Framework 2 Zend Framework Day – Turin, Italy – 07/02/2014
- 3. CLEAN CODE ADEPT BDD FANATIC 3
- 4. CLEAN CODE ADEPT BDD FANATIC 4
- 5. WHAT IS BDD?
- 7. SAME RULES 1. 7 You are not allowed to write any production code unless it is to make a failing unit test pass.
- 8. SAME RULES 1. 2. 8 You are not allowed to write any production code unless it is to make a failing unit test pass. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
- 9. SAME RULES 1. 2. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures. 3. 9 You are not allowed to write any production code unless it is to make a failing unit test pass. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.
- 11. TDD STARTS FROM COMPONENTS
- 12. CREATE THE TEST private $calculator; function setUp(){ $this->calculator = new Calculator(); } function testSumTwoPositive(){ $expectedResult = 8; $result = $this->calculator(6,2); assertEquals($expectedResult,$result); } 12
- 13. 13
- 14. WRITE QUICK, TEST VALIDATING CODE class Calculator{ public function sum($num1, $num2){ return 8; } } 14
- 15. 15
- 16. REFACTOR class Calculator{ public function sum($num1, $num2){ $sum = $num1 + $num2; return $sum; } } 16
- 17. 17
- 18. BDD STARTS FROM AN EXAMPLE
- 19. SPECIFICATION BY EXAMPLE Scenario: Add two number Given I fill number1 field with 2 And I fill number2 field with 6 When I press Add button Then the result should be 8 19
- 24. HOW IS STORY CODE RELATED?
- 25. GHERKIN Scenario: Add two number Given I fill number1 field with 2 And I fill number2 field with 6 When I press Add button Then the result should be 8 25
- 26. Interpreted in many languages 26
- 27. GHERKIN 27
- 28. GHERKIN 28
- 29. WHAT IS BEHAT?
- 31. Scenario: Add two numbers Given I fill number1 field with value of 2 TRANSLATE /** * @Given /^I fill ([^’’]*) with (d+)$/ **/ public function iFieldFieldWith($number, $fieldName) { throw new PendingException(); } 31
- 32. EXECUTION 32
- 33. USERS WILL NOT READ STORIES
- 34. THEY WILL USE AN UI
- 35. BROWSER
- 36. HOW TO TEST BROWSER WITH BEHAT? 36
- 37. HERE IT COMES, MINK!
- 38. GHERKIN + 38
- 39. Web Acceptance Test GOUTTE • Headless Browser • No Javascript • Really fast 39
- 40. Web Acceptance Test GOUTTE • Headless Browser • No Javascript • Really fast 40 SELENIUM • Can test Javascript • Really slow • Use Firefox as emulator
- 41. Web Acceptance Test GOUTTE • Headless Browser • No Javascript • Really fast 41 SELENIUM • Can test Javascript • Really slow • Use Firefox as emulator Zombie.js • Can test Javascript • Medium • Use Firefox as emulator
- 42. Web Acceptance Test GOUTTE • Headless Browser • No Javascript • Really fast 42 SELENIUM • Can test Javascript • Really slow • Use Firefox as emulator Zombie.js • Can test Javascript • Medium • Use Firefox as emulator SAHI • Can test Javascript • slow • Emulate every Browser
- 43. Scenario: Add two numbers Given I fill number1 field with 2 And I fill number2 field with 6 When I press Add button Then the result should be 8 /** * @When /^I press ‘’(/[^’’]*)’’ button$/ **/ public function iPressButton($buttonName) { $this->pressButton($buttonName); } 43
- 45. "require-dev " :{ ......... "behat/behat" : "2.4.*@stable", "behat/mink": "1.5.0", "behat/mink-extension":"*", "behat/mink-browserkit-driver":"dev-master", "behat/mink-goutte-driver":"*", "phpspec/phpspec":" 2.0.*@dev" } 45
- 46. Differs from documentation because there is a fix for ZF2 multicheckbox selection "require-dev " :{ ......... "behat/behat" : "2.4.*@stable", "behat/mink": "1.5.0", "behat/mink-extension":"*", "behat/mink-browserkit-driver":"dev-master", "behat/mink-goutte-driver":"*", "phpspec/phpspec":" 2.0.*@dev" } 46
- 47. Mink Setup behat.yml default : extensions : BehatMinkExtensionExtension : base_url : 'http://example.com' goutte : ~ 47
- 48. + + 48
- 49. Static method private static app; /** * @BeforeSuite **/ public static function initializeZf(){ If(self::$zendApp === null){ $path = __DIR__ .’/../../config/application.config.php’; self::app = ZendMvcApplication::init(require $path); } } 49
- 50. ZF2 EXTENSION
- 52. Zf2 Behat Extension behat.yml default : extensions : MvLabsZf2ExtensionZf2Extension : config : config/application.config.php module : 52
- 53. Zf2 Behat Extension run from console bin/behat --init ‘’module name’’ 53
- 54. Feature Context Implements Zf2AwareContextInterface class FeatureContext extends MinkContext implements Zf2AwareContextInterface{ private $zf2MvcApplication; ......... public function setZf2App(Application $zf2MvcApplication) { $this->zf2MvcApplication = $zf2MvcApplication; } } 54
- 55. WE STILL NEED TO TEST OUR COMPONENTS
- 56. GHERKIN + 56
- 57. WHY PHPSPEC? 57
- 58. BDD BASED ON BEHAVIOUR DESCRIPTION Robert C. Martin
- 59. PHPUnit focus on testing code private $calculator; function setUp(){ $this->calculator = new Calculator(); } function testSumTwoPositive(){ $expectedResult = 8; $result = $this->calculator(6,2); assertEquals($expectedResult,$result); } 59
- 60. PHPSpec focus on code behavior function let(){ $this->shouldBeConstructed(); } function it_sum_two_positive_number(){ $this->sum(2,6)->shouldReturn(8); } 60
- 61. Subject under Specification "It’s this unexisting object, on which you’re calling unexisting methods and assuming future outcomes. Most important thing? There could be only one SUS in specification" Kostantin Kudryashov 61
- 62. Developer Tool Vs Testing Framework 62
- 63. Autogenerates classes & methods bin/phpspec desc ‘’ApplicationControllerIndexController’’ 63
- 65. Demeter Law's Violation function let(){ $this->shouldBeConstructed(); } function it_sum_two_positive_number(){ $this->getPlayer()->getSword()->shouldBeInstanceOf(‘Sword’); } 65
- 67. Add PHPSpec to Zf2 + 67
- 68. "require-dev":{ ........... "phpspec/phpspec" : "2.0.*@dev" }, "config": { "bin-dir": "bin/" }, "autoload": { "psr-0" { "Application" : " module/Application/src" } } 68
- 69. Add a single module ’’require-dev’’:{ "require-dev":{ ........... ... "phpspec/phpspec" : "2.0.*@dev" "phpspec/phpspec":" 2.0.*@dev" }, }, "config": { "config": { "bin-dir": "bin/" "bin-dir": "bin« }, }, "autoload": { { "autoload": "psr-0" { { "psr-0": "Application" : " module/Application/src" "Application": "module/Application/src" } } }} 69
- 70. Add more modules "require-dev":{ ........... "phpspec/phpspec" : "2.0.*@dev" }, "config": { "bin-dir": "bin/" }, "autoload": { "psr-0" { "Application" : " module/Application/src", "Calculator" : "module/Calculator/src" } } 70
- 71. Create phpspec.yml in project root formatter.name : progresssuites Application: namespace : Application spec_prefix : Spec src_path : 'module/Application/src/' spec_path : 'module/Application/' ModuleDemo: namespace : ModuleDemo spec_prefix : Spec src_path : 'module/ModuleDemo/src/' spec_path : 'module/ModuleDemo/' 71
- 72. What to test with PHPSpec? 72
- 73. What to test with PHPSpec? 1.Model Logic 73
- 74. What to test with PHPSpec? 1.Model Logic 2.Factories 74
- 75. What to test with PHPSpec? 1.Model Logic 2.Factories 3.Validation 75
- 76. Behat bad practices 1. Verbose Stories 2. Using Mink to test REST calls 3. Testing every possible usages combination 4. Fixture loading within Context 76
- 77. WHY TESTING?
- 78. IT’S A TREND
- 80. RELAX
- 81. SOMEONE WILL READ YOUR CODE
- 82. IT COULD BE YOU SOME DAY
- 83. YOUR COLLEAGUES
- 84. OR 84
- 85. A VIOLENT PSYCHOPATH WHO KNOWS WHERE YOU LIVE
- 87. Thank you for your attention David Contavalli @mauipipe
- 88. QUESTIONS?
- 90. Some readings 90