platformio / platformio/platformio-core

pio remote support code coverage reporting

Open
#4,459 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature remote
Dominant language
Python
Stars
9.5k
Forks
905
Avg merge
2d 13h
Merged PRs (30d)
2

Description

Feature Request

I am trying to add Sonar to my GitLab pipeline to get code coverage reporting and analysis. This works very well when running pio test --junit-output-path . however that option is not availalbe to pio remote test. I would like to be able to run pio remote test -e <env_name> --junit-output-path <path_to_coverage_report>. There is no coverage reporting option that I have found for this scenario but I am fairly new to embedded testing and development so I haven't been exposed to all the tools that are available so there may be one but don't know of it.

Description of problem

I am using an Arduino MKR WiFi 1010 and have not been able to find an emulator for the Cortex-M0 processor it uses. I need to run the unit tests through pio remote [options] and also want to generate the same code coverage reports that I am able to produce locally.

Expected Results

Executing pio remote test --junit-output-path <report_path> generates a coverage report and the report is stored at <report_path> where it can be used by the coverage analysis tool.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the pio remote test entry point and compare its options with local pio test --junit-output-path. Determine how remote test execution can produce and store the requested report at the supplied path; done when the option is accepted and the generated report is usable by the stated coverage analysis workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.