Apart from being undesirable that debugging messages are always written to stdout, the information is redundant as a similar message is logged at debug level. #12681
The default is 'true'. When set 'false', file: and qrc: URLs are treated as invalid (unknown scheme) rather than opening local files, as requested in issue #12752. In order to test this, I added a mechanism to test/run-tests.py allowing individual tests to be annotated with command-line options to pass to phantomjs or the script.
Unfortunately, due to Qt and WebKit limitation, this is technically clearing all the cache used by every web page instance. It is the best we can have right now. #10357
In case Qt doesn't provide the information yet, deduce it from the OS kernel version (e.g. 14.x.y for OS 10.10 Yosemite). #12579
This is available via the new property called `release`. A very simple example to demonstrate it: var system = require('system'); console.log('Kernel release', system.os.release); which will print (on OS X 10.7.5 Lion): Kernel release 11.4.2 #12587
This means you don't have to wait 30 seconds in between invocations of run-tests.py. Also, if the test server fails to bind its port, print the actual OS-level error message rather than guessing what the problem is. issue #12439
* correctly fake a package to hold all the response-hook modules * use StringIO correctly in the response hooks * prevent .py(c) files in test/www/ from being accessed directly * prevent test/www/__init__ from being treated as a response hook * add a test case that makes sure the existing hooks _can_ return 200 OK (issue #12439; buggy commit 4d60e94)