[asterisk-dev] [Code Review] 3476: Memory Pre- and Post-Test Condition
Benjamin Keith Ford
reviewboard at asterisk.org
Fri Apr 25 10:41:55 CDT 2014
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3476/
-----------------------------------------------------------
(Updated April 25, 2014, 3:41 p.m.)
Review request for Asterisk Developers.
Changes
-------
- Added a yaml sample that explains the usage of this test condition and an example
Bugs: ASTERISK-18429
https://issues.asterisk.org/jira/browse/ASTERISK-18429
Repository: testsuite
Description
-------
This testcondition can be enabled for any test using the keyword 'memory' under testconditions. The purpose of this testcondition is to check the memory allocated before and after the test, and make sure they are within a certain range. If the test wants to look at something specific (such as channel.c), then each allocation that you want to look at can also be specified in under 'allocations'. If both the global memory and individual allocations are to be checked by the test, that option can be enabled by setting 'both' to value True.
Diffs (updated)
-----
./asterisk/trunk/test-config.yaml 4944
./asterisk/trunk/sample-yaml/memorytestcondition-config.yaml.sample PRE-CREATION
./asterisk/trunk/lib/python/asterisk/test_conditions.py 4944
./asterisk/trunk/lib/python/asterisk/test_case.py 4944
./asterisk/trunk/lib/python/asterisk/memory_test_condition.py PRE-CREATION
Diff: https://reviewboard.asterisk.org/r/3476/diff/
Testing
-------
Thanks,
Benjamin Keith Ford
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20140425/7644b399/attachment-0001.html>
More information about the asterisk-dev
mailing list