I couldn't find a good self-explanatory example for the usage of Delphi-code-coverage tool so here you will find a simple example from top to bottom. The idea is really simple; I have a set of units which I want to know whether they are covered by my unit tests or not. Even though there is a lot of information about the project, I couldn't find a really good example explaining all the details about How to properly set up the project, folders, flags, etc. I have used the Delphi-code-coverage-wizard which is great to generate the initial structure (batch file + list of paths + units) but I went manual from there as I couldn't get any output.
I must say that both projects are really good and that's why I'm giving them an opportunity as I want to test the coverage of my projects under Delphi XE.
First step is to correctly identify where your source code is and your unit tests are. This step is really important as to correctly set-up the code coverage project. All my testing code is under my repository and available here: Delphi-repositoty. For this example I'm using a very simple example where I have a unique unit test which tries to cover two units (thundax.AbstractFactory.pas and thundax.Prototype.pas).
My unit test project is called thundax.DesignPatternsTest.exe which has 2 tests:
Now I want to know if those two unit tests cover my previously defined units (thundax.AbstractFactory.pas and thundax.Prototype.pas).
Download Delphi-Code-Coverage and leave it under your bin\ folder or where your test.exe application is (in my case thundax.DesignPatternsTest.exe).
Create two text files called dcov_paths.lst and dcov_units.lst. You can use Delphi-code-coverage-wizard to set up the initial structure, but I would rather go manual as I have more control of the execution.
- The first file (dcov_paths.lst) will contain the path to your source code:
- The second file (dcov_units.lst) will contain the list of unit tests you want to check whether they cover your code or not.
Your projects needs to have debug information generating a detailed Map file:
Now we can create a small batch file (dcov_execute.bat) or run the following command from the command line tool:
This is the configuration that works for me, where:
- -e identifies the executable to run (in this case the Unit test framework).
- -m identifies the map file (the map file contains all the debugging symbols).
- -ife include file extension (if you are using generics.collections use this option).
- -uf list of your units (source code, not your unit tests code).
- -spf list of source directories.
- -od Output directory (".\" gets the current).
- -lt generates log file. (Delphi-Code-Coverage-Debug.txt).
- -html Html output
- -xml Xml output
- -emma EMMA output
- -meta Generate separate meta and coverage files when generating emma output - 'coverage.em' and 'coverage.ec' will be generated for meta data and coverage data. (Needs -emma as well). These are the important files to run EMMA.
- CodeCoverage_summary.html (Html output)
- CodeCoverage_summary.xml (xml output)
- coverage.es (EMMA output)
- coverage.em (EMMA output)
- coverage.ec (EMMA output)
- thundax.AbstractFactory(thundax.AbstractFactory.pas).html (Your report)
- thundax.Prototype(thundax.Prototype.pas).html (Your report)
If you open the summary you will see the total of lines and %age covered by your test:
If you want to use EMMA, is as easy as this (once the code coverage tool has outputted the .ec and .em files):
Emma component will generate a coverage folder with the following html file:
The entire example can be found in my Delphi repository.
I hope you find this useful and start using it.