-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
2.8.9, 2.9.4, 3.0.2
-
MOODLE_28_STABLE, MOODLE_29_STABLE, MOODLE_30_STABLE
-
Currently, when there is a debugging message emitted during a test, the debugging message is printed to the screen and then a separate message is sent via trigger_error to fail the test. The debugging message(s) should be included with the message for trigger_error as it helps with several things:
- Debugging messages are no longer printed in the PHPUnit progress bar (at least if it happens during a test).
- The debugging message is actually associated to the test in the PHPUnit report. This works for the text format or for JUnit format which is used on CI. Without this, you cannot tell which debugging message goes with which test and you must look at the logs for the message itself. This helps a lot with CI builds.
- duplicates
-
MDL-56354 Fail on debugging output anywhere in a test chain backtrace and include it in the failure report
-
- Closed
-