Change JS coverage report dir to match CTI

Bug #1588389 reported by Matt Borland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Matt Borland

Bug Description

Krotscheck has pointed out that to follow the CTI definition, we should place all our JS coverage reports in ./cover. This means we need subdirs in there for 'horizon' and 'openstack_dashboard'.

https://governance.openstack.org/reference/cti/javascript-cti.html#executing-tests-and-code-coverage

Tags: angularjs
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/324558

Changed in horizon:
assignee: nobody → Matt Borland (palecrow)
status: New → In Progress
Matt Borland (palecrow)
tags: added: angularjs
Changed in horizon:
importance: Undecided → Low
milestone: none → newton-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/324558
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=bf7c5908fbe46d322bb1842ff659206d8fdd3583
Submitter: Jenkins
Branch: master

commit bf7c5908fbe46d322bb1842ff659206d8fdd3583
Author: Matt Borland <email address hidden>
Date: Thu Jun 2 08:25:14 2016 -0600

    Output JS Karma test coverage reports to ./cover/

    Per CTI direction (see bug filing), this patch moves the JS Karma test coverage
    reports to ./cover/ so they may be collected in the gate for archiving.

    The two runs each have their own directory so they don't overlap/conflict.

    Change-Id: I0b1536c115a516f4b6ab80b5ebab5337b308c210
    Closes-Bug: 1588389

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/horizon 10.0.0.0b2

This issue was fixed in the openstack/horizon 10.0.0.0b2 development milestone.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.