mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-27 18:17:22 +02:00
ec0838b84e
And here's the wild part: instead of cloning WPT tests, import the relevant WPT tests that this fixes into our own test suite. This works by adding a small Ladybird-specific callback in resources/testharnessreport.js (which is what that file is meant for!) Note that these run as text tests, and so they must signal the runner when they are done. Tests using the "usual" WPT harness should just work, but tests that do something more freestyle will need manual signaling if they are to be imported. I've also increased the test timeout here from 30 to 60 seconds, to accommodate the larger WPT-style tests.
46 lines
1.7 KiB
JavaScript
46 lines
1.7 KiB
JavaScript
/* global add_completion_callback */
|
|
/* global setup */
|
|
|
|
/*
|
|
* This file is intended for vendors to implement code needed to integrate
|
|
* testharness.js tests with their own test systems.
|
|
*
|
|
* Typically test system integration will attach callbacks when each test has
|
|
* run, using add_result_callback(callback(test)), or when the whole test file
|
|
* has completed, using
|
|
* add_completion_callback(callback(tests, harness_status)).
|
|
*
|
|
* For more documentation about the callback functions and the
|
|
* parameters they are called with see testharness.js
|
|
*/
|
|
|
|
/* If the parent window has a testharness_properties object,
|
|
* we use this to provide the test settings. This is used by the
|
|
* default in-browser runner to configure the timeout and the
|
|
* rendering of results
|
|
*/
|
|
try {
|
|
if (window.opener && "testharness_properties" in window.opener) {
|
|
/* If we pass the testharness_properties object as-is here without
|
|
* JSON stringifying and reparsing it, IE fails & emits the message
|
|
* "Could not complete the operation due to error 80700019".
|
|
*/
|
|
setup(JSON.parse(JSON.stringify(window.opener.testharness_properties)));
|
|
}
|
|
} catch (e) {
|
|
}
|
|
|
|
add_completion_callback(function(tests, harness_status) {
|
|
if (window.internals) {
|
|
// NOTE: If we're running inside the test harness,
|
|
// filter out stuff we don't want to see, like local filesystem paths.
|
|
for (const details of document.querySelectorAll("pre, details")) {
|
|
details.style.display = 'none';
|
|
}
|
|
window.internals.signalTextTestIsDone(document.getElementById("log").innerText);
|
|
}
|
|
});
|
|
|
|
|
|
// vim: set expandtab shiftwidth=4 tabstop=4:
|