noVNC/tests
Pierre Ossman 18e96092c3 Flush out rendering after each performance test
There might be operations pending in the render queue. Make sure
these are fully handled before we consider the test run over.
2016-12-09 09:20:39 +01:00
..
assertions.js Fix 'sent' assertion 2016-06-03 16:31:29 +02:00
fake.websocket.js Use Typed Arrays for the send queue 2015-08-06 14:47:03 -04:00
input.html New way of detecting touch 2016-10-14 02:41:06 +02:00
playback.js Flush out rendering after each performance test 2016-12-09 09:20:39 +01:00
run_from_console.casper.js Switch to PhantomJS 2.x for testing 2016-09-16 15:49:52 -04:00
run_from_console.js Switch to PhantomJS 2.x for testing 2016-09-16 15:49:52 -04:00
run_from_console.zombie.js Support Skipped Tests and Fix JSHint Issues 2013-12-17 17:56:18 -05:00
test.base64.js Cleanup and Test: base64.js 2014-09-15 16:46:02 -04:00
test.display.js Wait for proper image load event 2016-10-24 14:42:13 +02:00
test.helper.js Move input-related files into core/input 2016-09-16 15:49:52 -04:00
test.keyboard.js Move input-related files into core/input 2016-09-16 15:49:52 -04:00
test.rfb.js Process entire WebSocket message at once 2016-10-24 14:42:08 +02:00
test.util.js Util shouldn't modify window object 2016-09-16 15:49:52 -04:00
test.websock.js Fix failing test 2016-04-30 02:28:45 +02:00
vnc_perf.html Fix performance tests to follow new state API 2016-10-24 17:41:20 +02:00
vnc_playback.html Fix performance tests to follow new state API 2016-10-24 17:41:20 +02:00