Cornichon - A scala DSL for testing HTTP JSON API

Transcript

1. Cornichon A scala DSL for testing HTTP JSON API Berlin Scala User Group
 11.01.2017 @ArnaudGourlay
2. Brief history 2
3. Brief history • Building an e-commerce API @commercetools 2
4. Brief history • Building an e-commerce API @commercetools • Important Ruby Cucumber codebase 2
5. Brief history • Building an e-commerce API @commercetools • Important Ruby Cucumber codebase • Lack of Ruby expertise 2
6. Brief history • Building an e-commerce API @commercetools • Important Ruby Cucumber codebase • Lack of Ruby expertise • Difficulty to scale a DSL based on String parsing 2
7. Brief history • Building an e-commerce API @commercetools • Important Ruby Cucumber codebase • Lack of Ruby expertise • Difficulty to scale a DSL based on String parsing • Lack of enthusiasm for writing acceptance tests 2
8. Brief history • Building an e-commerce API @commercetools • Important Ruby Cucumber codebase • Lack of Ruby expertise • Difficulty to scale a DSL based on String parsing • Lack of enthusiasm for writing acceptance tests • Frustration breeds creativity… 2
9. Need for a different tool? 3
10. Need for a different tool? • In Scala! 3
11. Need for a different tool? • In Scala! • Code over plain text 3
12. Need for a different tool? • In Scala! • Code over plain text • Powerful built-in DSL 3
13. Need for a different tool? • In Scala! • Code over plain text • Powerful built-in DSL • Extensible DSL 3
14. Need for a different tool? • In Scala! • Code over plain text • Powerful built-in DSL • Extensible DSL • Great error reporting 3
15. Need for a different tool? • In Scala! • Code over plain text • Powerful built-in DSL • Extensible DSL • Great error reporting • Maintainable acceptance tests 3
16. Need for a different tool? • In Scala! • Code over plain text • Powerful built-in DSL • Extensible DSL • Great error reporting • Maintainable acceptance tests • Smooth integration in a build pipeline 3
17. First commit 4
18. Live demo 5
19. Live demo • Won’t explain much during demo… 5
20. Live demo • Won’t explain much during demo… • But the next 50 slides afterwards will! 5
21. Live demo • Won’t explain much during demo… • But the next 50 slides afterwards will! • No boring domain as example please… 5
22. Live demo • Won’t explain much during demo… • But the next 50 slides afterwards will! • No boring domain as example please… • Let’s play cards! 5
23. Live demo • Won’t explain much during demo… • But the next 50 slides afterwards will! • No boring domain as example please… • Let’s play cards! • My first feature using “http://deckofcardsapi.com” 5
24. Live demo • Won’t explain much during demo… • But the next 50 slides afterwards will! • No boring domain as example please… • Let’s play cards! • My first feature using “http://deckofcardsapi.com” • Source for later reference partly at https://github.com/agourlay/ cornichon/blob/master/src/it/scala/ com.github.agourlay.cornichon.examples/DeckOfCard.scala 5
25. What have we learned? 6
26. What have we learned? • debugging instruction 6
27. What have we learned? • debugging instruction • asserting response parts 6
28. What have we learned? • debugging instruction • asserting response parts • dealing with unstable fields 6
29. What have we learned? • debugging instruction • asserting response parts • dealing with unstable fields • reusing and abstracting over steps 6
30. What have we learned? • debugging instruction • asserting response parts • dealing with unstable fields • reusing and abstracting over steps • SBT is your friend 6
31. What have we learned? • debugging instruction • asserting response parts • dealing with unstable fields • reusing and abstracting over steps • SBT is your friend • baseUrl 6
32. What have we learned? • debugging instruction • asserting response parts • dealing with unstable fields • reusing and abstracting over steps • SBT is your friend • baseUrl • using the session 6
33. Terminology (1) 7
34. Terminology (1) • feature container for scenarios 7
35. Terminology (1) • feature container for scenarios • scenario container for steps 7
36. Terminology (1) • feature container for scenarios • scenario container for steps • step abstract executable instruction 7
37. Terminology (1) • feature container for scenarios • scenario container for steps • step abstract executable instruction • effect step session => Future[Session] 7
38. Terminology (1) • feature container for scenarios • scenario container for steps • step abstract executable instruction • effect step session => Future[Session] case class EffectStep(title: String, effect: Session ⇒ Future[Session]) extends Step 7
39. Terminology (2) 8
40. Terminology (2) • assert step session => Assertion 8
41. Terminology (2) • assert step session => Assertion • assertion runs a predicate 8
42. Terminology (2) • assert step session => Assertion • assertion runs a predicate case class AssertStep(title: String, action: Session ⇒ Assertion) extends Step trait Assertion {
 def validated: ValidatedNel[CornichonError, Done]
 } 8
