curl-curl/tests/data/test1156
Daniel Stenberg 8724306e78
runtests: support memory-limits per test
The idea here is to set limits per test how many allocations and maximum
amount of memory it is allowed to use. This is a means to make sure the
number and total size of allocations are kept in check and don't
mistakenly "blow up".

If runtests.pl detects that the given limits have been exceeded it fails
the test case with an error.

The `<verify>` part now supports `<limits>`, and in this section two
limits can be set for each test (verified in debug builds only):

    Allocations: [number of allocation calls]
    Maximum allocated: [maximum concurrent memory allocated]

Default limits (used if nothing is set in the test file):

    Allocations: 1000
    Maximum allocated: 1000000

Closes #17821
2025-07-08 10:14:45 +02:00

75 lines
992 B
Plaintext

<testcase>
<info>
<keywords>
HTTP
HTTP GET
Content-Range
Resume
Range
</keywords>
</info>
# Server-side
<reply>
<data nocheck="yes">
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 5
body
</data>
<data1 nocheck="yes">
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 5
Content-Range: bytes 3/7
body
</data1>
<data2 nocheck="yes">
HTTP/1.1 416 Requested Range Not Satisfiable
Content-Type: text/html
Content-Length: 5
body
</data2>
<data3 nocheck="yes">
HTTP/1.1 416 Requested Range Not Satisfiable
Content-Type: text/html
Content-Length: 5
Content-Range: bytes */2
body
</data3>
</reply>
# Client-side
<client>
<server>
http
</server>
<tool>
lib%TESTNUMBER
</tool>
<name>
HTTP resume/range fail range-error content-range combinations
</name>
<command>
http://%HOSTIP:%HTTPPORT/want/%TESTNUMBER
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<stdout>
0
</stdout>
<limits>
Allocations: 1300
</limits>
</verify>
</testcase>