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)
Dec 3 2024, 11:30 PM
Unknown Object (File)
Nov 21 2024, 6:43 AM
Unknown Object (File)
Oct 19 2024, 5:21 AM
Unknown Object (File)
Oct 5 2024, 1:58 PM
Unknown Object (File)
Oct 5 2024, 5:44 AM
Unknown Object (File)
Oct 4 2024, 7:07 PM
Unknown Object (File)
Oct 3 2024, 12:07 AM
Unknown Object (File)
Oct 2 2024, 10:14 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