TemplateDefinition test case is complicated

Bug #1477833 reported by yuanying
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Low
yuanying

Bug Description

TemplateDefinitionTestCase has its children class tests.
So we need split up it.

yuanying (yuanying)
Changed in magnum:
assignee: nobody → yuanying (ootsuka)
importance: Undecided → Low
milestone: none → liberty-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

Changed in magnum:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/205381
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=0101200967897e50ebd05b55d0b05f37a951257d
Submitter: Jenkins
Branch: master

commit 0101200967897e50ebd05b55d0b05f37a951257d
Author: OTSUKA, Yuanying <email address hidden>
Date: Fri Jul 24 14:45:50 2015 +0900

    Split TemplateDefinitionTestCase to different test case

    This test case will become huge when adding more unit test to each
    TemplateDefinition classes. This patch splits this test case.

    Change-Id: Ia968b1c3e7fabca1d00773bb6979dd80bae2562f
    Closes-Bug: #1477833

Changed in magnum:
status: In Progress → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
status: Fix Committed → Fix Released
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.