summaryrefslogtreecommitdiff
path: root/tests/usr.bin/printf
AgeCommit message (Collapse)Author
2022-05-24fix various typos in comment, documentation and log messages.andvar
2021-05-19With the (very) recent changes to printf(1), a numeric conversion from datakre
of the form '+1 (two (or more) characters after the quote) will now generate an error message, and cause printf(1) to exit(1) when it is done. Adapt the test cases which use that data form to handle that.
2021-05-19Fix a truly embarrassing quoting screwup. There is an explanation askre
to why this didn't cause any failures, but I won't go into it here. This was detected by the about to be committed printf changes. While here also correct a couple of minor comment layout issues.
2020-04-24ATF runs shell script tests with "sh -e" (WHY???)kre
Compensate for that by adding an explicit test to a command so -e will not kill the shell when the command (expectedly) fails. Previously this was saved by /bin/sh disabling -e in command subs.
2019-11-12Add a missing ("quoting") '>' in an atf_fail error message string.kre
Since the tests don't (usually) fail no-one ever noticed the missing char. That is, the "received this" and "expected this" strings were supposed to appear in the output err message as "<<string>>" but one of those closing '>' chars was missing. No-one should ever notice this change in normal operation, as the tests are not intended to fail.
2019-07-21Stop assuming that printf handles options in any way at allkre
(it doesn't - that is, shouldn't) which includes processing -- as an "end of options". The first arg is (always) the format string. Remove/fix tests that assumed the contrary. Problem (with printf) pointed out on tech-userlevel by Thierry Laronde.
2019-07-21Correct a typo. It is atf_require_prog not atf_require_pfog ...kre
2018-09-14Move the tests of character value args to floating conversionskre
out of the %e test and into the NetBSD specific tests, while POSIX once (apparently) required (or seemed to require) support for that, it no longer does (and character value args to float conversions do not make much sense - char valuse are always integers). When char conversions are supported, test that \' (or \" ) (that is, no character following the quote) works as an arg (should result in zero, as there's a \0 in the arg after the quote char). Add some big/small number %g conversion tests.
2018-09-14When the shell being tested for builtin printf supports "type -t"kre
use it to test if printf is built in, it is must more reliable that guessing at the output format and message of "type" (without -t).
2018-09-10Add a test where printf is run twice in the same shell, and thekre
first invocation uses \c in a %b arg - make sure that 2nd invocation is not affected by that (it was until recently, for a very long time).
2018-09-08Make sure we're in the standard locale when testing for printfkre
being built in to the shell, so we don't receive an unrecognisable (to the script) message from the shell when we ask it.
2018-09-05Add ATF tests for printf(1)kre
Two new test programs, one for the version of printf in /bin/sh and one for the command /usr/bin/printf (t_builtin and t_command) Each test program has 28 test cases (the same in each) of which currently 27 pass, and 1 is skipped. See the test scripts themselves for more information.