fune/dom/websocket/tests/test_websocket1.html
Brian Grinstead 0d460e3432 Bug 1544322 - Part 2.2 - Remove the [type] attribute for one-liner <script> tags loading files in /tests/SimpleTest/ in dom/ r=bzbarsky
This is split from the previous changeset since if we include dom/ the file size is too
large for phabricator to handle.

This is an autogenerated commit to handle scripts loading mochitest harness files, in
the simple case where the script src is on the same line as the tag.

This was generated with https://bug1544322.bmoattachments.org/attachment.cgi?id=9058170
using the `--part 2` argument.

Differential Revision: https://phabricator.services.mozilla.com/D27457

--HG--
extra : moz-landing-system : lando
2019-04-16 03:53:28 +00:00

42 lines
1.5 KiB
HTML

<!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8"></meta>
<title>WebSocket test</title>
<script src="/tests/SimpleTest/SimpleTest.js"></script>
<script type="text/javascript" src="websocket_helpers.js"></script>
<script type="text/javascript" src="websocket_tests.js"></script>
<link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css" />
</head>
<body onload="testWebSocket()">
<script class="testbody" type="text/javascript">
var tests = [
test1, // client tries to connect to a http scheme location;
test2, // assure serialization of the connections;
test3, // client tries to connect to an non-existent ws server;
test4, // client tries to connect using a relative url;
test5, // client uses an invalid protocol value;
test6, // counter and encoding check;
test7, // onmessage event origin property check
test8, // client calls close() and the server sends the close frame (with no
// code or reason) in acknowledgement;
test9, // client closes the connection before the ws connection is established;
test10, // client sends a message before the ws connection is established;
];
function testWebSocket() {
doTest();
}
SimpleTest.requestFlakyTimeout("The web socket tests are really fragile, but avoiding timeouts might be hard, since it's testing stuff on the network. " +
"Expect all sorts of flakiness in this test...");
SimpleTest.waitForExplicitFinish();
</script>
<div id="feedback">
</div>
</body>
</html>