Hi Tom,
On Wed, 22 Jan 2025 at 10:24, Tom Rini trini@konsulko.com wrote:
On Mon, Jan 20, 2025 at 02:25:22PM -0700, Simon Glass wrote:
The current method of running unit tests relies on subcommands of the ut command. Only the code in each subcommand knows how to find the tests related to that subcomand.
This is not ideal and we now have quite a few subcommands which do nothing but locate the relevant tests in a linker list, then call a common function to run them.
This series adds a list of test suites, so that these subcommands can be removed.
An issue with 'ut all' is that it doesn't record how many tests failed overall, so it is necessary to examine copious amounts of output to look for failures. This series adds a new 'total' feature allow recording the total number of failed tests.
To help with 'ut all' a new pytest is created which runs it (as well as 'ut info') and makes sure that all is well. Due to the 'ut all' failures this does not pass, so the test is disabled for now. It is here because it provides security against misnaming a test suite and causing it not to run.
This is a size reduction when the tests are enabled (and so seen on a few in-tree configs), nice work.
Thanks.
Regards, Simon