curl-curl/tests/data/test3207
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

179 lines
4.3 KiB
Plaintext

<testcase>
<info>
<keywords>
HTTPS
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Type: text/html
Content-Length: 29
run 1: foobar and so on fun!
</data>
<datacheck>
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
run 1: foobar and so on fun!
</datacheck>
</reply>
# Client-side
<client>
<features>
SSL
OpenSSL
</features>
<server>
https
</server>
<name>
concurrent HTTPS GET using shared ssl session cache
</name>
<tool>
lib%TESTNUMBER
</tool>
# provide URL and ca-cert
<command>
https://localhost:%HTTPSPORT/%TESTNUMBER %CERTDIR/certs/test-ca.crt
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<limits>
Allocations: 13300
</limits>
</verify>
</testcase>