‎2013 Jun 10 3:38 PM
Hi there,
before creating an OSS message, I would like to ask around whether somebody knows this problem:
When executing the unit tests of a class within SE80 from within the ABAP Unit Browser, chosing the path "Execute tests and measure coverage", we get a zero coverage which is wrong since the unit tests are executed.
This happens for a large number of classes, but not for all classes: For some classes, the coverage is measured correctly.
We have this problem on a system with SAP_BASIS SAPKB70212, patch level 300. In comparison: On another system with SAPKB70211, patch level 220, we don't observe this phenomenon.
Or is there maybe an info block missing for come classes? How to regenerate these info blocks (not with the "consistency check / repair execution blocks" in SCOV, which works for the complete system and takes days - but only for a single class)?
Any fellow sufferer?
~Rüdiger
‎2013 Jun 14 2:52 PM
Nobody. OK. That's an answer too.
I created OSS message 551858 / 2013.
‎2013 Jun 14 2:52 PM
Nobody. OK. That's an answer too.
I created OSS message 551858 / 2013.
‎2013 Jul 08 7:26 AM
Just to finish this: They gave me the advice to set the parameter "abap/test_generation" to "on". After this, the pair SCOV/Unit Tests works fine for classes that are re-generated. For those that aren't, a run of SGEN for all existing loads should have resolved the issue.
But even after these changes, I had the problem that I had to run the unit tests twice to make the coverage summary show results.