Status: Accepted
Owner: janne.t.harkonen
Labels: Type-Defect Priority-Medium Target-2.5.7
New issue 820 by janne.t.harkonen: Test criticality is serialized
incorrectly if Set Tags and --noncritical are used
http://code.google.com/p/robotframework/issues/detail?id=820
Currently opening test tag is written like
<test critical="yes" name="test"...
If Set Tags -keyword is used inside the test to add a tag specified with
--noncritical (effectively making the test non-critical at runtime) the XML
contains wrong criticality information, since it is written before Set Tags
has been run.
RF itself does not use the value from XML when reports are created, but
for example, the RF-Jenkins plugin uses the XML value and may get the
criticality wrong. RF's own Jython build is failing currently due to this
bug.
One possible fix for this is to serialize the criticality in the status
tag, which is written after all keywords have been run and the correct
criticality information is available at that time.
