Vasileios Karakasis

This is wrong, as the test's `time_limit` should override any time limit set at the partition level. The workaround is to pass `-S [test.]time_limit=` to set it explicitly.

Now we have plenty of places where commands from either the configuration or the test are emitted and we need special [tricks]() to generate multiple steps. It would be better...

It only shows the system and not the partition's name. ```bash ./bin/reframe -c unittests/resources/checks/frontend_checks.py -n ^PerformanceFailureCheck -r ``` In failure info: ```console * System partition: generic ``` Instead of showing...

We should also add a tip that if you are writing a library it's a wise idea to properly make the names unique by following a pattern `__`. This will...

If the `descr` field is set properly in the test, this will give more insight as of what the test's purpose is. CC: @gppezzi

Currently, only a single aggregation is supported, meaning that to obtain the three currently available stats (min, max, mean), users have to run the `--list-stored-testcases` three times. This is inefficient...

Currently, references are indexed by the system and/or partition name. This is insufficient as many times the references do not depend on the system partition per se, but rather partition...

The `RegressionMixin` is used for extending the functionality of existing tests, thus the more accurate name of "plugin". The plan is for 4.9 to deprecate the `RegressionMixin` name in favor...

Although when the updated logging was introduced in 4.0 we thought that this would be sort of "compatibility" mode, I think it's still valid and widely used. Therefore, I suggest...