File: code_coverage.md

package info (click to toggle)
thunderbird 1%3A143.0.1-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 4,703,968 kB
  • sloc: cpp: 7,770,492; javascript: 5,943,842; ansic: 3,918,754; python: 1,418,263; xml: 653,354; asm: 474,045; java: 183,079; sh: 111,238; makefile: 20,410; perl: 14,359; objc: 13,059; yacc: 4,583; pascal: 3,405; lex: 1,720; ruby: 999; exp: 762; sql: 715; awk: 580; php: 436; lisp: 430; sed: 69; csh: 10
file content (25 lines) | stat: -rw-r--r-- 1,033 bytes parent folder | download | duplicates (14) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
 
---
layout: page
title: Code coverage
permalink: /contributing/code-coverage
---

# Code Coverage

> In computer science, test coverage is a measure used to describe the degree to which the source code of a program is executed when a particular test suite runs. A program with high test coverage, measured as a percentage, has had more of its source code executed during testing, which suggests it has a lower chance of containing undetected software bugs compared to a program with low test coverage. ([Wikipedia](https://en.wikipedia.org/wiki/Code_coverage))

# Automated reports

For pull requests and main pushes we generate code coverage reports on taskcluster and they can be accessed via the GitHub checks.

# Generating reports locally

Locally you can generate a coverage report for a module with the following command:
```bash
./gradlew -Pcoverage <module>:build
```

After that you'll find an HTML report at the following location:
```
components/<path to module>/build/reports/jacoco/jacocoTestReport/html/index.html
```