Code coverage to expose project

Bug #1489155 reported by Ronald Bradford on 2015-08-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eslint-config-openstack
Undecided
Unassigned

Bug Description

When generating code coverage (i.e. npm test) the cover HTML output does not give any indication to the project to which the output belongs when viewing the coverage report.

Ideally a wish list would be to indicate the specific project in a header.

Currently python code coverage (e.g. http://logs.openstack.org/38/212738/12/check/designate-coverage/bc2e329/cover/ and http://logs.openstack.org/82/165682/8/check/nodepool-coverage/08c6340/cover ) it can be determined which project by the prefix of the filenames.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers