From 3478474a8a1fd22b10a02d3e34f3291c996181db Mon Sep 17 00:00:00 2001 From: Witold Bedyk Date: Thu, 7 Jun 2018 17:06:36 +0200 Subject: [PATCH] Initialize alarm in test_alarm_metric_mixcase In some cases thresholding engine needs longer to evaluate the first measurement and checking the alarm state returns UNDETERMINED. To make the test safer, we send the first measurement to initialize the alarm. Change-Id: Ib294952d29b5c1c464baa24978f4c18a257fe0bc Story: 2001539 Task: 20046 --- monasca_tempest_tests/tests/api/test_alarm_transitions.py | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/monasca_tempest_tests/tests/api/test_alarm_transitions.py b/monasca_tempest_tests/tests/api/test_alarm_transitions.py index 6498d5f..0e79699 100644 --- a/monasca_tempest_tests/tests/api/test_alarm_transitions.py +++ b/monasca_tempest_tests/tests/api/test_alarm_transitions.py @@ -202,7 +202,11 @@ class TestAlarmTransitions(base.BaseMonascaTest): # Ensure the new Alarm Definition gets to the Threshold Engine time.sleep(constants.ALARM_DEFINITION_CREATION_WAIT) - self._send_measurement(metric_def, 20) + self._send_measurement(metric_def, 1) alarm_id, initial_state = self._wait_for_alarm_creation(definition_id) - self.assertEqual("ALARM", initial_state) + self.assertEqual("UNDETERMINED", initial_state) + + self._send_measurement(metric_def, 20) + + self._wait_for_alarm_transition(alarm_id, "ALARM")