| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | tests: Automatically deduce the tool name from the test case for unit tests | Steve Holme | 2020-02-27 | 1 | -4/+0 |
| | | | | | | | | | | | | | It is still possible to override the executable to run during the test, using the <tool> tag, but this patch removes the requirement that the tag must be present for unit tests. It also removes the possibility of human error when existing test cases are used as the basis for new tests, as recently witnessed in 81c37124. Reviewed-by: Daniel Stenberg Closes #4976 | ||||
| * | unittests: a dedicated feature in tests | Daniel Stenberg | 2011-01-03 | 1 | -8/+4 |
| | | | | | | | The test runner script now knows if unittests can run and the unit test setup file says it is one. I also made runtests.pl deal with no <command> tag set, so that the description file can get even simpler. | ||||
| * | unittest: framework for unit-testing | Daniel Stenberg | 2011-01-03 | 1 | -0/+30 |
| This is the first approach at doing fairly clean and easy to write and debug unit tests. | |||||
 |
index : delta/curl.git | |
| github.com: bagder/curl.git |
| summaryrefslogtreecommitdiff |