Failed Test Case Statistics based on Failure Reason

[gitissuepost]

Is your feature request related to a problem? Please describe.
With a large test-suite with a high number of failures, currently it is difficult to prioritize the failed group test cases to increase the execution rate.
E.g. With a report of 300 test failures if 100 gets failed because an element is not accessible due to change is locator, currently there is no option to figure out how many failures fall under what exception reason.

Describe the solution you'd like
Just like we have a All Steps view, if we can get a view for failure reasons, The messages we see in red in below screenshot. It will solve the purpose. This will help the automation team to understand how many failures are intermittent/related to env issues and what all needs an attentions. Out of the failed test cases need to be fixed, they can pick the category with high failure and start working on that. It could be a minor fix which will fix majority of the test failures related to scripting.

Describe alternatives you've considered
Currently we are capturing the failures in a json as part of listener and do our analysis on those entries.

[bischoffdev]

I like this idea a lot, this sounds like a good addition for the next release.

[gitissuepost]

@bischoffdev - I don't see any reference of DaggerClucumberCoreGraph class. Should it be part of any other repo? I downloaded to play around but couldn't proceed due to compilation issues

[gdonati78]

@bischoffdev - I don't see any reference of DaggerClucumberCoreGraph class. Should it be part of any other repo?

If I'm not mistaken, that should be a generated class based on src/main/java/com/trivago/cluecumber/engine/dagger/CluecumberCoreGraph.java , that Dagger generates during the building process of cluecumber-engine.
You can build the whole project with make build from root, did you do that?

[gitissuepost]

@gdonati78 - I didn't try that. Thanks for the lead.

[bischoffdev]

If I'm not mistaken, that should be a generated class based on src/main/java/com/trivago/cluecumber/engine/dagger/CluecumberCoreGraph.java , that Dagger generates during the building process of cluecumber-engine.

Exactly, Dagger code needs to be generated.

[gitissuepost]

@bischoffdev - I think long back you mentioned that you have it in your plan to generate a pdf report but not part of this project as this report focuses only on html reporting. Do we have any other project to generate pdf report that I can use?

[bischoffdev]

Hi, no there is no plan to do this.

[gitissuepost]

@bischoffdev - Any plan for a new relase this year? or the next version will be in Q1 2025?

[bischoffdev]

We might have another release this year.