43. Terminology (3) 9
44. Terminology (3) • session state in Map[String, Vector[String]] 9
45. Terminology (3) • session state in Map[String, Vector[String]] • placeholders key referencing value in the session 9
46. Terminology (3) • session state in Map[String, Vector[String]] • placeholders key referencing value in the session When I get("/deck/<deck-id>/draw/") 9
47. Execution model 10
48. Execution model • features are executed sequentially 10
49. Execution model • features are executed sequentially • scenarios within are executed in parallel 10
50. Execution model • features are executed sequentially • scenarios within are executed in parallel • can be changed via configuration 10
51. Execution model • features are executed sequentially • scenarios within are executed in parallel • can be changed via configuration • depends also on the tested system 10
52. Basic features 11
53. HTTP effect DSL 12
54. HTTP effect DSL • GET, DELETE, HEAD, OPTIONS, POST, PUT and PATCH 12
55. HTTP effect DSL • GET, DELETE, HEAD, OPTIONS, POST, PUT and PATCH • Use a builder shape with body, params, headers for consistency 12
56. HTTP effect DSL • GET, DELETE, HEAD, OPTIONS, POST, PUT and PATCH • Use a builder shape with body, params, headers for consistency • Params in URL are supported for convenience 12
57. HTTP effect DSL • GET, DELETE, HEAD, OPTIONS, POST, PUT and PATCH • Use a builder shape with body, params, headers for consistency • Params in URL are supported for convenience • Body supported on every HTTP verb 12
58. HTTP effect DSL post("/superheroes").withBody(
 """
 {
 "name": "Scalaman" } """ ) get("/series").withParams(
 "titles" -> "Game of Thrones",
 "season" -> "1"
 ) 13
59. HTTP withBody type 14
60. HTTP withBody type • Built-in support for String 14
61. HTTP withBody type • Built-in support for String • Body type can be parametrised via typeclasses
 
 case class HttpRequest[A: Show: Resolvable: Encoder](body: Option[A],…) 14
62. HTTP withBody type • Built-in support for String • Body type can be parametrised via typeclasses
 
 case class HttpRequest[A: Show: Resolvable: Encoder](body: Option[A],…) • Cats.Show / Circe.Encoder / Cornichon.Resolvable 14
63. HTTP assert DSL 15
64. HTTP assert DSL status.is(200) status.isSuccess status.isClientError status.isServerError status.isRedirect 15
65. HTTP assert DSL status.is(200) status.isSuccess status.isClientError status.isServerError status.isRedirect headers.name("Server").isPresent headers.contain("Server" → "akka-http/10.0.1") headers.name("server").isAbsent 15
66. JSON assert DSL (1) 16
67. JSON assert DSL (1) • Body is assumed to be JSON (see limitations) 16
68. JSON assert DSL (1) • Body is assumed to be JSON (see limitations) • JSON Path 16
69. JSON assert DSL (1) • Body is assumed to be JSON (see limitations) • JSON Path • Ignoring fields 16
70. JSON assert DSL (1) • Body is assumed to be JSON (see limitations) • JSON Path • Ignoring fields • Whitelisting 16
71. JSON assert DSL (1) • Body is assumed to be JSON (see limitations) • JSON Path • Ignoring fields • Whitelisting • JSON Array 16
72. JSON DSL in action 17
73. When I get("/superheroes/Batman")
 
 And assert body.is(
 """
 {
 "name": "Batman",
 "realName": "Bruce Wayne",
 "city": "Gotham city",
 "hasSuperpowers": false,
 "publisher":{
 "name":"DC",
 "foundationYear":1934,
 "location":"Burbank, California"
 }
 }
 """
 ) 18
