You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #105 there is no user output (echo or var_dump()) forwarded to the online editor results. There is no test for that, so it wasn't catched in advance.
Add a test for user output
Make it possible again to have the output in the results
I also got that feedback from a collegue on CLI. Maybe PHPUnit needs to be configured accordingly?
The text was updated successfully, but these errors were encountered:
The problem is not present for students using the CLI. Nothing changed for them.
PHPUnit decided to remove <system-out> from JUnit for PHPUnit V10+. There is no replacement.
It is not possible to suppress all PHPUnit output and let user output shown up. The reason is, that PHPUnit captures all output and controls showing it with its own output creation.
It is possible to mark tests, that produce output, as failed (--disallow-test-output --fail-on-risky).
JUnit log file doesn't contain these as failed: <testsuite name="HelloWorldTest" [...] tests="1" assertions="1" errors="0" failures="0" skipped="0" time="0.007922">
Teamcity log file does contain these tests, but the file must be parsed additionally (| is escape char): ##teamcity[testFailed name='testHelloWorld' message='This test printed output: My |'User üâ|||| output|'|n\Some backslash|nobject(stdClass)#79 (0) {|n}|n' details='' duration='6' flowId='6893']
Conclusion:
Write additional Teamcity log file during test run
Add Teamcity log file parsing to junit-handler
Provide user output from Teamcity log file in JSON result file as expected for V3
Since #105 there is no user output (
echo
orvar_dump()
) forwarded to the online editor results. There is no test for that, so it wasn't catched in advance.I also got that feedback from a collegue on CLI. Maybe PHPUnit needs to be configured accordingly?
The text was updated successfully, but these errors were encountered: