Howto BullsEye - Quick...
As per these facts we need a procedure that does the following.
It is advised not to change the value again, let it be the one you use untill the session finishes, but the file you select should be for this session only.
If you are measuring several modules, or have multiple unittests, your code can loop from this point.
****************** Loop start
First parse the project file, so we get all the relevant files that are included in the project / module that we are going to unittest and get coverage for.
Save result to a temporary file which we will use later, in this example we call that one %tempfile%.
BullsEye Coverage file has it's own internal format, so lets create one now (this is a new file, right...)
Turn on Coverage Building (so BullsEye can injects it's compilers and linkers)
Add the files you parsed earlier and saved to a temp file (files can be added one by one, by that is slower)
Now build the project, the unittest and run the unittest....
When done results are in the file selected by %COVFILE%
Turn off Coverage Building
(This saves whatever findings bullseye still has in memory....)
copy the covfile to another location
Before you do another measurement, you can export the results to your likings.
Result export utilies are:
feel free to read doc on the utils yourself - they do tell about themselves if you just call them in the command prompt
The delete %COVFILE%, a new will be initialized in beginning of loop
Loop - get next project to parse.
When loop is done you can merge all the covfiles you created into one big with the covmerge utility
BullsEye Coverage >