Skip to content
Snippets Groups Projects
Commit 80860537 authored by Francesco Giacomini's avatar Francesco Giacomini
Browse files

initial information on how to evaluate test coverage

parent b40916c6
No related branches found
No related tags found
1 merge request!3Add VOMS embedded variables
......@@ -27,3 +27,19 @@ Using the docker image provided to exploit Openresty in the Storm2 project (see
prove -v
A copy of the `t` folder is needed since the `prove` command creates a directory `servroot` in `t`.
### Test coverage
To enable test coverage pass the `--coverage` option to both the compiler and the linker. For example, if the build happens inside the ``storm2/nginx-voms-build`` image:
```
% ./configure ${resty_config_options} --add-module=../ngx_http_voms_module --with-debug --with-cc-opt="-g -O0 --coverage" --with-ld-opt="--coverage"
% make && make install
```
Building in debug mode, with no optimizations, helps to better associate coverage information to source code.
The above command generates data files aside the source files for all Nginx. To enable coverage only for ``ngx_http_voms_module`` the ``--coverage`` option should be passed only when compiling ``ngx_http_voms_module.cpp`` (to be done).
The run the tests, e.g. with `prove`. This will create other data files with coverage information. To view that information, run `gcov <source of object file>`, e.g. `gcov /home/build/openresty-1.13.6.1/build/nginx-1.13.6/objs/addon/src/ngx_http_voms_module.o`. This will produce files with the ``.gcov`` extension in the current directory.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment