Currently in Portal we have the ability to get the code coverage for our unit tests only. This gives us the appearance that our coverage is very low whereas we touch a lot of the other code though our API tests.
Proposed solution:
I've created a development branch which gives us the ability to:
Run PFE using nyc to get information about the files that are touched during the API Tests.
Collect the generated coverage data out of a Docker container.
Combine this file with a coverage file generated from the Unit tests (or local run tests).
Description of the enhancement:
Currently in Portal we have the ability to get the code coverage for our unit tests only. This gives us the appearance that our coverage is very low whereas we touch a lot of the other code though our API tests.
Proposed solution:
I've created a development branch which gives us the ability to:
nyc
to get information about the files that are touched during the API Tests.This branch needs tidying and testing as it was only designed to be an MVP. The thought for this is in the future it'll be able to be shown on Jenkins (https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin).
Design decisions:
test.sh
or separate?Note: