|
|
Some of the testsuite tests have an option code coverage enabled. This option allows to know which part of the code has been tested by the testsuite, and which part of the code remains untested.
|
|
|
|
|
|
![Capture_d_écran_de_2019-08-13_18-01-32](uploads/5b0e78819ddb11e087cffbfb9c3079a7/Capture_d_écran_de_2019-08-13_18-01-32.png)
|
|
|
|
|
|
You can access to the section by blocking on the icon located in the column `Code Coverage`
|
|
|
|
|
|
![Capture_d_écran_de_2019-08-13_18-02-50](uploads/d72f9a564344c7cd67c0b63d1ea9cbd2/Capture_d_écran_de_2019-08-13_18-02-50.png)
|
|
|
|
|
|
The Code Coverage page shows two tables. First, a summary, in which appears the total number of files (resp. functions, and code blocks), the quantity of covered and uncovered files/functions/blocks, and the coverage proportion for each of them.
|
|
|
The block coverage represents the finest measure of the code effectively tested.
|
|
|
|
|
|
The second table gives detailed information about each source code file of Alya. It indicates the module, the path, and the number of functions contained in the file/covered functions/function coverage, as well as the block number/covered blocks/block coverage. The status column depicts a symbol, red for a 0% block coverage, orange for a <50% coverage, violet for a <100% coverage and green for full coverage.
|
|
|
|
|
|
You can click on the file to get more insight about the code parts that have been tested.
|
|
|
|
|
|
![Capture_d_écran_de_2019-08-13_18-10-48](uploads/9cece5dc5e818c3d9e9ad9266f8dc6b8/Capture_d_écran_de_2019-08-13_18-10-48.png) |
|
|
\ No newline at end of file |