Changes between Version 2 and Version 3 of GSoC/2018/coverage_analysis_toolset


Ignore:
Timestamp:
May 23, 2018, 1:18:21 PM (17 months ago)
Author:
Vijay Kumar Banerjee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2018/coverage_analysis_toolset

    v2 v3  
    1313'''Blockers:''' Generating .gcno notes files by changing gcc flags
    1414
     15''' Development Blog :''' https://thelunatic.github.io/rtems_gsoc18
    1516= Introduction =
    1617This project is to improve the tools used to perform the analysis and generate reports. It will convert all the config files to .ini and get the coverage analysis running properly. Then the coverage tools will be integrated with RTEMS Tester .
     
    2526* Reports (HTML and text currently, add XML)
    2627
    27 == Running covoar for coverage analysis ==
     28== Running covoar To generate coverage reports ==
    2829
    2930To run covoar we need to run covoar from the RTEMS-KERNEL BUILD directory.
     
    5758
    5859}}}
     60
     61== Running RTEMS-TESTER for Coverage analysis ==
     62
     63RTEMS-TESTER when run with `--coverage` option, generates an html coverage analysis report (report.html)
     64
     65{{{
     66$HOME/development/rtems/test/rtems-tools/tester/rtems-test \
     67--rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log \
     68--rtems-bsp=leon3-qemu-cov --coverage --no-clean \
     69/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe
     70}}}
     71
     72[[span(style=color: #FF0000, NOTE : )]] The `--no-clean` option tells the script not to delete the .cov trace files generated while running the coverage.
     73These Trace files can be used for running covoar directly.
     74
     75Please visit [https://thelunatic.github.io/rtems_gsoc18/blog/coverage-report/ my development blog] to see examples of coverage report
     76
    5977== Resources ==
    6078