Right now selenium test output is very messy and almost entirely pointless. Let's shrink the noise so people focus on the results.
I have indeed made Quibble to relay the PHP embedded web server to info. just elevate it to debug and we should be fine +1!
We will probably later need a way to finely tune the logging config from the CLI or via a config file.
The reason I have made it to relay everything at info level is that the PHP built-in server writes access log as well as potential errors solely on stderr without any way to set a minimal log level. If we relay to debug we would miss the webserver errors, then they are probably available via the mw-debug-www.log error log.
I thought about parsing the emitted messages to filter out access log, but that sounds too fragile. Maybe we can just spawn the builtin server with error_log set.