aboutsummaryrefslogtreecommitdiff
path: root/tests/data/test1330
diff options
context:
space:
mode:
authorYang Tse <yangsita@gmail.com>2013-03-15 19:58:00 +0100
committerYang Tse <yangsita@gmail.com>2013-03-15 19:59:51 +0100
commit1700668d783220957a2ad0d1f4f963be58b687f7 (patch)
treeb38fa3310b60e9e2b6b2c981c05fccc2a55c6b49 /tests/data/test1330
parenta8f93d4efc07cd445843b5bc82a3b38653744868 (diff)
tests: add #96 #558 and #1330
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.
Diffstat (limited to 'tests/data/test1330')
-rw-r--r--tests/data/test133050
1 files changed, 50 insertions, 0 deletions
diff --git a/tests/data/test1330 b/tests/data/test1330
new file mode 100644
index 000000000..8f8f9674b
--- /dev/null
+++ b/tests/data/test1330
@@ -0,0 +1,50 @@
+<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>