Angus Salkeld 3c9bdbeae6 Move nested stack delete test to functional ...

This tries to prove that if you manually delete a nested
stack, the parent stack is still deletable.

part of blueprint decouple-nested
Change-Id: I1d0bf7b5d982dc1f312fbe70cbb09a2e624e3371

2015-02-17 21:14:38 +10:00

..

__init__.py

Functional test UpdateStackTest

2014-10-20 16:31:09 +13:00

test_autoscaling.py

Move autoscaling tests with signals to functional

2015-02-12 19:35:51 +10:00

test_aws_stack.py

Move aws nested stack tests to functional tests

2015-02-03 18:53:30 +10:00

test_default_parameters.py

Add "parameter_defaults" to the environment

2014-12-15 09:44:11 +10:00

test_heat_autoscaling.py

Test for path attributes in OS::Heat::AutoScalingGroup

2015-02-06 13:07:01 +02:00

test_instance_group.py

Wait for all resources to get updated before asserting state

2015-02-03 11:27:40 +10:00

test_remote_stack.py

Enable H305 and H307 style checks

2015-01-20 09:47:25 +02:00

test_resource_group.py

Move resource group property update tests to functional

2015-01-23 15:31:14 +10:00

test_template_resource.py

Move nested stack delete test to functional

2015-02-17 21:14:38 +10:00

test_update.py

Move template resource tests to functional

2015-01-12 23:07:05 +10:00

test_validation.py

Move assign_keypair method in base class

2015-02-13 06:27:14 -05:00