Description

mathewbutler

opened on Feb 9, 2023

Issue body actions

• SQL Developer V20.4.1.407 (Build 407.006)
• utPLSQL SQL Developer Plugin V1.3.1.20210104.21005

Trying out the code coverage feature of the utPLSQL SQL Developer plugin and this not producing any output. I suspect a restriction since this is running in an environment with no public internet access.

• Right click on test package in SQL Developer
• Click on the [Code coverage...] option
• Nothing happens

The issues below suggest that the assets for offline usage may be required for this to work

• Use local assets for code coverage report for offline usage #110
• #110 - Use local assets for code coverage report for offline usage #120

Questions:

• Are the assets referred to in Use local assets for code coverage report for offline usage #110 now included in V1.4.1 ?
• If not, I can import these to my environment and follow the instructions in Use local assets for code coverage report for offline usage #110 "assets can be copied into the same temporary directory as the HTML file.". Can you please advise of the location of this temporary directory?
• Is there anything else needed for the report to function offline other than the above?

Thanks in advance - and also thank you for producing this plug-in. The team I work on find this incredible useful.

Activity

1. mathewbutler commented on Feb 17, 2023

   

   mathewbutler

   on Feb 17, 2023

   Author

   More actions

   Revisiting the virtual desktop where I ran these coverage reports - these have been successfully generated. I can only assume they took a long time to be produced.

   I’m closing this.
2. mathewbutler

   closed this as completedon Feb 17, 2023
3. PhilippSalvisberg commented on Feb 17, 2023

   

   PhilippSalvisberg

   on Feb 17, 2023

   Member

   More actions

   @mathewbutler Thanks for checking again. Sometimes it really is the case that problems are solved automatically if you just wait long enough. ;-)

   ASFAIK @jgebal is looking for ways to reduce the overhead of large code coverage reports in the core framework. In the meantime it is a good idea to reduce to run just parts of large suites with code coverage. I know it's not always feasible, but I cannot to more at the moment.
4. PhilippSalvisberg

   self-assigned this

   on Feb 17, 2023
5. PhilippSalvisberg

   added

   question

   on Feb 17, 2023
6. mathewbutler commented on Feb 17, 2023

   

   mathewbutler

   on Feb 17, 2023

   Author

   More actions

   Appreciate the follow up, and the additional suggestions, and happy with your response. I genuinely thought I was seeing a different issue - thanks again.

Issue actions