summaryrefslogtreecommitdiffstats
path: root/tests.sh
Commit message (Collapse)AuthorAgeFilesLines
* tests: Add some tests that require sudoTavian Barnes2019-04-241-13/+77
|
* tests: Redirect stdin from /dev/nullTavian Barnes2019-04-241-0/+3
|
* tests: Use more colorsTavian Barnes2019-04-241-32/+39
|
* parse: Allow things like -uid ++10Tavian Barnes2019-04-211-0/+20
| | | | GNU find does too.
* tests: Fix --bfs=pathTavian Barnes2019-04-211-10/+10
|
* tests: Don't test symlink permissionsTavian Barnes2019-04-201-1/+1
| | | | They're different between platforms.
* tests: Add a test with -printf %H and multiple rootsTavian Barnes2019-04-201-0/+5
| | | | To make sure we're keeping track of different root paths correctly
* tests: Refuse to run as rootTavian Barnes2019-04-181-256/+267
| | | | | Suggested by Chris Lamb here: https://salsa.debian.org/lamby/pkg-bfs/commit/b173efb35da126adb39b0984219d6a2fd9ff428f#note_74877
* tests: Fix color NUL byte test on platforms where sort expects textTavian Barnes2019-03-281-1/+17
|
* color: Implement ln=targetTavian Barnes2019-03-281-0/+5
| | | | | With ln=target in LS_COLORS, links should be colored according to their target's stat() info, not their own.
* color: Implement escape sequence parsingTavian Barnes2019-03-281-0/+10
| | | | | GNU ls allows custom escape sequences inside color values, including control characters and embedded NULs.
* opt: Optimize redundant comma expressionsTavian Barnes2019-03-211-2/+14
|
* tests: Respond to terminal resizesTavian Barnes2019-03-211-3/+9
|
* tests: Make the output more colorful and nicerTavian Barnes2019-03-201-18/+16
|
* opt: Replace -a -false/-o -true with -not when possibleTavian Barnes2019-03-201-0/+7
|
* tests: Add utilities for comparing colors to lsTavian Barnes2019-03-191-1/+1
|
* tests: Use archive extensions for color testsTavian Barnes2019-03-171-2/+3
|
* color: Match the behaviour of GNU ls more closelyTavian Barnes2019-03-171-3/+58
|
* tests: Add a test for extension overridesTavian Barnes2019-03-071-0/+10
|
* eval: Fix -unique with -depthTavian Barnes2019-03-071-0/+10
|
* Implement -uniqueTavian Barnes2019-03-011-0/+16
| | | | Closes #48
* tests: Add a test for symlink coloring to a deviceTavian Barnes2019-02-181-1/+6
|
* tests: Add tests for -no{group,user} under fd pressureTavian Barnes2019-02-071-0/+16
|
* tests: New utility for making and testing socket filesTavian Barnes2019-02-011-11/+11
|
* main: Fix closed standard stream handlingTavian Barnes2019-02-011-0/+29
| | | | | bfs >&- should complain about a missing file descriptor, rather than silently succeeding.
* tests: Fail if bfs failsTavian Barnes2019-01-311-3/+17
| | | | | For tests that expect bfs to fail, the return value disambiguates whether bfs itself failed or whether the output was unexpected.
* posix1e: Split out ACL and capability handling from utilTavian Barnes2019-01-021-3/+3
|
* color: Fix more incompatibilities with GNU lsTavian Barnes2019-01-021-4/+79
|
* tests: Fix test_exit() to not depend on breadth-first orderingTavian Barnes2018-12-281-1/+1
|
* tests.sh: Add a --help with usage informationTavian Barnes2018-12-171-1/+36
|
* exec: Reject -exec \; without a commandTavian Barnes2018-11-141-1/+15
| | | | | | | | | | | Prior to this, we'd fork and then segfault on every file as NULL was passed to execvpe(). Found while looking through old FreeBSD find bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=36521 bfs still supports the (dubious, possibly unintentional?) GNU find extension to POSIX that allows $ bfs -exec {} \;
* tests: Don't assume BSD find has the "implicit ."Tavian Barnes2018-11-141-3/+2
| | | | Also, FreeBSD find rejects -L -delete, so don't test it under --bsd.
* tests: Don't assume find continues after filesystem loopsTavian Barnes2018-11-141-13/+45
| | | | | | | | | | | POSIX says > When it detects an infinite loop, find shall write a diagnostic > message to standard error and shall either recover its position in the > hierarchy or terminate. So make the 'links' folder not have any loops, and add a new 'loops' folder for testing the GNU/bfs behaviour.
* tests: Make the weird names tests POSIX-compliantTavian Barnes2018-11-011-6/+6
|
* tests: Add testcases for -pruneTavian Barnes2018-11-011-0/+16
|
* tests: Sort test listsTavian Barnes2018-09-271-159/+292
|
* tests: Move test for -H -newer out of POSIXTavian Barnes2018-09-271-1/+2
| | | | | The POSIX spec implies that -newer is actually not supposed to respect -H/-L. But all implementations I know about do anyway.
* tests: Remove non-POSIX features from POSIX testsTavian Barnes2018-09-261-13/+21
| | | | Credit to http://core.suckless.org/sbase/ for identifying these.
* Update some more copyright datesTavian Barnes2018-09-261-1/+1
|
* spawn: New posix_spawn()-like API for execTavian Barnes2018-09-181-9/+0
|
* opt: Re-run optimizations after reordering expressionsTavian Barnes2018-08-181-1/+11
| | | | | This catches new data flow inferences that can be made after swapping the children of an expression.
* printf: Support %B, GNU find's undocumented birth time specifierTavian Barnes2018-07-241-2/+2
|
* tests: Add tests for mode 000Tavian Barnes2018-07-201-0/+21
|
* printf: Output ? for errors in %YTavian Barnes2018-07-201-0/+16
|
* eval: Fix -delete when following symlinks.Tavian Barnes2018-07-121-0/+14
| | | | | Same bug as https://savannah.gnu.org/bugs/?46305. Please don't ever do this though.
* tests: Add some more tests for broken symlinksTavian Barnes2018-07-071-0/+45
|
* tests: Use -maxdepth 0 instead of | head -n1Tavian Barnes2018-07-071-1/+1
| | | | | | | This avoids the potential for "broken pipe" errors observed on some systems, e.g. http://build.alpinelinux.org/buildlogs/build-edge-s390x/testing/bfs/bfs-1.2.2-r0.log
* tests: Relax test_depth_errorTavian Barnes2018-06-241-3/+0
| | | | | Whether bfs can return children of a directory without search permission depends on whether d_type is filled in, which can't be guaranteed.
* tests: New test for -depth in the presence of read errorsTavian Barnes2018-06-231-0/+18
|
* tests: Work around broken rm in cleanupTavian Barnes2018-03-181-0/+7
| | | | | | | BusyBox rm, for example, doesn't handle long paths properly, so give it some help. C.f. http://lists.busybox.net/pipermail/busybox/2018-March/086302.html