Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h3>Which tool should I use?</h3> <p>This <a href="http://web.archive.org/web/20090527141110/http://www.kimbly.com/blog/000331.html" rel="noreferrer">article describes</a> another developers frustrations searching for C++ code coverage tools. The author's final solution was <a href="http://www.bullseye.com/" rel="noreferrer">Bullseye Coverage</a>. </p> <p><strong><a href="http://www.bullseye.com/" rel="noreferrer">Bullseye Coverage</a> features:</strong></p> <ul> <li><a href="http://www.bullseye.com/platform.html" rel="noreferrer">Cross Platform Support</a> (win32, unix, and embedded), (supports linux gcc compilers and MSVC6)</li> <li><a href="http://www.bullseye.com/usability.html" rel="noreferrer">Easy to use</a> (up and running in a few hours).</li> <li><a href="http://www.bullseye.com/measurementTechnique.html" rel="noreferrer">Provides "best" metrics</a>: Function Coverage and Condition/Decision Coverage.</li> <li>Uses source code instrumentation.</li> </ul> <p>As for hooking into your continuous integration, it depends on which CI solution you use, but you can likely hook the instrumentation / coverage measurement steps into the make file you use for automated testing.</p> <hr> <h3>Testing Linux vs Windows?</h3> <p>So long as all your tests run correctly in both environments, you should be fine measuring coverage on one or the other. (Though Bullseye appears <a href="http://www.bullseye.com/platform.html" rel="noreferrer">to support both platforms</a>). But why aren't you doing continuous integration builds in both environments?? If you deliver to clients in both environments then you <em>need</em> to be testing in both. </p> <p>For that reason, it sounds like you might need to have two continuous build servers set up, one for a linux build and one for a windows build. Perhaps this can be easily accomplished with some virtualization software like <a href="http://www.vmware.com/" rel="noreferrer">vmware</a> or <a href="http://www.virtualbox.org/" rel="noreferrer">virtualbox</a>. You may not need to run code coverage metrics on both OSs, but you should definitely be running your unit tests on both.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload