Javantura v7 - Behaviour Driven Development with Cucumber - Ivan Lozić
0 likes846 views
Javantura v7 - Behaviour Driven Development with Cucumber - Ivan Lozić Behaviour-Driven Development (or TDD for that matter) is one of the pillars of Software Quality. While it is very important, not many of us do it or do not have the support from the management to invest time in it. Commonly, it has been described as a waste of time or an intangible effort conflicting with the deadlines. In this presentation, I would like to share my experiences with the Behaviour-Driven Development, the effects of not having it at all, as well as the outcomes of working on projects where a significant amount of behavior is automated with Cucumber tool. By attending this session you will be able to learn what BDD and Cucumber are, how to build Cucumber tests and hear about first-hand experiences around automating specifications.
![[241] AI 칩 개발에 사용되는 엔지니어링](https://cdn.slidesharecdn.com/ss_thumbnails/241deview2018furiosafinal-181012001208-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (20)
Similar to Javantura v7 - Behaviour Driven Development with Cucumber - Ivan Lozić (20)
Ad
More from HUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association (20)
Ad
Recently uploaded (20)
Javantura v7 - Behaviour Driven Development with Cucumber - Ivan Lozić
- 1. Ivan Lozić, CEO of Deegloo BDD with Cucumber [email protected]
- 2. Who am I? - CEO of Deegloo - software agency - Software Engineer with ~10 years of professional experience - .Net, iOS developer, Java - Software Architect - Car Industry, Dairy Industry
- 3. - Software Development Agency - Developing US Dairy Industry products - Web, Mobile and Data Science Source: Dairy.com What Does Deegloo Do?
- 4. Behavior Driven Development “Agile Software Development Process which encourages collaboration between developers, QA and non-technical people” Source: Wikipedia
- 5. User Story As a (type of user), I would like to be able to (do some action), so that I can (achieve some goal or get some result) Acceptance Criteria Scenario: Given … When I ... Then...
- 6. Collaboration BDD specs are written in simple, descriptive text and are understandable by non-technical people PO/PM, Sales, ...
- 7. Specification by Example Collaborative approach of... Capturing and illustrating requirements through realistic examples instead of abstract statements So, why does this matter? - Human brains are generally not that great at understanding abstractions
- 8. How does BDD relate to TDD? Emerged from TDD Both are test first approach BDD focuses on behavior, and not on implementation i.e. BDD tests product from users perspective, instead of testing the code i.e. BDD doesn’t care about how a particular output is created, only that it is correct under specified conditions
- 9. Cucumber A tool which supports BDD Enables writing specifications Integrates with IntelliJ, Eclipse, Jira, ...
- 10. Gherkin - Domain specific language - Helps describing business behaviour without going into technical details - Acts like a living documentation Basic Gherkin Syntax ● Feature ● Scenario ● Given ● When ● Then
- 11. IDE Integration and Test Setup Example with IntelliJ
- 12. Cucumber + Gherkin An Example
- 13. Cucumber + Gherkin It still requires coding :)
- 14. Cucumber + Gherkin It still requires coding :)
- 15. Cucumber + Gherkin Running the Spec
- 16. Cucumber + Gherkin Running the Spec
- 17. Real World Example - FC Tracker is a tool used by brokers allowing for Milk Commodity trading at the Market Exchange - ~1 year of development - We combined JUnit Integration tests and Cucumber specs - 394 Integration tests - 128 Cucumber scenarios in 49 features - All tests running against in-memory H2 database Forward Contracting Tool
- 18. Real World Example Forward Contracting Tool
- 19. Controller Service Repository db Specification Real World Example Forward Contracting Tool
- 20. Real World Example Learnings - Overall a positive experience - It takes initial learning time before becoming productive - Integrating all layers makes sense - Steps are reusable across features, need to be careful about naming them - Choosing correct wording matters to make specs readable
- 21. BDD and Cucumber Sound Good? Still, not many of us do it in the industry...
- 22. The Typical Excuse We don’t have enough time to write tests
- 23. Understood, however... Let’s consider the following scenarios
- 24. Scenario 1 Cognitive Limitation Human beings are cognitively limited We can process only so much at the particular moment Do we want to focus on identifying behaviors through examples OR do we want to jump into implementation immediately?
- 25. Scenario 2 Collaborating with PO My experience: working together with PO on defining all acceptance tests for free-text search functionality
- 26. Scenario 3 Fear of Refactoring Programming is hard… Understanding other people’s (bad) code is even harder...
- 27. Scenario 3 Fear of Refactoring ● Early refactoring is crucial ● Not improving the code over time leads to unhealthy platform and bugs ● Bugs take time, rewriting pieces of software consume even more time ● BDD specs protect behavior and encourage refactoring As a developer, I feel safe knowing there are tests which will ensure behavior remains intact after my code refactoring
- 28. Scenario 4 Rapid Issue Tracing
- 29. Scenario 4 Rapid Issue Tracing ● Challenges to reproduce the issue: ○ This is production environment ○ There is a background job generating PDF ○ PDF is sent at the end of the business day in the email inbox ● We don’t need to setup anything, there is already cucumber tests for each report
- 30. Scenario 4 Rapid Issue Tracing
- 31. Scenario 4 Rapid Issue Tracing
- 32. Scenario 4 Rapid Issue Tracing Adding Settlement in July of 2019 - test passes Removing Settlement from July of 2019 - test fails
- 33. Scenario 4 Rapid Issue Tracing ● No need to have production data for debugging - focus is on behavior and minimal amount of data to represent a behavior ● No need to have complete workflow setup locally - simply play with Cucumber test ● Ability to validate assumptions running tests with different inputs ● Ability to present and confirm results with PM/PO before applying fix
- 34. Scenario 5 Employee Turnover My experience: Replacing existing search engine within a relatively new team
- 35. Scenario 5 Employee Turnover People leave companies, teams change significantly Automated specs can serve as a living documentation that remains for new people Automated specs save you time and avoid angry calls
- 36. The one thing you should bring with you from this talk is...
- 37. Never forget about the cucumbers!
- 39. Ivan Lozić, CEO of Deegloo [email protected] Thank you for your attention.