./sky/tools/skydb --debug [url]
(skydb)
prompthelp
to see the list of available commands//out/Debug
./sky/tools/test_sky --debug
//out/Debug
. If you want to run against //out/Release
, omit the --debug
flag.sky/tools/run_sky_httpd
out/Debug/mojo_shell --args-for="mojo:native_viewport_service --use-headless-config" --content-handlers=text/html,mojo:sky_viewer --url-mappings=mojo:window_manager=mojo:sky_tester mojo:window_manager
sky_tester
should print #READY
when readyhttp://127.0.0.1:8000/lowlevel/text.html
, and press the enter keyresources/mocha.html
and resources/chai.html
describe('My pretty test of my subject', function() {
var subject = new MySubject();
it('should be pretty', function() {
assert.ok(subject.isPretty);
});
});
Sky does not have proper pixel tests. Instead we have only reftests. If you want a pixel test, you need to dump the png from a reftest, upload it to googlestorage and then put and pointing to the uploaded file in the reference.
Copying the file to googlestorage: $ sha1sum ../out/Debug/layout-test-results/framework/flights-app-pixels-actual.png db0508cdfe69e996a93464050dc383f6480f1283 ../out/Debug/layout-test-results/framework/flights-app-pixels-actual.png $ gsutil.py cp ../out/Debug/layout-test-results/framework/flights-app-pixels-actual.png gs://mojo/sky-pngs/db0508cdfe69e996a93464050dc383f6480f1283
Long-term, we should not have these tests at all and should just dump paint commands. In the short-term, if we find we're doing this a lot we should obviously automate this process, e.g. test_sky could do all of this work, including spitting out the correct reference file.