Test suite cleanup and Test Coverage

[nashif]

Reported by Anas Nashif:

Over time we have been adding tests and adapting existing tests using different methods for running the tests and reporting test results.

Here is a summary of what needs to be done to get to a consistent and unified testsuite with clean output that is easy to parse for humans and scripts:

• Review all tests and categorise them correctly

• Review all tests and apply Zephyr code style on them Remove CamelCase Start tests consistently (we still have remnants of MDEF way of starting tests)

• Convert all tests to use ztest where possible

• Review ztest and enhance it to support existing tests and improve test result reporting

• Provide a parseable output that can be consumed by scripts

• Reduce debug output and make it configurable, i.e. do not print out to console by default, in case of failure and when reproducing failures make it possible to print more output.

• Increase coverage of supported features. We have many untested features.

• [x] GH-2281: Fix coding style issues with test cases

• [x] GH-1662: cleanup ztest output and make it more readable

(Imported from Jira ZEP-2249)

[nashif]

by punit vara:

Anas Nashif When you say review test cases , do you mean samples as well as tests directory ?

[nashif]

by Anas Nashif:

i mean tests/*, samples/ are not considered testcases.

[nashif]

Related to ZEP-2449