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
cefc8ba9
Commit
cefc8ba9
authored
21 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
CURLDEBUG is the symbol now
parent
d0bd644e
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
+3
-3
3 additions, 3 deletions
tests/README
with
3 additions
and
3 deletions
tests/README
+
3
−
3
View file @
cefc8ba9
...
...
@@ -27,7 +27,7 @@ Run:
Memory:
The test script will check that all allocated memory is freed properly IF
curl has been built with the
MALLOC
DEBUG define set. The script will
curl has been built with the
CURL
DEBUG define set. The script will
automatically detect if that is the case, and it will use the ../memanalyze
script to analyze the memory debugging output.
...
...
@@ -52,7 +52,7 @@ Logs:
to be kept after the test run.
Data:
All test
-data
are put in the data/ subdirctory. Each test is stored in the
All test
cases
are put in the data/ subdirctory. Each test is stored in the
file named according to the test number.
The test case file format is simply a way to store different sections within
...
...
@@ -72,7 +72,7 @@ TEST CASE NUMBERS
500 - 599 libcurl source code tests, not using the curl command tool
Since 30-apr-2003, there's nothing in the system that requires us to keep
within these number series. Each test case now specif
y their
own server
within these number series. Each test case now specif
ies its
own server
requirements, independent of test number.
TODO:
...
...
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