Behat c'est plus que ça | Behat is more than that
•
12 j'aime•4,731 vues
Behat is not just a tool that helps to achieve browser automation. It can be used to test the different layers of applications and to have a better understanding of the domain.
Recommandé
Contenu connexe
En vedette
En vedette (7)
Similaire à Behat c'est plus que ça | Behat is more than that
Similaire à Behat c'est plus que ça | Behat is more than that (20)
Plus de Samuel ROZE
Plus de Samuel ROZE (12)
Dernier
Dernier (20)
Behat c'est plus que ça | Behat is more than that
- 1. Behat C'est plus que ça !
- 2. Samuel Roze @samuelroze Software Engineer at Inviqa SensioLabs UK
- 5. Defines a feature with Gherkin
- 6. Creates your context file
- 7. behat.yml
- 10. Something's wrong here... Technical language
- 11. Something's wrong here... Technical language Implementation details
- 12. Describe your business behaviour, not the implementation
- 13. Using examples?
- 14. I can still use Mink!
- 15. I can still use Mink!
- 16. I can still use Mink!
- 17. I can still use Mink!
- 18. But we can use our objects
- 19. But we can use our objects
- 20. But we can use our objects
- 21. We can also uses the both! $ bin/behat -‐-‐suite=smoke order.feature behat.yml
- 22. We can also uses the both! $ bin/behat -‐-‐suite=smoke order.feature behat.yml
- 23. We can also uses the both! $ bin/behat -‐-‐suite=smoke order.feature behat.yml
- 24. Test this same behaviour on different layers
- 25. Inject Symfony2 services in context classes behat.yml OrderContext.php
- 26. Inject Symfony2 services in context classes behat.yml OrderContext.php
- 27. Inject Symfony2 services in context classes behat.yml OrderContext.php
- 28. Inject Symfony2 services in context classes
- 29. And the dependencies? Application Persistence Third Party APIs
- 30. Interfaces Instead of directly using these external dependencies, we can wrap them behind our interfaces
- 31. Using another implementation for your test suites
- 32. Using another implementation for your test suites
- 33. Using another implementation for your test suites
- 34. Using another implementation for your test suites
- 35. Using another implementation for your test suites
- 36. Using another implementation for your test suites
- 37. Using another implementation for your test suites
- 38. Use different Symfony environments
- 39. Use different Symfony environments
- 40. Use different Symfony environments
- 41. Use different Symfony environments
- 42. Use different Symfony environments $ bin/behat -‐-‐profile=smoke
- 43. Decouple the application from its dependencies
- 44. Describe your business behaviour, not the implementation Takeaways
- 45. Describe your business behaviour, not the implementation Test this same behaviour on different layers Takeaways
- 46. Decouple the application from its dependencies Describe your business behaviour, not the implementation Test this same behaviour on different layers Takeaways