Open phil-davis opened 5 years ago
A bit of discussion around here: https://github.com/owncloud/data_exporter/pull/58#issuecomment-457590048
And I'm sure this has been mentioned in other places.
Here is the part, to utilize codecovs tagging functionality - the reports need to be uploaded separately ( similar as done in core ).
This can be done either by splitting the integration and unit tests per matrix permutation and providing a tag - or by having separate upload targets with fixed tags.
(note: acceptance tests are another level up - "external" - there is not currently any coverage measure for those)
Generating code coverage for acceptance tests is usually not done - I can understand that this is a nice-to-have part for QA-Team.
Difficulty here would be to setup the remote apache instance with xdebug and collecting the coverage logs from there - while behat drives the testing
Some repos have both unit and integration tests. And each produce code coverage.
Decide a standard for naming and processing the multiple sets of coverage reports so that they do not stomp on each other, but do provide a reading of the code coverage of each level of testing.
(note: acceptance tests are another level up - "external" - there is not currently any coverage measure for those)