Page MenuHomeFreeBSD

du: tests: make H_flag tests more strict about output requirements
ClosedPublic

Authored by kevans on Jan 5 2021, 10:13 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jul 10, 10:22 AM
Unknown Object (File)
Sun, Jul 5, 10:27 AM
Unknown Object (File)
Sun, Jul 5, 10:27 AM
Unknown Object (File)
Sat, Jul 4, 3:00 AM
Unknown Object (File)
Fri, Jul 3, 11:41 PM
Unknown Object (File)
Thu, Jul 2, 9:16 PM
Unknown Object (File)
Thu, Jul 2, 2:52 AM
Unknown Object (File)
Wed, Jul 1, 11:55 PM
Subscribers

Details

Summary

The current version of this test will effectively pass as long as one of the
specified paths is in the output, and it could even be a subset of one of
the paths.

Strengthen up the test a little bit:

  • Specify beginning/end anchors for each path
  • Add egrep -v checks to make sure we don't have any *additional* paths
  • Ratchet down paths2 to exactly the two paths we expect to appear

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 35959
Build 32848: arc lint + arc unit

Event Timeline

Macro stlgtm:

usr.bin/du/tests/du_test.sh
57

Could you please add a comment here noting why this check exists?

60

Could you please add a comment here noting why this check exists?

This revision is now accepted and ready to land.Jan 6 2021, 5:08 PM