jquery/test/karma.debug.html
Michał Gołębiowski-Owczarek 8cf39b78e6
Tests: Fix the link to QUnit CSS file
Without this fix, the layout is fine during the test run but all the CSS is gone
when tests finish and the results are shown.

This affects commands like `grunt karma:chrome-debug`.

Closes gh-5090
2022-08-29 17:44:10 +02:00

47 lines
1.5 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/external/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>
// QUnit.config is populated from QUnit.urlParams but only at the beginning
// of the test run. We need to read both.
var esmodules = QUnit.config.esmodules || QUnit.urlParams.esmodules,
amd = QUnit.config.amd || QUnit.urlParams.amd;
// Workaround: Remove call to `window.__karma__.loaded()`
// in favor of calling `window.__karma__.start()` from `loadTests()`
// because tests such as unit/ready.js should run after document ready.
if ( !esmodules && !amd ) {
loadTests();
}
</script>
</body>
</html>