I’m facing the problem of writing of the web application. Frontend of the application is mainly a form, where a user must pass through from the very first page to the last one. It’s trivial to automate the flow, but the problem is how to do it best. As far as I know, test cases (scenarios) should run independently of each other, but in this case, it’s not possible because a previous step is always required to go forward. Also, according to best practices of , ’s feature should depend… one feature but the definition of e2e tests is testing across various features.

So, the questions is: how the Cucumber and its best practices with e2e tests? Can you propose a file structure, example scenarios or step definitions?

edit: the idea is to execute the e2e tests as a smoke test while building a new version.

Source link https://sqa.stackexchange.com/questions/34508/how-to-deal-cucumber-framework-and-end-2-end-tests


Please enter your comment!
Please enter your name here