summaryrefslogtreecommitdiffstats
path: root/tools/regression/lib/libc/string
Commit message (Collapse)AuthorAgeFilesLines
* Integrate tools/regression/lib/libc/string into the FreeBSD test suitengie2015-11-086-436/+0
| | | | | | | as lib/libc/tests/string MFC after: 1 week Sponsored by: EMC / Isilon Storage Division
* Make the strerror tests work without libtap.jmmv2014-03-122-34/+42
| | | | | | Just replace the simple calls to the library with ad-hoc code. We should later rewrite these with the ATF libraries anyway, which are part of the base system.
* Allow strerror(0) and strerror_r(0, ...).jilles2011-04-051-8/+13
| | | | | | | | | | | | | Of course, strerror_r() may still fail with ERANGE. Although the POSIX specification said this could fail with EINVAL and doing this likely indicates invalid use of errno, most other implementations permitted it, various POSIX testsuites require it to work (matching the older sys_errlist array) and apparently some applications depend on it. PR: standards/151316 MFC after: 1 week
* Tests for wcscasecmp(), wcsnlen(), and stpncpy().das2009-02-284-1/+269
|
* Add to CFLAGS, rather than overriding it. Use LDFLAGS for the -L option,nik2005-02-011-2/+3
| | | | | | and LDLIBS to specify -ltap. Submitted by: ru
* Link against libtap (ports/devel/libtap). Replace the calls to assert()nik2005-02-012-31/+32
| | | | | with calls to libtap::ok1(), and make sure the correct number of tests is planned for, and that the exit code is correct.
* Switch over to a different, more flexible test output protocol that'snik2004-11-112-2/+14
| | | | | | | | | | | | | | | | | | | | understood by Perl's Test::Harness module and prove(1) commands. Update README to describe the new protocol. The work's broken down into two main sets of changes. First, update the existing test programs (shell scripts and C programs) to produce output in the ok/not ok format, and to, where possible, also produce a header describing the number of tests that are expected to be run. Second, provide the .t files that actually run the tests. In some cases these are copies of, or very similar too, scripts that already existed. I've kept the old scripts around so that it's possible to verify that behaviour under this new system (in terms of whether or not a test fails) is identical to the behaviour under the old system. Add a TODO file.
* Add regression test for strerror()/strerror_r().mike2002-12-182-0/+141
Based on: src/lib/libc/string/strerror.c (rev 1.8)
OpenPOWER on IntegriCloud