curl/tests/data/test1330
Steve Holme 0922f76240
tests: Automatically deduce the tool name from the test case for unit tests
It is still possible to override the executable to run during the test,
using the <tool> tag, but this patch removes the requirement that the
tag must be present for unit tests.

It also removes the possibility of human error when existing test cases
are used as the basis for new tests, as recently witnessed in 81c37124.

Reviewed-by: Daniel Stenberg
Closes #4976
2020-02-27 00:51:49 +00:00

47 lines
543 B
Plaintext

<testcase>
<info>
<keywords>
unittest
TrackMemory
</keywords>
</info>
#
# Server-side
<reply>
</reply>
# Client-side
<client>
<server>
none
</server>
<features>
unittest
TrackMemory
</features>
<name>
unit tests memory tracking operational
</name>
<command>
nothing
</command>
</client>
#
# Verify data after the test has been "shot"
<verify>
<file name="log/memdump">
MEM unit1330.c: malloc()
MEM unit1330.c: free()
</file>
<stripfile>
s/ =.*//
s/\(.*\)/()/
s/:\d+/:/
s:^(MEM )(.*/)(.*):$1$3:
s/\r\n/\n/
</stripfile>
</verify>
</testcase>