hzl | 1ccac19 | 2016-06-02 18:22:12 | [diff] [blame] | 1 | # Android code coverage instructions |
| 2 | |
mvanouwerkerk | 0ac0a37 | 2016-10-18 09:00:31 | [diff] [blame] | 3 | These are instructions for collecting code coverage data for android |
Yun Liu | 02ae34b | 2019-07-18 22:01:44 | [diff] [blame] | 4 | instrumentation and JUnit tests. |
hzl | 1ccac19 | 2016-06-02 18:22:12 | [diff] [blame] | 5 | |
| 6 | [TOC] |
| 7 | |
Yun Liu | 02ae34b | 2019-07-18 22:01:44 | [diff] [blame] | 8 | ## How JaCoCo coverage works |
hzl | 1ccac19 | 2016-06-02 18:22:12 | [diff] [blame] | 9 | |
Yun Liu | 02ae34b | 2019-07-18 22:01:44 | [diff] [blame] | 10 | In order to use JaCoCo code coverage, we need to create build time pre-instrumented |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 11 | class files and runtime **.exec** files. Then we need to process them using the |
Yun Liu | eaf7a454 | 2019-05-15 17:27:39 | [diff] [blame] | 12 | **build/android/generate_jacoco_report.py** script. |
hzl | 1ccac19 | 2016-06-02 18:22:12 | [diff] [blame] | 13 | |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 14 | ## How to collect coverage data |
hzl | 1ccac19 | 2016-06-02 18:22:12 | [diff] [blame] | 15 | |
mvanouwerkerk | 0ac0a37 | 2016-10-18 09:00:31 | [diff] [blame] | 16 | 1. Use the following GN build arguments: |
mvanouwerkerk | 0ac0a37 | 2016-10-18 09:00:31 | [diff] [blame] | 17 | |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 18 | ```gn |
| 19 | target_os = "android" |
Yun Liu | c0f2f73 | 2019-09-18 17:06:31 | [diff] [blame] | 20 | use_jacoco_coverage = true |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 21 | ``` |
David 'Digit' Turner | 40560ef7 | 2018-03-07 09:44:28 | [diff] [blame] | 22 | |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 23 | Now when building, pre-instrumented files will be created in the build directory. |
David 'Digit' Turner | 40560ef7 | 2018-03-07 09:44:28 | [diff] [blame] | 24 | |
hzl | 1ccac19 | 2016-06-02 18:22:12 | [diff] [blame] | 25 | 2. Run tests, with option `--coverage-dir <directory>`, to specify where to save |
Yun Liu | 02ae34b | 2019-07-18 22:01:44 | [diff] [blame] | 26 | the .exec file. For example, you can run chrome JUnit tests: |
mvanouwerkerk | 0ac0a37 | 2016-10-18 09:00:31 | [diff] [blame] | 27 | `out/Debug/bin/run_chrome_junit_tests --coverage-dir /tmp/coverage`. |
David 'Digit' Turner | 40560ef7 | 2018-03-07 09:44:28 | [diff] [blame] | 28 | |
Yun Liu | 02ae34b | 2019-07-18 22:01:44 | [diff] [blame] | 29 | 3. The coverage results of JUnit and instrumentation tests will be merged |
mvanouwerkerk | 0ac0a37 | 2016-10-18 09:00:31 | [diff] [blame] | 30 | automatically if they are in the same directory. |
David 'Digit' Turner | 40560ef7 | 2018-03-07 09:44:28 | [diff] [blame] | 31 | |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 32 | ## How to generate coverage report |
David 'Digit' Turner | 40560ef7 | 2018-03-07 09:44:28 | [diff] [blame] | 33 | |
Yun Liu | 02ae34b | 2019-07-18 22:01:44 | [diff] [blame] | 34 | 1. Now we have generated .exec files already. We can create a JaCoCo HTML/XML/CSV |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 35 | report using `generate_jacoco_report.py`, for example: |
| 36 | |
| 37 | ```shell |
| 38 | build/android/generate_jacoco_report.py \ |
| 39 | --format html \ |
Finnur Thorarinsson | ab96686 | 2020-03-27 15:31:38 | [diff] [blame] | 40 | --output-dir /tmp/coverage_report/ \ |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 41 | --coverage-dir /tmp/coverage/ \ |
| 42 | --sources-json-dir out/Debug/ \ |
| 43 | ``` |
Yun Liu | eaf7a454 | 2019-05-15 17:27:39 | [diff] [blame] | 44 | Then an index.html containing coverage info will be created in output directory: |
David 'Digit' Turner | 40560ef7 | 2018-03-07 09:44:28 | [diff] [blame] | 45 | |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 46 | ``` |
| 47 | [INFO] Loading execution data file /tmp/coverage/testTitle.exec. |
| 48 | [INFO] Loading execution data file /tmp/coverage/testSelected.exec. |
| 49 | [INFO] Loading execution data file /tmp/coverage/testClickToSelect.exec. |
| 50 | [INFO] Loading execution data file /tmp/coverage/testClickToClose.exec. |
| 51 | [INFO] Loading execution data file /tmp/coverage/testThumbnail.exec. |
| 52 | [INFO] Analyzing 58 classes. |
| 53 | ``` |
Yun Liu | eaf7a454 | 2019-05-15 17:27:39 | [diff] [blame] | 54 | |
Yun Liu | 02ae34b | 2019-07-18 22:01:44 | [diff] [blame] | 55 | 2. For XML and CSV reports, we need to specify `--output-file` instead of `--output-dir` since |
| 56 | only one file will be generated as XML or CSV report. |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 57 | ```shell |
| 58 | build/android/generate_jacoco_report.py \ |
| 59 | --format xml \ |
Finnur Thorarinsson | ab96686 | 2020-03-27 15:31:38 | [diff] [blame] | 60 | --output-file /tmp/coverage_report/report.xml \ |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 61 | --coverage-dir /tmp/coverage/ \ |
| 62 | --sources-json-dir out/Debug/ \ |
| 63 | ``` |
Yun Liu | eaf7a454 | 2019-05-15 17:27:39 | [diff] [blame] | 64 | |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 65 | or |
| 66 | |
| 67 | ```shell |
| 68 | build/android/generate_jacoco_report.py \ |
| 69 | --format csv \ |
Finnur Thorarinsson | ab96686 | 2020-03-27 15:31:38 | [diff] [blame] | 70 | --output-file /tmp/coverage_report/report.csv \ |
Yun Liu | 435bb17 | 2019-05-17 21:44:34 | [diff] [blame] | 71 | --coverage-dir /tmp/coverage/ \ |
| 72 | --sources-json-dir out/Debug/ \ |
| 73 | ``` |