jquery/test/karma.debug.html
Michał Gołębiowski-Owczarek d7e64190ef
Build: Remove the external directory, read from node_modules directly
Now that Sizzle is gone & we use npm, we can read from node_modules directly
and skip the setup that copies some files to the external directory.

Closes gh-4466
2019-08-26 18:53:54 +02:00

48 lines
1.6 KiB
HTML

<!DOCTYPE html>
<html lang="en" id="html">
<head>
%X_UA_COMPATIBLE%
<title>DEBUG</title>
<meta charset="utf-8">
<!-- Karma serves this page from /context.html. Other files are served from /base -->
<link rel="stylesheet" href="/base/node_modules/qunit/qunit/qunit.css" />
<link rel="stylesheet" href="/base/test/data/testsuite.css" />
</head>
<body id="body">
<div id="qunit"></div>
<!-- Start: jQuery Test HTML -->
<!-- this iframe is outside the #qunit-fixture so it won't waste time by constantly reloading; the tests are "safe" and clean up after themselves -->
<iframe id="loadediframe" name="loadediframe" style="display:none;" src="/base/test/data/iframe.html"></iframe>
<div id="qunit-fixture"></div>
<!-- End: jQuery Test HTML -->
<!-- Start: Karma boilerplate -->
<script src="/context.js"></script>
<script src="/debug.js"></script>
<script>
%CLIENT_CONFIG%
%MAPPINGS%
</script>
%SCRIPTS%
<!-- End: Karma boilerplate -->
<script src="/base/test/data/qunit-fixture.js"></script>
<script>
// Workaround: Remove call to window.__karma__.loaded()
// in favour of calling window.__karma__.start() at window.onload
// because tests such as unit/ready.js should run after document ready
window.addEventListener('load', function() {
window.__karma__.start();
// Workaround: https://github.com/karma-runner/karma-qunit/issues/92
QUnit.testStart(function () {
// Restore content
document.getElementById("qunit-fixture").innerHTML = QUnit.config.fixture;
});
});
</script>
</body>
</html>