Seeding a Tree in a Gherkin
Download as PPTX, PDF0 likes433 views
The document discusses strategies for setting up automated tests, focusing on using Gherkin syntax to clarify scenarios and ensure effective test case management. It outlines various approaches, such as common test data sets, setup methods, and builders, highlighting the importance of readability and maintainability in test specifications. The document also emphasizes engaging the reader and iterating on designs to improve test structures.
Seeding a Tree in a Gherkin
- 1. www.techtalk.at Setting up Complex Scenarios for Automated Tests Paul Rohorzka Software Gardener February 22nd, 2017 Seeding a Tree in a Gherkin @paulroho pro@techtalk.at
- 3. 3 What is right? Make it right Is it right? Requirements Engineer Product Owner Developer Tester QA PM Testautomation Engineer Architect
- 4. 4 Arrange Act Assert Setup Execute Verify What is right? Make it right Is it right? Given When Then By original uploader: Roke - Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=31996181
- 5. 5 Setup Execute Verify Given When Then Arrange Act Assert Three Parts of an Automated Test What is the scenario? What should trigger the behaviour? Important question: How are they related? Can I actually observe what I expected?
- 8. 8 Setup Check This talk ... and a little bit ... It's Often Like This
- 10. 10 What Are My Options?
- 11. 11 Can feel clean (???) Hidden Setup Incomplete Scenario Obscuring important parts Dependencies State?! What if scaling out? Classical Option 1: Common Test Data Set Data B Data C Data A Data Y Data X Data Z Test 2 Test 3 Test 1 Test 98 Test 97 Test 99 Code, Database, File, ...
- 12. 12 Easy to get via refactoring Gets quickly out of hand (overloads, optional parameters, ...) Classical Option 2: Setup Method
- 13. 13 Can be easily extended (as domain grows) IDE can help (Intellisense) Initial effort Needing multiple parts of complex structure Classical Option 3: Builders
- 15. 15 No Matter What – Think of the Reader! What would we like to read? Write it down! Do we like it? Fix the syntax! Do we still like it? Make it work! Imagine Engage Accomplish
- 16. 16 Use whatever works best for the people involved https://flic.kr/p/47xDKh
- 18. Act 1: Specifying a C# API
- 19. Structure of an Organization "Org Units"
- 20. 20 Specifying the InfoManager API InfoManager Client C# API Specs
- 21. 21 The Obvious Approach: Unit Tests
- 22. 22 The Obvious Approach: Unit Tests
- 23. 23 • Where is the code under test? • How let the spec stand out from other low-level unit tests? • The client app's developer is the user of your API • The interface might be subject of a conversation • It defines the behaviour (i.e. more than the static contract) Give Gherkin a try! Considerations
- 24. 24 Interlude: The Gherkin Language Given When Then
- 25. 25 Connecting Gherkin With Code "Step Bindings"
- 26. 27 Our Take – The Specs
- 27. 28 Our Take – One More
- 28. 29 • Bindings might get increasingly messy • Refactoring can make the specs wrong Some Downsides
- 29. 30
- 30. Act 2: Building a Permission Chain https://flic.kr/p/4SxU1r
- 31. Introducing PERSY (PERmission SYstem) • 6 chained objects • Each active/inactive • Ignore chain if one object is inactive User Position AD-Group Groupm:n m:n
- 32. 33 Setup in 6 one-liners?
- 34. 35 Super entity PermissionChain User Position AD-Group Groupm:n m:n PermissionChain
- 37. 38 String Representation in Unit Testing Style
- 39. 40 The Catch Fragile! Meta tests Is it worth it? Yes, if this is part of the core domain 1 out of 50+!
- 40. 41 A Meta Test
- 41. 42
- 42. Act 3: Seeding A Tree https://flic.kr/p/ooBmLt
- 43. 44 Testing a Feature Based on a Tree Structure "Org Units"
- 45. 46 Obvious Approach: Domain Model API
- 49. 50 Away With the Parent References
- 50. 51 Away With That Many Columns
- 51. 52 Away With the Table
- 52. 53 Away With the Dots
- 54. 55
- 55. 56 Is It Worth The Trouble? ReadabilityEase of Usage Effort of Implementation Living Documentation maintain extend discover edit
- 56. 57 Build ReflectDecide Hint: Iterate! Don't try to build too much magic up front!
- 57. 58 Put First What You Would Love to See Not What You Have. By Mstyslav Chernov - Self-photographed, http://mstyslav-chernov.com/, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=28541140
- 59. 60