Updates:
Summary: Log: Keep non-critical failed tests closed by default and
differentiate them from critical failed tests
Comment #1 on issue 1031 by pekka.klarck: Log: Keep non-critical failed
tests closed by default and differentiate them from critical failed tests
http://code.google.com/p/robotframework/issues/detail?id=1031
This is a good idea.
Just keeping the non-critical failed tests closed has a problem, though, as
there is no way to tell from a closed test is it critical or not. If people
aren't aware that non-critical ones are initially closed, then they will
open them to check that out. Thus this enhancement may actually have a
negative effect on usability.
To overcome the above problem, we need to make it easy to see is a closed
test critical or not. We probably need to add word `critical` there in some
format and could also consider different shades of red for critical and
non-critical failures.
Notice that keeping non-critical tests closed is implemented already for RF
2.7 alpha 1. Differentiating critical and non-critical closed tests is left
for alpha2 or beta1, whichever comes next.
