unrelated deprecation warning for --assert

[staabm]

Q	A
OS	macOS 26.7
Shell & version	sh 2.0 / bash 3.0 / ...
bashunit version	50.1

Summary

I guess the deprecation warning is not expected

Current behavior

since I did not run bashunit test --assert I don't expect a deprecation warning telling me I shouldn't use it and it is deprecated

How to reproduce

$ bashunit -a not_contains 'Bar.php' "Baarar" 
Deprecated: `bashunit test --assert`. Use `bashunit assert` instead.

Expected behavior

no warning?

alternatively

$ bashunit -a not_contains 'Bar.php' "Baarar" 
Deprecated: `bashunit -a`. Use `bashunit assert` instead.

[Chemaclass]

Hi! Actually the warning is correct. The bashunit test --assert|-a was deprecated in favor of bashunit assert

Reasoning: theoptions flags where growing and did not make sense to have them under the test command. Therefore, I split the commands into their own context independent from the default test command.

See more: https://bashunit.com/command-line#assert

[staabm]

I am fine with the deprecation itself. what is confusing is, that I did not invoke bashunit test --assert|-a but the bashunit -a and the error message talks about a command I did not use :)

[Chemaclass]

You're right, and it's fixed in #1367.

The warning came from the -a | --assert branch of the test command parser and hardcoded bashunit test --assert, while bashunit -a gets there through the implicitly inferred test subcommand. So it named a command you never ran. It now quotes back what you typed: bashunit -a, bashunit --assert or bashunit test --assert.

The deprecation itself stays, for the reason above. It ships in the next release.

[staabm]

thank you!