74. Then assert body.path("hasSuperpowers").is(false) Then assert body.path("city").isPresent
 
 Then assert body.path("city").is("Gotham city")
 
 Then assert body.path("city").containsString("Gotham")
 
 Then assert body.path("city").matchesRegex(“.*city”.r)
 
 Then assert body.path("country").isAbsent
 19
75. 
 Then assert body.path("publisher.name").is("DC")
 
 Then assert body.path("publisher.foundationYear").is(1934) Then assert body.path("publisher").ignoring("location").is(
 """
 {
 "name":"DC",
 "foundationYear":1934
 }
 """
 ) 20
76. And assert body.ignoring("publisher.name", "publisher.location").is(
 """
 {
 "name": "Batman",
 "realName": "Bruce Wayne",
 "city": "Gotham city",
 "hasSuperpowers": false,
 "publisher":{
 "foundationYear":1934
 }
 }
 """
 )
 
 And assert body.whitelisting.is(
 """
 {
 "name": "Batman",
 "realName": "Bruce Wayne"
 }
 """
 ) 21
77. Wrapper steps 22
78. Wrapper steps • Control the execution of a series of steps 22
79. Wrapper steps • Control the execution of a series of steps • Can be arbitrarily nested 22
80. Wrapper steps • Control the execution of a series of steps • Can be arbitrarily nested trait WrapperStep extends Step {
 def nested: List[Step]
 }
 22
82. Repeat(3) {
 When I get("http://superhero.io/batman")
 Then assert status.is(200)
 } 23
83. Repeat(3) {
 When I get("http://superhero.io/batman")
 Then assert status.is(200)
 } RepeatDuring(300.millis) {
 When I get("http://superhero.io/batman")
 Then assert status.is(200)
 } 23
84. Repeat(3) {
 When I get("http://superhero.io/batman")
 Then assert status.is(200)
 } RepeatDuring(300.millis) {
 When I get("http://superhero.io/batman")
 Then assert status.is(200)
 } RetryMax(3) {
 When I get("http://superhero.io/batman")
 Then assert status.is(200)
 } 23
