The title says it all, I want to filter for only failed tests, and it is not always working, I don’t know why. I need to use this so I can quickly get the failed tests information. expanding everything and scrolling every time is very time consuming. It seems to be doing this with KeywordUtil.markFailed but also with WebUI.verifySomething methods.
To my knowledge, that has been an issue for quite some time (I keep forgetting to report it as a bug). Turning off Info helps… but it would be nice to clear all passes too.
I suspect the issue is, when a subordinate step fails, without its parent showing (marked as a pass) the tree breaks - but that’s just a guess.
I’d vote for the test case log to be shown flat like the Log Viewer.
Hi. I came across this and honestly thought it was a bug. For me the sole purpose of existence of the filter feature is to easily get to the step where it failed (so I can see the screenshot).
When it’s a main test step you can get there rather easily without filtering, but if it’s nested inside some callToTestTestCase or if it’s inside a loop or customKeyWord call… Now I have to extend all to get there.
Also, ideally the “information” tab should immediately show on top both the line were our test case failed AND the line from the actually failed line of code. If possible also clickable, so we can immediately go to the desired script line where the test failed, be that the testcase or a callToTestCase or a custom keyword script…
That would also help a lot.
