Coverage report looks wrong for triggers #34

Activity

1. jgebal commented on Mar 30, 2016

   

   jgebal

   on Mar 30, 2016

   Contributor

   More actions

   A steps to reproduce or a working example of bad behavior would help
2. danbroun commented on Apr 4, 2016

   

   danbroun

   on Apr 4, 2016

   Author

   More actions

   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.
3. javornikolov commented on Apr 4, 2016

   

   javornikolov

   on Apr 4, 2016

   Collaborator

   More actions

   @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.