x/monasca-vagrant
Code Issues Proposed changes
monasca-vagrant/tests
History
Craig Bryant c70f1f8a6a Fix smoke test 
Agent renamed the metrics the smoke test was using. Change to use
the new metric names

Change-Id: I1271d738d169c57df8ddba4165a65deb1982fbff
2014-09-05 13:37:57 -06:00
..
alarms
Simple test setup from api->thresh->notification->persister
2014-03-24 16:44:25 -06:00
alarms-no-notification
Simple test setup from api->thresh->notification->persister
2014-03-24 16:44:25 -06:00
alarm_crud.py
Added test to alarm_crud.py of changing state via API and then having it change back to original state via the incoming metrics.
2014-06-11 09:36:57 -06:00
alarm.py
Update the field name for actions_enabled in Alarms. It changed in the API
2014-06-02 13:23:41 -06:00
alarms_notifications.py
Simple test setup from api->thresh->notification->persister
2014-03-24 16:44:25 -06:00
cli_wrapper.py
Name changes for the agent package.
2014-07-29 16:52:22 -06:00
measurement_test.py
Fix the system tests to work with keystone auth
2014-08-06 10:43:54 -06:00
notification_crud.py
Name changes for the agent package.
2014-07-29 16:52:22 -06:00
notification_cycleTest.py
Added test to alarm_crud.py of changing state via API and then having it change back to original state via the incoming metrics.
2014-06-11 09:36:57 -06:00
notification-jmeter.jmx
Simple test setup from api->thresh->notification->persister
2014-03-24 16:44:25 -06:00
notification.json
Initial alarm notifications.
2014-03-24 13:28:33 -06:00
notification.py
Added test to alarm_crud.py of changing state via API and then having it change back to original state via the incoming metrics.
2014-06-11 09:36:57 -06:00
README.md
test readme fix
2014-05-09 09:47:39 -06:00
smoke.py
Fix smoke test
2014-09-05 13:37:57 -06:00
utils.py
Fix the system tests to work with keystone auth
2014-08-06 10:43:54 -06:00

README.md

Test notifications

  • The api is currently rejecting alarms with no action specified, so expect an error defining that alarm.
  • Setup alarms and Notifications
  • Run the jmeter tests
    • jmeter -t notification-jmeter.jmx &
    • The config is saved for a basic test that should create a notification on alarm and a hundred non-notification alarms. Change the thread loop counts to try different combinations.