Skip to content

modules: Add a web-platform-tests run module#695

Merged
svenstaro merged 1 commit intosvenstaro:masterfrom
alimpfard:wpt
Jan 8, 2026
Merged

modules: Add a web-platform-tests run module#695
svenstaro merged 1 commit intosvenstaro:masterfrom
alimpfard:wpt

Conversation

@alimpfard
Copy link
Copy Markdown
Contributor

@alimpfard alimpfard commented Nov 30, 2025

In case you're a browser person and want to pretend to be running tests.
This is a veeeery tiny slice of what WPT tests being run looks like, but it looks similar enough I think.

asciicast

The number of tests/subtests are roughly equivalent to the real test suite (though no one really knows the actual number anyway), and the final result is fairly close to what chrome would get IRL :P

@svenstaro
Copy link
Copy Markdown
Owner

Hey, this is great! However, I think you should try to condense the wpt_tests.txt file quite a bit. There's a lot of repetition in there that should really be generated on the fly. Or even better, try to generate the tests entirely from the data that we already have! For instance, you could combine stuff from terraform_ids.txt and packages.txt. I'm also cool with a new file but please try to dynamically construct the paths.

@alimpfard
Copy link
Copy Markdown
Contributor Author

alimpfard commented Nov 30, 2025

That file is just a list of tests I grabbed off wpt.py, we could probably just take a random 6k-long slice too.

I'm not sure if it'd make any sense to generate them from what's in the repo already since the names are pretty specific? maybe we could split it into some CSS property names, web platform names (e.g. API names), so other future modules could use them too?

@svenstaro
Copy link
Copy Markdown
Owner

That file is just a list of tests I grabbed off wpt.py, we could probably just take a random 6k-long slice too.

I'm not sure if it'd make any sense to generate them from what's in the repo already since the names are pretty specific? maybe we could split it into some CSS property names, web platform names (e.g. API names), so other future modules could use them too?

You can do it like you want, just the current file is way too large and I think we can easily generate some stuff.

Copy link
Copy Markdown
Owner

@svenstaro svenstaro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, this looks great and it seems very realistic even though I've never run web platform stuff myself. Just a few remarks and then we can get this merged. :)

@svenstaro svenstaro merged commit 262923a into svenstaro:master Jan 8, 2026
15 checks passed
@svenstaro
Copy link
Copy Markdown
Owner

Very cool, thanks!

svenstaro added a commit that referenced this pull request Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants