Code Coverage - exporting and filtering

afarr

When using Code Coverage, I would like to:

a) filter out the lines have not been executed (i.e. the red lines)

b) export the lines (actually, just the black lines) to a single text file.

Does anyone konw how to do this?

Thanks,
Alastair

ara3n

filter on "No. of hits" <> 0 then copy and paste them to excel.

afarr

Hi Rashed,

Thanks for the quick reply.

I realise now that I can even remove the filter on the Object Type and Object No. and this will show me all the executed code in all the objects. Unfortunately, I can't display the Object Type and Object No. - the only column that shows in "View Columns" is Code. If there is a way of showing those fields that would be great.


Regards,
Alastair

ara3n

design the form and add the fields to the form.

Tomas

ara3n wrote:

design the form and add the fields to the form.

This is useful!

afarr

OK, thanks for that. Here's all the steps (I just sent this out to the other developers I work with because I think it will be quite useful):

1. Design the Code Coverage form (Form 566) and add the fields Object Type and Object ID.
Add some documentation, save and close the form.

2. Go to Tools – Debugger – Code Coverage – Code.

3. Press Ctrl+F7 to view the filters.

4. Remove the filters for Object Type and Object ID (so that you can see code for all the objects together – you can identify which code is for which object thanks to the fields added in step 1 above).

5. Add a filter for No. of Hits, <>0 (this will show only the black lines).

6. If you want you can even copy the lines to Excel.

kriki

[Topic moved from Navision forum to Navision Tips & Tricks forum]

ajhvdb

What you're missing in code coverage is the sequential order in which code is executed.

ara3n

That is what you use client Monitor for.

Also if you use SQL perform tools. It combines Code coverage with client Monitor so you can debug those really bad code and loops.

Alagar

This Really Good Tips =D> =D> =D>

Belias

i've never find the "no. of hits" very reliable, because the "if" statements (and all the code that does not start and end in the same line), are shown as never hit. (edit: this does not depend from the semicolon, as i wrote before) this makes the code coverage less useful, because you won't see the whole line of code, but only the second(or third or fourth) one
edit: [removed a wrong example and replaced with this one]

Code
  WITH VATAmountLine DO  //hits=0
    IF FINDSET THEN//hits=1
      REPEAT//hits=0
        IF (PrevVatAmountLine."VAT Identifier" <> "VAT Identifier") OR//hits=0
           (PrevVatAmountLine."VAT Calculation Type" <> "VAT Calculation Type") OR//hits=0
           (PrevVatAmountLine."Tax Group Code" <> "Tax Group Code") OR//hits=0
           (PrevVatAmountLine."Use Tax" <> "Use Tax")//hits=0
        THEN//hits=1
          PrevVatAmountLine.INIT;//hits=0