1
0
mirror of https://github.com/moparisthebest/curl synced 2024-08-13 17:03:50 -04:00

tests: Replace outdated test case numbering documentation

Tests are no longer grouped by numeric range[1]. Let's stop saying that
and provide some alternative advice for numbering tests.

[1] https://curl.haxx.se/mail/lib-2019-08/0043.html

Closes #4227
This commit is contained in:
Mike Crowe 2019-08-15 16:06:38 +01:00 committed by Daniel Stenberg
parent 0b1e74b6b1
commit a8ac1be705
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2

View File

@ -216,27 +216,12 @@ The curl Test Suite
2.1 Test case numbering 2.1 Test case numbering
1 - 99 HTTP Test cases used to be numbered by category, but the ranges filled
100 - 199 FTP up. Subsets of tests can now be selected by passing keywords to the
200 - 299 FILE runtests.pl script via the make TFLAGS variable.
300 - 399 HTTPS
400 - 499 FTPS
500 - 599 libcurl source code tests, not using the curl command tool
600 - 699 SCP/SFTP
700 - 799 SOCKS4 (even numbers) and SOCK5 (odd numbers)
800 - 849 IMAP
850 - 899 POP3
900 - 999 SMTP
1000 - 1299 miscellaneous
1300 - 1399 unit tests
1400 - 1499 miscellaneous
1500 - 1599 libcurl source code tests, not using the curl command tool
(same as 5xx)
1600 - 1699 unit tests
2000 - x multiple sequential protocols per test case
There's nothing in the system that *requires* us to keep within these number New tests should now be added by finding a free number in
series. tests/data/Makefile.inc.
3. Write tests 3. Write tests