rabi fe4f250826 Don't check alarm state when signaled ... Scaling policies(alarm_url) are normally expected to be used with 'alarm_actions' of Alarm resource plugins by the template author. However, we should not check for the alarm state before proceeding on handling the signal. This would provide flexibility to use these policies with other alarm actions like 'insufficient_data_actions', if required. Change-Id: I733f986c9ac151f76aa997d26e9b9cf8afd9f6c9 Closes-Bug: #1598044		2016-07-25 05:33:32 +00:00
..
__init__.py	Move TestInstanceGroup to test_instance_group.py	2014-10-07 12:01:30 +10:00
inline_templates.py	Move all scaling policy tests to autoscaling/	2015-02-04 16:48:59 +10:00
test_heat_scaling_group.py	Added refs_map attribute to AutoScalingGroup	2016-06-22 10:25:25 -04:00
test_heat_scaling_policy.py	Don't check alarm state when signaled	2016-07-25 05:33:32 +00:00
test_launch_config.py	Remove unused stuff in test_launch_config.py	2016-03-09 10:26:18 +08:00
test_lbutils.py	Stack updated error if creation fails	2015-06-17 19:05:40 +08:00
test_new_capacity.py	Move new capacity calculation to scaling library	2015-09-10 21:01:24 +05:30
test_rolling_update.py	Fix scenario names in rolling update test	2015-09-10 10:43:21 -04:00
test_scaling_group.py	Unit tests: Don't use ResourceDefinition as cfn snippet	2016-05-01 19:42:20 -05:00
test_scaling_policy.py	Don't check alarm state when signaled	2016-07-25 05:33:32 +00:00
test_scaling_template.py	Fix [H405] pep rule in heat/tests	2015-10-12 14:08:16 +03:00