The heat.tests.functional.test_CFN_API_Actions Module

class heat.tests.functional.test_CFN_API_Actions.CfnApiFunctionalTest(methodName='runTest')[source]

Bases: unittest.case.TestCase

This test launches a wordpress stack then attempts to verify correct operation of all actions supported by the heat CFN API

Note we use class-level fixtures to avoid setting up a new stack for every test method, we set up the stack once then do all the tests, this means all tests methods are performed on one class instance, instead of creating a new class for every method, which is the normal nose unittest.TestCase behavior.

The nose docs are a bit vague on how to do this, but it seems that (setup|teardown)All works and they have to be classmethods.

Contrary to the nose docs, the class can be a unittest.TestCase subclass

classmethod setupAll()[source]
speed = 'slow'
tag = ['func', 'wordpress', 'api', 'cfn', 'F17']
classmethod teardownAll()[source]
testDescribeStackEvents()[source]
testDescribeStackResource()[source]
testDescribeStackResources()[source]
testDescribeStacks()[source]
testGetTemplate()[source]
testListStackResources()[source]
testListStacks()[source]
testValidateTemplate()[source]
test_instance()[source]

This Page