86. Eventually(maxDuration = 15.seconds, interval = 200.millis) {
 When I get(“http://superhero.io/random”) Then assert body.path("hasSuperpowers").is(true)
 } 24
87. Eventually(maxDuration = 15.seconds, interval = 200.millis) {
 When I get(“http://superhero.io/random”) Then assert body.path("hasSuperpowers").is(true)
 } Concurrently(factor = 3, maxTime = 10 seconds) {
 When I get(“http://superhero.io/batman")
 Then assert status.is(200)
 } 24
88. Eventually(maxDuration = 15.seconds, interval = 200.millis) {
 When I get(“http://superhero.io/random”) Then assert body.path("hasSuperpowers").is(true)
 } Concurrently(factor = 3, maxTime = 10 seconds) {
 When I get(“http://superhero.io/batman")
 Then assert status.is(200)
 } Within(maxDuration = 10 seconds) {
 When I get("http://superhero.io/batman")
 Then assert status.is(200)
 } 24
90. WithHeaders(("Authorization", "Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==")){
 When I get("http://superhero.io/secured") 
 Then assert status.is(200)
 } 25
91. WithHeaders(("Authorization", "Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==")){
 When I get("http://superhero.io/secured") 
 Then assert status.is(200)
 } WithBasicAuth("admin", "root"){
 When I get("http://superhero.io/secured") 
 Then assert status.is(200)
 } 25
92. Placeholders 26
93. Placeholders • syntax to extract values from Session 26
94. Placeholders • syntax to extract values from Session • HTTP effect request body, parameters, URL, headers 26
95. Placeholders • syntax to extract values from Session • HTTP effect request body, parameters, URL, headers • JSON path, assertions 26
96. Placeholders • syntax to extract values from Session • HTTP effect request body, parameters, URL, headers • JSON path, assertions • actually built-in…almost everywhere 26
97. Placeholders • syntax to extract values from Session • HTTP effect request body, parameters, URL, headers • JSON path, assertions • actually built-in…almost everywhere • In your custom steps via the Resolver API manually 26
98. Given I save("favorite-superhero" → "Batman")
 
 Then assert session_value("favorite-superhero").is("Batman")
 
 When I get("/superheroes/<favorite-superhero>")
 
 Then assert body.is(
 """
 {
 "name": "<favorite-superhero>",
 "realName": "Bruce Wayne",
 "city": "Gotham city",
 "publisher": "DC"
 }
 """
 ) 27
99. Built-in placeholders 28
100. • <random-uuid> for a random UUID Built-in placeholders 28
101. • <random-uuid> for a random UUID • <random-positive-integer> for a random Integer Built-in placeholders 28
102. • <random-uuid> for a random UUID • <random-positive-integer> for a random Integer • <random-string> for a random String of length 5 Built-in placeholders 28
103. • <random-uuid> for a random UUID • <random-positive-integer> for a random Integer • <random-string> for a random String of length 5 • <random-alphanum-string> for a random alphanumeric Built-in placeholders 28
104. • <random-uuid> for a random UUID • <random-positive-integer> for a random Integer • <random-string> for a random String of length 5 • <random-alphanum-string> for a random alphanumeric • <random-boolean> for a random Boolean string Built-in placeholders 28
105. • <random-uuid> for a random UUID • <random-positive-integer> for a random Integer • <random-string> for a random String of length 5 • <random-alphanum-string> for a random alphanumeric • <random-boolean> for a random Boolean string • <timestamp> for the current timestamp Built-in placeholders 28
107. post("/superheroes").withBody(
 """
 { "id": "<random-uuid>", 
 "name": "<random-string>", "age": <random-positive-integer>, "hasSuperpowers": <random-boolean> } """ ) 29
108. post("/superheroes").withBody(
 """
 { "id": "<random-uuid>", 
 "name": "<random-string>", "age": <random-positive-integer>, "hasSuperpowers": <random-boolean> } """ ) Eventually(maxDuration = 500.hours, interval = 50.milliseconds) {
 When I get("/superheroes/<random-string>") Then assert status.is(200)
 } 29
109. Data table 30
110. Data table • used to express JSON arrays 30
111. Data table • used to express JSON arrays • supports placeholders 30
112. Data table • used to express JSON arrays • supports placeholders When I get("/superheroes") Then assert body.asArray.ignoringEach("publisher").is(
 """
 | name | realName | city | hasSuperpowers |
 | "Batman" | "Bruce Wayne" | "Gotham city" | false |
 | "Superman" | "Clark Kent" | "Metropolis" | true |
 | "Spiderman" | "Peter Parker" | "New York" | true |
 """
 ) 30
113. Advanced features 31
114. DSL composition 32
115. DSL composition • Avoid copy paste 32
116. DSL composition • Avoid copy paste • Reuse sub part of scenarios 32
117. DSL composition • Avoid copy paste • Reuse sub part of scenarios • Increases composition 32
118. DSL composition • Avoid copy paste • Reuse sub part of scenarios • Increases composition • Any wrapper step 32
119. DSL composition • Avoid copy paste • Reuse sub part of scenarios • Increases composition • Any wrapper step • “Attach" for regular step 32
121. def superhero_exists(name: String) =
 Attach {
 When I get(s"/superheroes/$name")
 Then assert status.is(200)
 } 33
122. def superhero_exists(name: String) =
 Attach {
 When I get(s"/superheroes/$name")
 Then assert status.is(200)
 } Then assert superhero_exists("Batman") 33
123. def superhero_exists(name: String) =
 Attach {
 When I get(s"/superheroes/$name")
 Then assert status.is(200)
 } def random_superheroes_until(name: String) =
 Eventually(maxDuration = 3 seconds, interval = 10 millis) {
 When I get("/superheroes/random")
 Then assert body.path("name").is(name)
 Then I print_step("bingo!")
 } Then assert superhero_exists("Batman") 33
124. def superhero_exists(name: String) =
 Attach {
 When I get(s"/superheroes/$name")
 Then assert status.is(200)
 } def random_superheroes_until(name: String) =
 Eventually(maxDuration = 3 seconds, interval = 10 millis) {
 When I get("/superheroes/random")
 Then assert body.path("name").is(name)
 Then I print_step("bingo!")
 } Then assert random_superheroes_until("Batman") Then assert superhero_exists("Batman") 33
125. HttpService 34
126. HttpService • Abstracts HTTP calls to endpoint behind Effect Step 34
127. HttpService • Abstracts HTTP calls to endpoint behind Effect Step • Increases step reusability 34
128. HttpService • Abstracts HTTP calls to endpoint behind Effect Step • Increases step reusability • Useful to work against different endpoints 34
129. HttpService • Abstracts HTTP calls to endpoint behind Effect Step • Increases step reusability • Useful to work against different endpoints • Offers helpers to work on response 34
131. def create_publisher(body: String) = EffectStep(
 title = s"create the publisher\n $body",
 effect = http.requestEffect(
 request = HttpRequest.post("/publishers").withBody(body),
 extractor = RootExtractor("publisher"),
 expectedStatus = Some(201)
 )
 ) 35
132. def create_publisher(body: String) = EffectStep(
 title = s"create the publisher\n $body",
 effect = http.requestEffect(
 request = HttpRequest.post("/publishers").withBody(body),
 extractor = RootExtractor("publisher"),
 expectedStatus = Some(201)
 )
 ) Given I create_publisher {
 """
 "name":"DC",
 "foundationYear":1934,
 "location":"Burbank, California"
 """
 } 35
133. And more… 36
134. And more… • Hooks 36
135. And more… • Hooks • GraphQL 36
136. And more… • Hooks • GraphQL • Web hook testing via HTTP mocking 36
137. And more… • Hooks • GraphQL • Web hook testing via HTTP mocking • Server-Sent-Event 36
138. And more… • Hooks • GraphQL • Web hook testing via HTTP mocking • Server-Sent-Event • Custom session extractors 36
139. And more… • Hooks • GraphQL • Web hook testing via HTTP mocking • Server-Sent-Event • Custom session extractors • Automatic headers setting 36
140. And more… • Hooks • GraphQL • Web hook testing via HTTP mocking • Server-Sent-Event • Custom session extractors • Automatic headers setting • Data table driven step 36
141. And more… • Hooks • GraphQL • Web hook testing via HTTP mocking • Server-Sent-Event • Custom session extractors • Automatic headers setting • Data table driven step • … 36
142. Under the hood 37
143. Main dependencies 38
144. Main dependencies • Akka-http for the client 38
145. Main dependencies • Akka-http for the client • Circe for the JSON handling 38
146. Main dependencies • Akka-http for the client • Circe for the JSON handling • Cats for the FP goodness 38
147. Main dependencies • Akka-http for the client • Circe for the JSON handling • Cats for the FP goodness • Parboiled2 for parsing (placeholder, JSON path, DT) 38
148. Main dependencies • Akka-http for the client • Circe for the JSON handling • Cats for the FP goodness • Parboiled2 for parsing (placeholder, JSON path, DT) • Scalatest for the SBT integration and test runner 38
149. DSL internals (1) 39
150. DSL internals (1) • Dynamic trait 39
151. DSL internals (1) • Dynamic trait • Infix notation 39
152. DSL internals (1) • Dynamic trait • Infix notation 39 sealed trait Starters extends Dynamic {
 def name: String
 def applyDynamic(mandatoryWord: String)(step: Step) = step.setTitle(s"$name $mandatoryWord ${step.title}")
 }
 
 case object When extends Starters { val name = "When" }
153. DSL internals (2) 40
154. DSL internals (2) • How do HTTP requests are turned into steps? 40
155. DSL internals (2) • How do HTTP requests are turned into steps? implicit def httpRequestToStep[A: Show: Resolvable: Encoder] (request: HttpRequest[A]): EffectStep =
 EffectStep(
 title = request.compactDescription,
 effect = http.requestEffect(request)
 ) 40
156. DSL internals (3) 41
157. DSL internals (3) • How is the Feature object built? 41
158. DSL internals (3) • How is the Feature object built? • Macro collects elements of a given type 41
159. DSL internals (3) • How is the Feature object built? • Macro collects elements of a given type • Contributed by @OlegIlyenko 41
160. DSL internals (3) • How is the Feature object built? • Macro collects elements of a given type • Contributed by @OlegIlyenko case class BodyElementCollector[Body, Result](fn: List[Body] ⇒ Result) {
 def apply(body: ⇒ Body): Result = macro Macro.collectImpl
 } 41
162. def Feature(name: String, ignored: Boolean = false) =
 BodyElementCollector[ScenarioDef, FeatureDef]{scenarios ⇒ FeatureDef(name, scenarios, ignored) } 42
163. def Feature(name: String, ignored: Boolean = false) =
 BodyElementCollector[ScenarioDef, FeatureDef]{scenarios ⇒ FeatureDef(name, scenarios, ignored) } def Scenario(name: String, ignored: Boolean = false) =
 BodyElementCollector[Step, ScenarioDef]{steps ⇒ ScenarioDef(name, steps, ignored) } 42
164. def Feature(name: String, ignored: Boolean = false) =
 BodyElementCollector[ScenarioDef, FeatureDef]{scenarios ⇒ FeatureDef(name, scenarios, ignored) } def Scenario(name: String, ignored: Boolean = false) =
 BodyElementCollector[Step, ScenarioDef]{steps ⇒ ScenarioDef(name, steps, ignored) } def Concurrently(factor: Int, maxTime: FiniteDuration) =
 BodyElementCollector[Step, Step] { steps ⇒
 ConcurrentlyStep(steps, factor, maxTime)
 } 42
165. Conceptual execution flow 43
166. Conceptual execution flow • Macro collects steps to build the scenario 43
167. Conceptual execution flow • Macro collects steps to build the scenario • Macro collects scenarios to build the feature 43
168. Conceptual execution flow • Macro collects steps to build the scenario • Macro collects scenarios to build the feature • Feature is turned into a Scalatest AsyncWordSpec 43
169. Conceptual execution flow • Macro collects steps to build the scenario • Macro collects scenarios to build the feature • Feature is turned into a Scalatest AsyncWordSpec • Each scenario becomes a test 43
170. Conceptual execution flow • Macro collects steps to build the scenario • Macro collects scenarios to build the feature • Feature is turned into a Scalatest AsyncWordSpec • Each scenario becomes a test • Scalatest invokes the engine that runs the scenario 43
171. Conceptual execution flow • Macro collects steps to build the scenario • Macro collects scenarios to build the feature • Feature is turned into a Scalatest AsyncWordSpec • Each scenario becomes a test • Scalatest invokes the engine that runs the scenario • Result of the execution is fed into a Scalatest assert() 43
172. Usage @commercetools 44
173. Internal usage growth 45
174. Internal usage growth Cornichon 45
175. Internal usage growth Cornichon 45
176. Internal usage growth Cucumber Cornichon 45
177. Internal usage growth Cucumber Cornichon 45
178. Teamcity integration 46
179. Teamcity integration • Runs against different environments 46
180. Teamcity integration • Runs against different environments • Injects configuration via typesafe-config arguments 46
181. Teamcity integration • Runs against different environments • Injects configuration via typesafe-config arguments • sbt test (testQuick to fight flaky systems) 46
182. Teamcity integration • Runs against different environments • Injects configuration via typesafe-config arguments • sbt test (testQuick to fight flaky systems) • Or build uber-jar test artifact to avoid recompilation 46
183. Teamcity integration 47
184. Features organisation 48
185. Features organisation • Sub-project - commit tests & features in a single PR 48
186. Features organisation • Sub-project - commit tests & features in a single PR • Abstract CommercetoolsFeature with the usual config 48
187. Features organisation • Sub-project - commit tests & features in a single PR • Abstract CommercetoolsFeature with the usual config • One package per entity/resource 48
188. Features organisation • Sub-project - commit tests & features in a single PR • Abstract CommercetoolsFeature with the usual config • One package per entity/resource • Custom steps in traits 48
189. OSS CTP archetype • https://github.com/agourlay/ctp-query-template 49
190. Usage outside of commercetools 50
191. Usage outside of commercetools • Used by three others devs (Gitter discussions) 50
192. Usage outside of commercetools • Used by three others devs (Gitter discussions) • Scale unknown, might be toy projects 50
193. Usage outside of commercetools • Used by three others devs (Gitter discussions) • Scale unknown, might be toy projects • Maybe more according to the maven DL stats 50
194. Usage outside of commercetools • Used by three others devs (Gitter discussions) • Scale unknown, might be toy projects • Maybe more according to the maven DL stats • ¯\_(ツ)_/¯ 50
195. Limitations (1) 51
196. Limitations (1) • JSON only (for now) 51
197. Limitations (1) • JSON only (for now) • Moving away from the well-known Gherkin syntax 51
198. Limitations (1) • JSON only (for now) • Moving away from the well-known Gherkin syntax • Important “classpath” (acceptance testing) 51
199. Limitations (1) • JSON only (for now) • Moving away from the well-known Gherkin syntax • Important “classpath” (acceptance testing) • No beforeAllFeatures and afterAllFeatures 51
200. Limitations (1) • JSON only (for now) • Moving away from the well-known Gherkin syntax • Important “classpath” (acceptance testing) • No beforeAllFeatures and afterAllFeatures • Obviously designed to fit our use case in first place 51
201. Limitations (2) 52
202. Limitations (2) • Managing authentication headers input can be tricky 52
203. Limitations (2) • Managing authentication headers input can be tricky • Full documentation on a Readme file 52
204. Limitations (2) • Managing authentication headers input can be tricky • Full documentation on a Readme file • Rely partly on exception internally (0.11 will hopefully fix it) 52
205. Limitations (2) • Managing authentication headers input can be tricky • Full documentation on a Readme file • Rely partly on exception internally (0.11 will hopefully fix it) • Truck factor of 1 52
206. Limitations (2) • Managing authentication headers input can be tricky • Full documentation on a Readme file • Rely partly on exception internally (0.11 will hopefully fix it) • Truck factor of 1 • Makes acceptance tests so fun that you less write UT ;) 52
207. Road to 1.0 53
208. Road to 1.0 • Hopefully in 2017! 53
209. Road to 1.0 • Hopefully in 2017! • Minimise breaking changes in the DSL 53
210. Road to 1.0 • Hopefully in 2017! • Minimise breaking changes in the DSL • Infrastructure - change underlying test runner 53
211. Road to 1.0 • Hopefully in 2017! • Minimise breaking changes in the DSL • Infrastructure - change underlying test runner • Features - introduce matchers 53
212. Road to 1.0 • Hopefully in 2017! • Minimise breaking changes in the DSL • Infrastructure - change underlying test runner • Features - introduce matchers • Docs - compiled example on a website 53
213. Closing notes 54
214. Closing notes • You learned what the tool can do and its limitations 54
215. Closing notes • You learned what the tool can do and its limitations • The built-in DSL takes you a long way 54
216. Closing notes • You learned what the tool can do and its limitations • The built-in DSL takes you a long way • Scala is great for building DSLs 54
217. Closing notes • You learned what the tool can do and its limitations • The built-in DSL takes you a long way • Scala is great for building DSLs • Focus on solving problems you actually have 54
218. Questions? 55