I wrote a scenario outline with deliberately compromised steps to reproduce the problem.
We can see that the report indicates fail while there are only compromised and succes iterations of the scenario.
BUT ! (and it's here i think there's something wrong) :
The overall status can change depending of the order of the compromised iterations.
I change the order of the scenario outline and if the last executed iteration is compromised, then the status of the scenario outline is compromised instead of being in error like the first example.
Here are others captures to balance the english explanations of a french developer :)
The problem can be reproduced by checkout a sample project dedicated to the issue :
https://github.com/jpatient/serenity_test
Just checkout the project, run "mvn clean install". Actually, the scenario outline is wrote to reproduce the issue.
wakaleo
commented
7 years ago
To illustrate the title, here some captures :
I wrote a scenario outline with deliberately compromised steps to reproduce the problem. We can see that the report indicates fail while there are only compromised and succes iterations of the scenario.
BUT ! (and it's here i think there's something wrong) : The overall status can change depending of the order of the compromised iterations. I change the order of the scenario outline and if the last executed iteration is compromised, then the status of the scenario outline is compromised instead of being in error like the first example.
Here are others captures to balance the english explanations of a french developer :)
The problem can be reproduced by checkout a sample project dedicated to the issue : https://github.com/jpatient/serenity_test Just checkout the project, run "mvn clean install". Actually, the scenario outline is wrote to reproduce the issue.