Open simasch opened 2 years ago
Currently the ut_realtime_reporter
is producing following output with disabled flag:
<test>
<disabled>true</disabled>
</test>
If test is not disabled we get the following outcome.
<test>
<disabled>false</disabled>
</test>
To keep backward compatibility we should not change that behaviour and add another flag.
I suggest introduction of <disabled_reason><![CDATA[Disabled reason description]]></disabled_reason>
So the results would be one of:
Disabled without reason
<test>
<disabled>true</disabled>
</test>
Disabled with reason
<test>
<disabled>true</disabled>
<disabled_reason><![CDATA[the reason]]></disabled_reason>
</test>
Enabled
<test>
<disabled>false</disabled>
</test>
@simasch @lwasylow @PhilippSalvisberg
I allowed myself to correct your post @jgebal as the word fale
got me really confused :P
I totally agree that a new flag called disabled_reason
would be best way.
I explained in utPLSQL/utPLSQL#1192 why I would use CamelCase and name the node disabledReason
. IMO the next step is to implement the change outlined there.
Version 1.4.0 of the SQLDev extension can show the disabled reason. Here's a screenshot:
utPLSQL adds a reason to a disabled test: https://github.com/utPLSQL/utPLSQL/issues/610
Add the reason to the result window if the test is disabled.