Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
36c621c9
Commit
36c621c9
authored
24 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
more details on debugging with the test suite
parent
1717963e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tests/README
+14
-5
14 additions, 5 deletions
tests/README
with
14 additions
and
5 deletions
tests/README
+
14
−
5
View file @
36c621c9
...
...
@@ -7,7 +7,7 @@
The cURL Test Suite
Requires:
perl
perl
(and a unix-style shell)
Run:
'make test'. This invokes the 'runtests.pl' perl script. Edit the top
...
...
@@ -15,7 +15,8 @@ Run:
The script breaks on the first test that doesn't do OK. Use -a to prevent
the script to abort on the first error. Run the script with -v for more
verbose output.
verbose output. Use -d to run the test servers with debug output enabled as
well.
Use -s fort shorter output, or pass a string with test numbers to run
specific tests only (like ./runtests.pl "3 4" to test 3 and 4 only)
...
...
@@ -33,9 +34,17 @@ Debug:
then just type 'run' in the debugger to perform the command through the
debugger.
If a test case causes a core dump, analyze it by running gdb like:
# gdb ../curl/src core
... and get a stack trace with the gdb command:
(gdb) where
Logs:
All logs are generated in the logs/ subdirctory (it is emtpied first
in the runtests.
sh
script)
in the runtests.
pl
script)
Data:
All test-data are put in the data/ subdirctory.
...
...
@@ -70,7 +79,7 @@ Data:
of the ftp server. It uses a simple syntax that is left to
describe here!
FIX
:
TODO
:
* Make httpserver.pl work when we PUT without Content-Length:
* Add persistant connection support and test cases
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment