Is your feature request related to a problem? Please describe.
Currently all steps shows only the status of BDD steps/stef defs. However, if we have test failures in hooks, that detail is not being captured.
In above sample report, the test steps got passed but the test has been marked as failure as there is an issue with hooks. And this details I don't find in All Step view. I do understand, that page has been created to get an overview of a quick healthcheck snaps of the step definitions. However, keeping tab on the hooks will also be helpful.
Moreover, the dashboard says this test is failed but when I open the test report, the dashboard inside test specific report says, it is passed. If I have an issue with hooks and I tag it as failure for my overall report, I should see this test as failed here as well. If we can include any mark or a legend to confirm we have issue with hooks, that will avoid the confusion when the report is being reviewed by business with no visibility on the technicality report.
Currently, if I compare the sample report, the dashboard says there are 9 failures but the all step page says 6 failures. This may vary how we have handled the assertion and exceptions. But in case of sample report, i hope, both count should match and this can be achieved if we will project the hooks related failures in that list as well. Again this will give a quick overview around how many test failed just in hooks with no impact on test/functional flow.
Describe the solution you'd like
We can add a toggle just like the one we have in Test Report to include Hooks into list. So user will have flexibility there and the failure count in dashboard will match the failure count in All step view
Is your feature request related to a problem? Please describe. Currently all steps shows only the status of BDD steps/stef defs. However, if we have test failures in hooks, that detail is not being captured.
In above sample report, the test steps got passed but the test has been marked as failure as there is an issue with hooks. And this details I don't find in All Step view. I do understand, that page has been created to get an overview of a quick healthcheck snaps of the step definitions. However, keeping tab on the hooks will also be helpful.
Moreover, the dashboard says this test is failed but when I open the test report, the dashboard inside test specific report says, it is passed. If I have an issue with hooks and I tag it as failure for my overall report, I should see this test as failed here as well. If we can include any mark or a legend to confirm we have issue with hooks, that will avoid the confusion when the report is being reviewed by business with no visibility on the technicality report.
Currently, if I compare the sample report, the dashboard says there are 9 failures but the all step page says 6 failures. This may vary how we have handled the assertion and exceptions. But in case of sample report, i hope, both count should match and this can be achieved if we will project the hooks related failures in that list as well. Again this will give a quick overview around how many test failed just in hooks with no impact on test/functional flow.
Describe the solution you'd like We can add a toggle just like the one we have in Test Report to include Hooks into list. So user will have flexibility there and the failure count in dashboard will match the failure count in All step view