[asterisk-dev] [Code Review] 4520: Testsuite: stasis: set a channel variable on websocket disconnect error

Ashley Sanders reviewboard at asterisk.org
Fri Mar 27 10:02:51 CDT 2015


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4520/
-----------------------------------------------------------

(Updated March 27, 2015, 10:02 a.m.)


Review request for Asterisk Developers.


Changes
-------

Changed reference to STASIS_STATUS to STASISSTATUS


Bugs: ASTERISK-24802
    https://issues.asterisk.org/jira/browse/ASTERISK-24802


Repository: testsuite


Description (updated)
-------

When an error occurs while writing to a web socket, the web socket is disconnected and the event is logged. A side-effect of this, however, is that any application on the other side waiting for a response from Stasis is left hanging indefinitely (as there is no mechanism presently available for notifying interested parties about web socket error states in Stasis).

This patch introduces a new channel variable: STASISSTATUS to give outside applications context when errors occur in Stasis that interrupt normal processing.

This test exercises three scenarios to elicit updates to the STASIS_STATUS channel variable:
1) The 'Babs' scenario: tests a nominal path of Stasis to verify the 'ACTIVE' state is correctly applied. For this test, a call is originated under normal conditions and then the system is polled for the value of STASIS_STATUS before the channel is hung up.
2) The 'Bugs' scenario: tests the situation where a call is originated requesting an app that was never registered in Stasis to verify the 'FAILED' state is correctly applied.
3) The 'Buster' scenario: tests the situation where an app that was registered in Stasis when call A was originated (and while call A is still active) but is no longer registered when call B is originated. Determines if the 'FAILED' state is correctly applied.

 ***Note*** This is a test. It is only a test. The review for the Asterisk source can be found at: https://reviewboard.asterisk.org/r/4519/


Diffs
-----

  ./asterisk/trunk/tests/rest_api/applications/tests.yaml 6547 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/test_scenario_factory.py PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/test_scenario.py PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/test_case.py PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/test-config.yaml PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/run-test PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/observable_object.py PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/configs/ast1/sip.conf PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/configs/ast1/http.conf PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/configs/ast1/extensions.conf PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/configs/ast1/ari.conf PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasis_status/ari_client.py PRE-CREATION 

Diff: https://reviewboard.asterisk.org/r/4520/diff/


Testing
-------


Thanks,

Ashley Sanders

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20150327/e613648b/attachment.html>


More information about the asterisk-dev mailing list