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 protected]>
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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1588389

Title:
  Change JS coverage report dir to match CTI

Status in OpenStack Dashboard (Horizon):
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1588389/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to