Coverage

What the unit tests exercised, line by line and branch by branch, in the build that produced this site. Each pack links into its part of the report, where every source file lists its lines with the count of times each ran and which way each branch went. The table is computed from the tracefile the coverage lane's gate was judged on, so the number shown is the number that passed; the gate itself is described with the lane in the CI pipeline.

Measured from main at 9ba7f64.

Pack	Lines		Branches
Core	3349 / 3349	100.0%	1342 / 1346	99.7%
CmsisRtos	75 / 75	100.0%	20 / 20	100.0%
FatFs	131 / 131	100.0%	60 / 60	100.0%
FreeRtos	64 / 64	100.0%	18 / 18	100.0%
LittleFs	138 / 138	100.0%	54 / 54	100.0%
LwipRaw	570 / 570	100.0%	185 / 186	99.4%
LwipSocket	382 / 382	100.0%	181 / 182	99.4%
MbedTls	772 / 773	99.8%	352 / 354	99.4%
OpenSsl	765 / 765	100.0%	396 / 398	99.4%
PlusFat	134 / 134	100.0%	58 / 58	100.0%
PlusTcp	343 / 343	100.0%	110 / 110	100.0%
Posix	755 / 756	99.8%	323 / 326	99.0%
StdAtomic	49 / 49	100.0%	15 / 16	93.7%
VxWorks64	647 / 647	100.0%	281 / 282	99.6%
WolfSsl	738 / 738	100.0%	380 / 380	100.0%
Total	8912 / 8914	99.9%	3775 / 3790	99.6%

Reading the report

A pack's index lists its source files with their line and branch rates. A file's page shows the source with each line's execution count in the margin. A line that never ran is marked, and a branch taken one way only is marked at the condition. The counts come from every test executable together, so a line counts as covered whichever executable reached it.

The report covers Core and every platform pack a Linux host can build. The Windows pack is tested on Windows and is not measured. The cross-built targets run their unit tests on the host against fakes, and that is what is measured.

To measure locally, build the coverage preset as Building & testing describes.