Driving Your Domain by Examples - Code Mastery Meetup

This is the same talk I've delivered twice before, but with some improvements. This version was delivered at the Code Mastery meetup and can be seen online here https://www.youtube.com/watch?v=EUYE0cFQbiU

Transcript

1. Sample Title Code Mastery Meetup Driving your domain by examples
2. Code Mastery Meetup Marco Lopes Technical Team Lead - Inviqa @mpmlopes Marco Lopes
3. Look at all these green fields
4. Change all things!
5. How did I end up here?
6. Why don’t they stop changing their minds?
7. It’s actually fair and normal to have change.
8. How can we deal with change, then?
9. Short feedback cycle
10. Short feedback cycle AKA Agile
11. What else can we do?
12. Shorten feedback cycle
13. BDD Refactor Story level Spec level
14. Behat & PHPSpec
15. Modelling by Example
16. Story level BDD
17. Domain Suite
18. Scenario: Paying with a credit card
 Given AwesomePay has credit card payments enabled
 When I fill the credit card number with 4444333322221111 And I fill the expiry date with ”04/2018” And I fill the CCV with 123 And the credit card has unlimited funds on payment gateway
 And I press place order button
 Then the payment should be accepted
19. Scenario: Paying with a credit card
 Given AwesomePay has credit card payments enabled
 When I fill the credit card number with 4444333322221111 And I fill the expiry date with ”04/2018” And I fill the CCV with 123 And the credit card has unlimited funds on payment gateway
 Then the payment should be accepted
20. Scenario: Paying with a credit card
 Given AwesomePay has credit card payments enabled
 When I have credit card 4444333322221111 And the credit card has unlimited funds on payment gateway
 Then the payment should be accepted
21. Scenario: Paying with a credit card
 Given AwesomePay has credit card payments enabled
 And I have credit card 4444333322221111 And the credit card has unlimited funds on payment gateway When I pay £42 using that credit card
 Then the payment should be accepted
22. Scenario: Paying with a credit card
 Given the payment gateway has credit card payments enabled
 And I have credit card 4444333322221111 And the credit card has unlimited funds on payment gateway When I pay £42 using that credit card
 Then the payment should be accepted
23. AwesomePay Framework Interfaces Interfaces Domain
24. Scenario: Paying with a credit card
 Given the payment gateway has credit card payments enabled
 And I have credit card 4444333322221111 And the credit card has unlimited funds on payment gateway When I pay £42 using that credit card
 Then the payment should be accepted
25. /**
 * @Given the payment gateway has credit card payments enabled
 */
 public function thePaymentGatewayHasCreditCardPaymentsEnabled()
 {
 $this->paymentGateway = new FakePaymentGateway();
 expect( $this->paymentGateway->HasCreditCardPaymentsEnabled() )->toBe(true);
 }
26. /**
 * @Given I have credit card :aCreditCard
 */
 public function iHaveCreditCard(CreditCard $aCreditCard)
 {
 $this->creditCard = $aCreditCard;
 }
27. /**
 * @Transform :aCreditCard
 */
 public function transformNumberToCreditCard($cardNumber)
 {
 return CreditCard::fromNumber($cardNumber);
 }
28. CreditCard::fromNumber($cardNumber); Named Constructor
29. /**
 * @Given the credit card has unlimited funds on payment gateway
 */
 public function theCreditCardHasUnlimitedFundsOnPaymentGateway()
 {
 $this->paymentGateway->cardHasUnlimitedCredit( $this->creditCard );
 }
30. Scenario: Paying with a credit card
 Given the payment gateway has credit card payments enabled
 And I have credit card 4444333322221111 And the credit card has unlimited funds on payment gateway When I pay £42 using that credit card
 Then the payment should be accepted
31. Scenario: Paying with a credit card
 Given the payment gateway has credit card payments enabled
 And I have credit card 4444333322221111
 And the payment gateway has unlimited credit for that card
 When I pay £42 using that credit card
 Then the payment should be accepted
32. /**
 * @Given the payment gateway has unlimited credit for that card
 */
 public function thePaymentGatewayHasUnlimitedCreditForThatCard()
 {
 $this->paymentGateway->hasUnlimitedCreditFor( $this->creditCard );
 }
33. Benefits?
34. Code closer to the business language
35. Code changes when business changes
36. Emergent design
37. Decoupling
38. AwesomePay ZF Interfaces Interfaces Domain
39. AwesomePay Symfony 2 Interfaces Interfaces Domain
40. AwesomePay Symfony 2 Interfaces Interfaces Domain
41. Mitigates communication problems
42. Easier development
43. Docs for free
44. Test for free
45. Easier QA
46. Respond to change
47. How about e2e tests?
48. default:
 suites:
 domain:
 contexts: [DomainContext]
49. default:
 suites:
 domain:
 contexts: [DomainContext] 
 web:
 contexts: [WebContext]
 filters: { tags: '@web' }
50. default:
 suites:
 domain:
 contexts: [DomainContext] filters: { tags: '~@ui' }
 web:
 contexts: [WebContext]
 filters: { tags: '@web' }
51. default:
 suites:
 domain:
 contexts: [DomainContext] filters: { tags: '~@ui' }
 web:
 contexts: [WebContext]
 filters: { tags: '@web' } mobile:
 contexts: [MobileContext]
 filters: { tags: '@mobile' }
52. default:
 suites:
 domain:
 contexts: [DomainContext] filters: { tags: '~@ui' }
 web:
 contexts: [WebContext]
 filters: { tags: '@web' } mobile:
 contexts: [MobileContext]
 filters: { tags: '@mobile' } integration:
 contexts: [IntegrationContext]
 filters: { tags: '@ui' }
53. In sum
54. Bounded domain
55. Decoupled parts of our application
56. Decoupling from frameworks
57. Better understanding of the business domain
58. Reduction of communication gaps
59. Easier development
60. Quicker CI builds