[asterisk-dev] [Code Review]: chan_iax2 consumption test for ACLs

Paul Belanger reviewboard at asterisk.org
Wed Jul 18 15:19:40 CDT 2012



> On July 17, 2012, 2:20 p.m., Paul Belanger wrote:
> > Add this to #asterisk-dev, but making a note here too.  I feel this and chan_sip ACL test could be refactored in a way to avoid duplicated code.  A side from 2 line, this is virtually the same as the chan_sip runtest.
> 
> jrose wrote:
>     I suppose I could add another subclass of TestClass.
>     
>     The biggest difference between the tests aside from the originate statements of course is the evaluation of the hangup. I'll just have the addition of the expecations work the way it currently does and have the concrete test establish its own hangup evaluation function.
> 
> jrose wrote:
>     After talking with mmichelson, I've decided I'm probably not going to do this right now since it's just these two tests being written. If we write more tests based on this stuff though, it'll definitely be worth refactoring this stuff then.

That's unfortunate.  -1 here.


- Paul


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


On July 17, 2012, 2:10 p.m., jrose wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2046/
> -----------------------------------------------------------
> 
> (Updated July 17, 2012, 2:10 p.m.)
> 
> 
> Review request for Asterisk Developers, Mark Michelson, opticron, and Matt Jordan.
> 
> 
> Summary
> -------
> 
> Just like the SIP test, only Iaxy.
> 
> Tests calls made with IAX2 peers using different addresses against different ACLs.  Includes tests for the following:
> 
> 1. Single ACL set via permit/deny
> 2. Single ACL set via acl=named_acl
> 3. Multiple ACLs set via acl=named_acl1,named_acl2,...
> 4. A bad ACL set via acl=<unavailable ACL name>
> 5. Multiple ACLs set from a realtime SQLite3 db via acl=realtime1,realtime2,...
> 
> 
> Diffs
> -----
> 
>   /asterisk/trunk/tests/iax2/acl_call/configs/ast1/acl.conf PRE-CREATION 
>   /asterisk/trunk/tests/iax2/acl_call/configs/ast1/extconfig.conf PRE-CREATION 
>   /asterisk/trunk/tests/iax2/acl_call/configs/ast1/extensions.conf PRE-CREATION 
>   /asterisk/trunk/tests/iax2/acl_call/configs/ast1/iax.conf PRE-CREATION 
>   /asterisk/trunk/tests/iax2/acl_call/configs/ast1/modules.conf PRE-CREATION 
>   /asterisk/trunk/tests/iax2/acl_call/configs/ast1/res_config_sqlite3.conf PRE-CREATION 
>   /asterisk/trunk/tests/iax2/acl_call/realtime.sqlite3 UNKNOWN 
>   /asterisk/trunk/tests/iax2/acl_call/run-test PRE-CREATION 
>   /asterisk/trunk/tests/iax2/acl_call/test-config.yaml PRE-CREATION 
>   /asterisk/trunk/tests/iax2/tests.yaml 3312 
> 
> Diff: https://reviewboard.asterisk.org/r/2046/diff
> 
> 
> Testing
> -------
> 
> 1. Ran the test itself and made sure the expected log messages appeared
> 2. Changed some test expectations to see how it would handle results differing from expectations.
> 
> 
> Thanks,
> 
> jrose
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20120718/c4c94116/attachment.htm>


More information about the asterisk-dev mailing list