Unit Test Results

       1 files         2 suites   1m 38s ⏱️
1 029 tests 1 025 ✔️ 4 💤 0 ❌
1 032 runs  1 024 ✔️ 8 💤 0 ❌

Results for commit c762920.

♻️ This comment has been updated with latest results.

Codecov Report

Merging #1183 (c762920) into develop (ab1acfa) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop    #1183      +/-   ##
===========================================
- Coverage    94.86%   94.80%   -0.07%     
===========================================
  Files          104      104              
  Lines         4853     4886      +33     
  Branches        21       23       +2     
===========================================
+ Hits          4604     4632      +28     
- Misses         241      245       +4     
- Partials         8        9       +1     

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 08bb27b...c762920. Read the comment docs.

We need to also update other reporters except ut_documentation_reporter Particularly:
(...)
For the ut_realtime_reporter - It would be good to check with @PhilippSalvisberg

I don't think this information is required for the realtime reporter. If you decide to add it, it will not have any effect. The SQLDev extension and the PL/SQL Developer plugin will ignore this additional information. If you think the behaviour in the IDE should change then I suggest to open dedicated issues for SQLDev and PL/SQL Developer.

@lwasylow @simasch
Not sure what are your thoughts on having disabled reason visible in SQL/PLSQL Developer IDE.
I think it would be a good to have a complete feature and similar behaviour across all use-cases & IDEs.

@lwasylow @simasch Not sure what are your thoughts on having disabled reason visible in SQL/PLSQL Developer IDE. I think it would be a good to have a complete feature and similar behaviour across all use-cases & IDEs.

So personally I think if we want to have that feature enabled it makes sense to be consistent. I think it's useful piece of information.
However lets hold on with making that call to see if other reporters support the reason of disabling.
I don't think it should hold up release of that feature as we can stage it given a dependency between objects and time needed for @PhilippSalvisberg @simasch to give us specs ( and I mean their personal time :) ) but would ultimate aim for that to be included?

@lwasylow @simasch Not sure what are your thoughts on having disabled reason visible in SQL/PLSQL Developer IDE. I think it would be a good to have a complete feature and similar behaviour across all use-cases & IDEs.

So personally I think if we want to have that feature enabled it makes sense to be consistent. I think it's useful piece of information. However lets hold on with making that call to see if other reporters support the reason of disabling. I don't think it should hold up release of that feature as we can stage it given a dependency between objects and time needed for @PhilippSalvisberg @simasch to give us specs ( and I mean their personal time :) ) but would ultimate aim for that to be included?

As mentioned before, you can include it if you want. The SQLDev extension and the PL/SQL Dev plugin will work without any change since they just pick the information from the XML events they need. I suggest to open dedicated issues for the IDEs. I think the commercial tools TOAD and DataGrip do not use the realtime reporter. However, if the reason for a disabled test should be displayed in the test runner they need to change something as well.

Please see snippet from junit reporter.

Here are results for ut_tfs_junit_reporter

as per documentation

If created a feature request for the PL/SQL Developer plugin utPLSQL/utPLSQL-PLSQL-Developer#25

Here results for ut_teamcity_reporter

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.7% Duplication