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

Timestamp:

05/23/18 13:18:21 (6 years ago)

Author:

Vijay Kumar Banerjee

Comment:

--

GSoC/2018/coverage_analysis_toolset

@@ -13 +13 @@
 '''Blockers:''' Generating .gcno notes files by changing gcc flags
 
+''' Development Blog :''' https://thelunatic.github.io/rtems_gsoc18
 = Introduction = 
 This 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 . 
@@ -25 +26 @@
 * Reports (HTML and text currently, add XML) 
 
-== Running covoar for coverage analysis ==
+== Running covoar To generate coverage reports ==
 
 To run covoar we need to run covoar from the RTEMS-KERNEL BUILD directory.
@@ -57 +58 @@
 
 }}}
+
+== Running RTEMS-TESTER for Coverage analysis ==
+
+RTEMS-TESTER when run with `--coverage` option, generates an html coverage analysis report (report.html)
+
+{{{
+$HOME/development/rtems/test/rtems-tools/tester/rtems-test \
+--rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log \
+--rtems-bsp=leon3-qemu-cov --coverage --no-clean \
+/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe
+}}}
+
+[[span(style=color: #FF0000, NOTE : )]] The `--no-clean` option tells the script not to delete the .cov trace files generated while running the coverage.
+These Trace files can be used for running covoar directly.
+
+Please visit [https://thelunatic.github.io/rtems_gsoc18/blog/coverage-report/ my development blog] to see examples of coverage report
+
 == Resources ==