Spot on! Comments like these are the reason I love dev.to
Thanks a tonne Bertil. That does clarify a lot.
Don't specify user interface details in the scenarios, because when the user interface changes, you would have to adapt your scenarios
I get the feeling this will be golden advice in the near future. This brings the question;do you use Gherkin to model the frontend or backend or the entire system? In this case, I mean with the scenario breakdowns. Would that be e2e or just backend or frontend? What are your thoughts on how they should be structured from a dev breakdown perspective? 😅 that was a lot of '?'s
Spot on! Comments like these are the reason I love dev.to
Thanks a tonne Bertil. That does clarify a lot.
I get the feeling this will be golden advice in the near future. This brings the question;do you use Gherkin to model the frontend or backend or the entire system? In this case, I mean with the scenario breakdowns. Would that be e2e or just backend or frontend? What are your thoughts on how they should be structured from a dev breakdown perspective? 😅 that was a lot of '?'s
Neither frontend, nor backend. Whole system from an external user's perspective.
Got it. Thanks a tonne!