Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Our Cucumber suite keeps everything on the World: the id of the record the last step created, the current user, a couple of counters, and a response object that three later steps read.
Feature files copy across fine and the tags lint clean. The step definitions are where I am stuck, because half of them are this.something = ... and there is no this to put it on.
Accepted answer
There is no World, and most of what you were keeping on it has a home already.
Values captured from a response become scenario variables:
When I save the response JSON path "id" as "orderId"
And I send a GET request to "/orders/{{orderId}}"Every {string} argument and doc string is rendered before the step runs, and the variables resolve in order: values saved in this scenario, then the current dataset row, then vars from the environment file. So the counters and the id stop being state you manage and become values you name.
The current user is not yours to track either — @user:standard or the leased-user step sets username, password, userId and role as variables, and applies the storage state.
The response object needs nothing: the assertion steps already read the last response.
What is genuinely left — a piece of object state two steps on the same page share — lives on the page object instance. pages.get(Class) caches one instance per class per scenario, so a field you set in a When is there in the Then, and it is thrown away when the scenario ends. Read variables from inside the class with this.vars and this.render().
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.