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
27c282a6
Commit
27c282a6
authored
16 years ago
by
Dan Fandrich
Browse files
Options
Downloads
Patches
Plain Diff
Mention that the test harness can't check every possible feature.
parent
53732895
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/runtests.1
+8
-4
8 additions, 4 deletions
tests/runtests.1
with
8 additions
and
4 deletions
tests/runtests.1
+
8
−
4
View file @
27c282a6
...
...
@@ -87,10 +87,14 @@ Many tests have conditions that must be met before the test case can run
fine. They could depend on built-in features in libcurl or features present in
the operating system or even in third-party libraries that curl may or may not
use.
The test script checks this by itself, why it is safe to attempt to run all
tests. They who cannot be run due to failed requirements, will simply be
skipped and you'll get a report about it when all test cases have completed.
.P
The test script checks most of these by itself to determine when it is
safe to attempt to run each test. Those which cannot be run due to
failed requirements will simply be skipped and listed at the completion
of all test cases. In some unusual configurations, the test script
cannot make the correct determination for all tests. In these cases,
the problematic tests can be skipped using the "!keyword" skip feature
documented earlier.
.SH "WRITING TESTS"
The simplest way to write test cases is to start with a similar existing test,
save it with a new number and then adjust it to fit. There's an attempt to
...
...
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