[~lfitzgerald] Sure, coveralls code coverage only pertains to go server code test coverage. It can be seen in the CI config where the code coverage is generated [here|https://github.com/aerogear/mobile-security-service/blob/master/.circleci/config.yml#L31]. Coveralls picks up the generated file, and that's what drives the code coverage % stat.
There is a code coverage command included with the UI [here|https://github.com/aerogear/mobile-security-service/blob/master/ui/package.json#L27] to generate code coverage data (which is similar to the one for the UI in the MDC), but these output stats are not included in the code coverage output file used fed to coveralls. This is the same as the MDC, where code coverage data from the UI tests are not included in the coveralls code stats.
The above code coverage command can be run from the Makefile [here|https://github.com/aerogear/mobile-security-service/blob/master/Makefile#L158]
|
|
