[asterisk-dev] [Code Review] 3353: testsuite: Test for receiving Play/Record start and stop events on ARI bridge playback/recording.

Jonathan Rose reviewboard at asterisk.org
Mon Mar 24 16:57:08 CDT 2014



> On March 20, 2014, 8:17 a.m., opticron wrote:
> > /asterisk/trunk/tests/rest_api/bridges/bridge_record/subscribe_bridge.py, line 46
> > <https://reviewboard.asterisk.org/r/3353/diff/1/?file=55987#file55987line46>
> >
> >     Use the logger instead if this needs to be logged somewhere.

Just leftover garbage.


- Jonathan


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


On March 13, 2014, 5:47 p.m., Jonathan Rose wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/3353/
> -----------------------------------------------------------
> 
> (Updated March 13, 2014, 5:47 p.m.)
> 
> 
> Review request for Asterisk Developers, Matt Jordan and Mark Michelson.
> 
> 
> Bugs: ASTERISK-23444
>     https://issues.asterisk.org/jira/browse/ASTERISK-23444
> 
> 
> Repository: testsuite
> 
> 
> Description
> -------
> 
> As mmichelson suggested, here are a couple automated tests for replicating the tests I did by hand in https://reviewboard.asterisk.org/r/3340/
> 
> The mechanism is fairly simple...
> 
> Channel enters stasis and starts the whole process
> Mixing bridge gets created via ARI
> An application subscribes to bridge stasis messages for the newly created bridge
> Channel gets pushed into the bridge via ARI
> Bridge is recorded via ARI / Bridge playback with sound:tt-weasels is executed via ARI
> The sound comes naturally to an end / the recording is stopped manually upon receiving its startup event
> The test closes in the same way as a normal bridge subscription test
> 
> 
> Diffs
> -----
> 
>   /asterisk/trunk/tests/rest_api/bridges/tests.yaml 4836 
>   /asterisk/trunk/tests/rest_api/bridges/bridge_record/test-config.yaml PRE-CREATION 
>   /asterisk/trunk/tests/rest_api/bridges/bridge_record/subscribe_bridge.py PRE-CREATION 
>   /asterisk/trunk/tests/rest_api/bridges/bridge_record/configs/ast1/extensions.conf PRE-CREATION 
>   /asterisk/trunk/tests/rest_api/bridges/bridge_play/test-config.yaml PRE-CREATION 
>   /asterisk/trunk/tests/rest_api/bridges/bridge_play/subscribe_bridge.py PRE-CREATION 
>   /asterisk/trunk/tests/rest_api/bridges/bridge_play/configs/ast1/extensions.conf PRE-CREATION 
> 
> Diff: https://reviewboard.asterisk.org/r/3353/diff/
> 
> 
> Testing
> -------
> 
> ran both tests some number of times to ensure success was repeatable.
> Varied some expectations to make sure everything I was looking for was actually being checked appropriately.
> 
> 
> Thanks,
> 
> Jonathan Rose
> 
>

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


More information about the asterisk-dev mailing list