Coverage report looks wrong for triggers

[danbroun]

If I have a look at a coverage report of a package every green/red and gray line is understandable. A coverage report for a trigger looks extremely random.

Can anyone confirm this behavior?

[jgebal]

A steps to reproduce or a working example of bad behavior would help

[danbroun]

Just create for example an insert trigger and then write a test which inserts data into the example table. If you have a look at the produced coverage report the marking which line were run looks really random.
If you want I can try to attach a example report. Hope I can make it this week.

[javornikolov]

@danbroun, may you also check PLSQL_OPTIMIZE_LEVEL option which has been used to compile the trigger? For better coverage output it's best to use 1.