Extension:MWUnit/Risky and skipped tests

MWUnit performs additional checks when it performs tests. These checks ensure the validity of the tests and inform the user about possibly invalid tests or misconfigurations.

Useless tests
By default, MWUnit is strict about tests that do not perform any assertions. A test that does not perform any assertions will be marked as risky.

Invalid context
MWUnit is always strict about tests using an invalid context annotation. The context annotation must either be empty, "canonical" or "user". A test that has an invalid context annotation will be marked as risky.

Invalid assertions
MWUnit is always strict about tests with invalid assertions. An assertion is invalid when it contains too few parameters, or parameters of an incorrect type. A test that has one or more invalid assertions will be marked as risky.

A test will not be marked as invalid when an assertion has too many parameters.

Invalid annotation
MWUnit can be configured, through the  configuration parameter, to be strict about invalid/untruthful   annotations. When enabled, a test will be marked as risky if the template a test  is not used directly, or indirectly, in a test case.

Mocked covers template
A test will be marked as risky when the template that test should cover is mocked.

Missing permissions for user mock
A test will be marked as risky when it is required to be run as another user, but running tests as another user is disabled or disallowed.