Description

simasch

opened on Feb 7, 2022

Issue body actions

utPLSQL adds a reason to a disabled test: utPLSQL/utPLSQL#610

Add the reason to the result window if the test is disabled.

Activity

1. simasch

   added

   enhancementNew feature or requestNew feature or request

   on Feb 7, 2022
2. jgebal commented on Feb 7, 2022

   

   jgebal

   on Feb 7, 2022

   Member

   More actions

   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>
3. jgebal commented on Feb 7, 2022

   

   jgebal

   on Feb 7, 2022

   Member

   More actions

   @simasch @lwasylow @PhilippSalvisberg
4. lwasylow commented on Feb 7, 2022

   

   lwasylow

   on Feb 7, 2022

   Member

   More actions

   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.

   Reacted by Jacek Gębal

   Reacted by Philipp Salvisberg

   Reacted by Jacek Gębal
5. PhilippSalvisberg commented on Feb 25, 2022

   

   PhilippSalvisberg

   on Feb 25, 2022

   Member

   More actions

   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.
6. PhilippSalvisberg commented on Feb 27, 2022

   

   PhilippSalvisberg

   on Feb 27, 2022

   Member

   More actions

   Version 1.4.0 of the SQLDev extension can show the disabled reason. Here's a screenshot:

   

Issue actions