ladybird/Tests/LibWeb/Ref/input/square-flex.html

<!DOCTYPE html>
<link rel="match" href="../expected/square-ref.html" />
<style>
    .box {
        display: flex;
    }

    .item {
        width: 100px;
        height: 100px;
        background-color: pink;
    }
</style><div class="box"><div class="item">
Meta: Add DOCTYPEs to ref tests 2025-03-18 15:29:54 -03:00			`<!DOCTYPE html>`
Tests/LibWeb: Restructure Ref and Screenshot test dirs to match others Now each test type has the same directories: - input - expected - data Also, tests can be in subdirectories within ./input. 2024-11-05 09:49:08 -03:00			`<link rel="match" href="../expected/square-ref.html" />`
headless-browser: Add ref tests support The ref tests runner takes screenshots of both the input page and the expected page, then compares them. Ref testing allows us to catch painting bugs, which cannot be detected with the layout and text tests we already have. With ref tests, we'll likely want to reuse the same expectation page for multiple inputs. Therefore, there's a `manifest.json` file that describes the relationship between inputs and expected outputs. 2023-08-13 19:37:49 -03:00			`<style>`
			`.box {`
			`display: flex;`
			`}`

			`.item {`
			`width: 100px;`
			`height: 100px;`
			`background-color: pink;`
			`}`
			`</style><div class="box"><div class="item">`