[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Running bash tests
From: |
Dennis Orlando |
Subject: |
Running bash tests |
Date: |
Thu, 10 Oct 2024 15:05:23 +0200 |
Hi,
I'm working on an SSH honeypot fingerprinting project and I wanted to run
the test suite of `bash` against such honeypot system (which is eulating
bash), in order to spot different behaviors and potential fingerprinting
artifacts.
I'm currently trying to figure out how the test scripts located in the main
repository work.
...However, I can't seem to figure it out 😅
Executing the `run-all` script in "tests" after compiling with `make`
produces a ton of unintuitive output. There sure must be a better way to
run all the tests, right? Did I miss something?
warning: please do not consider output differing only in the amount of
warning: white space to be an error.
run-redir
warning: the text of a system error message may vary between systems and
warning: produce diff output.
warning: if the text of an error message concerning `redir1.*' not being
warning: found or messages concerning bad file descriptors produce diff
warning: output, please do not consider it a test failure
155,156d154
< redir11 bad 1
< redir11 bad 2
159,160d156
< redir11 bad 7
< redir11 bad 8
run-rhs-exp
run-rsh
run-set-e
run-set-x
run-shopt
run-strip
run-test
run-tilde
run-tilde2
run-trap
warning: UNIX versions number signals and schedule processes differently.
warning: If output differing only in line numbers is produced, please
warning: do not consider this a test failure.
run-type
run-varenv
warning: some of these tests will fail if arrays have not
warning: been compiled into the shell
run-vredir
warning: the text of a system error message may vary between systems and
warning: produce diff output.
14,16d13
< bad foo 1
< bad foo 2
< bad foo 3
Have a nice day! :)
Dennis O.
- Running bash tests,
Dennis Orlando <=