Comment #3 on issue 423 by pekka.klarck: Easier way to implement
croscutting checks
http://code.google.com/p/robotframework/issues/detail?id=423
Wouldn't this basically mean adding another teardown? Although I understand
the
explained use case I'm afraid it would be somewhat confusing.
Would the functionality described in issue 177 be suitable in this case?
One of the
ideas behind is handling exactly this kind of situations where every/most
tests need
to check some condition after the execution.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
