1700668d78
These verfy that the 'memory tracking' subsystem is actually doing its job when using curl tool (#96), a test in libtest (#558) and also a unit test (#1330), in order to prevent regressions in this functionallity.
51 lines
625 B
Plaintext
51 lines
625 B
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
unittest
|
|
TrackMemory
|
|
</keywords>
|
|
</info>
|
|
|
|
#
|
|
# Server-side
|
|
<reply>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
none
|
|
</server>
|
|
<features>
|
|
unittest
|
|
TrackMemory
|
|
</features>
|
|
# tool is what to use instead of 'curl'
|
|
<tool>
|
|
unit1330
|
|
</tool>
|
|
|
|
<name>
|
|
unit tests memory tracking operational
|
|
</name>
|
|
<command>
|
|
nothing
|
|
</command>
|
|
</client>
|
|
|
|
#
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<file name="log/memdump" mode="text">
|
|
MEM ../../../tests/unit/unit1330.c: malloc()
|
|
MEM ../../../tests/unit/unit1330.c: free()
|
|
</file>
|
|
<stripfile>
|
|
s/ =.*//
|
|
s/\(.*\)/()/
|
|
s/:\d+/:/
|
|
</stripfile>
|
|
</verify>
|
|
|
|
</testcase>
|