Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 14 and Version 15 of GSoC/2017/coveragetools


Ignore:
Timestamp:
07/28/17 13:37:08 (7 years ago)
Author:
Cillian O'Donnell
Comment:

Improve Documentation

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2017/coveragetools

    v14 v15  
    5757= Coverage Analysis in RTEMS Tester =
    5858== Symbol Set Configurtion ==
    59 The tests run in rtems-test will be used to check what percentage of the symbols they cover and the symbols to be analysed are in the symbol set config file which can be found here
     59The tests run in rtems-test will have there trace data logged in a file called <test_name>.exe.cov. This will be used to check what percentage of the symbols they cover and the symbols to be analysed are in the symbol set config file which can be found here
    6060{{{
    6161From top directory of rtems-tools
     
    6969The format of the config file is
    7070
     71{{{
    7172 symbolset:
    7273 name = NAME_OF_SET
     
    8081 name = NAME_OF_ANOTHER_SET
    8182 lib = ...
     83}}}
    8284
    83851. Each set is defined with the keyword 'symbolset:'
     
    9496
    9597== Supported BSPS ==
    96 Leon 3: Use 'rtems-bsp=leon3-qemu' with rtems-test cmd.
     98Leon 3: Use '--rtems-bsp=leon3-qemu' with rtems-test cmd.
    9799
    98100== Performing Coverage Analysis with rtems-test command ==
     
    120122}}}
    121123
    122 After the testsuite is run, covoar then performs multiple runs for all tests on each symbol set in symbol_set.cfg. Covoar sections the objdump into seperate functions and uses the trace data from Couverture-Qemu that records trace blocks as 'executed' and 'not executed' to mark branches as 'taken' and 'not taken'. Covoar then creates coverage maps from the results. The maps are then merged together and a report is generated. The report is a html file that can be found in the directory created above coverage_test called report.html.
     124After the testsuite is run, covoar then performs multiple runs analysing the trace data collected by Couverture-QEMU for all tests on each symbol set in symbol_set.cfg. Covoar sections the objdump into seperate functions and uses the trace data from Couverture-Qemu that records trace blocks as 'executed' and 'not executed' to mark branches as 'taken' and 'not taken'. Covoar then creates coverage maps from the results. The maps are then merged together and a report is generated. The report is a html file that can be found in the directory created above coverage_test called report.html.
    123125
    124126{{{