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)
Thu, Mar 28, 12:28 PM
Unknown Object (File)
Mar 7 2024, 6:03 PM
Unknown Object (File)
Feb 11 2024, 8:01 AM
Unknown Object (File)
Dec 23 2023, 1:13 AM
Unknown Object (File)
Dec 22 2023, 11:03 PM
Unknown Object (File)
Dec 21 2023, 11:49 AM
Unknown Object (File)
Dec 12 2023, 10:03 AM
Unknown Object (File)
Oct 30 2023, 6:04 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
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Macro stlgtm:

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

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

63

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