[asterisk-dev] [Code Review] 2525: Test suite: Allow pluggable modules to be executed against particular Asterisk Versions

jbigelow reviewboard at asterisk.org
Fri May 10 10:13:57 CDT 2013


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

(Updated May 10, 2013, 10:13 a.m.)


Review request for Asterisk Developers and Matt Jordan.


Changes
-------

Added a sample test-config.yaml file that describes most settings (info taken from the wiki and README.txt) and of course documents the minversion/maxversion parameters for pluggable modules.


Repository: testsuite


Description
-------

This allows pluggable modules to have their configuration section execute against particular version(s) of Asterisk. If the version of Asterisk meets the minversion and maxversion specified for the pluggable module, then it's config-section will be used. If neither minversion or maxversion are specified, it's config-section is used like how it currently does. This can be useful if for example the name of an AMI event is changed.


Diffs (updated)
-----

  /asterisk/trunk/lib/python/asterisk/TestRunner.py 3769 
  /asterisk/trunk/runtests.py 3769 
  /asterisk/trunk/sample-yaml/test-config.yaml.sample PRE-CREATION 

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


Testing
-------

Set many different combinations of minversion and maxversion and used the version flag of runtests.py to simulate many different Asterisk versions. This and the logs provided the information to ensure it properly worked.


Thanks,

jbigelow

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


More information about the asterisk-dev mailing list