You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are we copying / transforming these tests into our codebase? Or could we use the tests "as-is" and have our code transform anything? I would opt for the latter, as we don't want to clutter our codebase with other people's code too much.
To ensure that our CSS3 tokenizer adheres to the CSS3 specifications, we should include all tests from the css-parsing-tests repo.
I have already added a lot of tests, and the tokenizer is passing them all, but it is best to add them all to ensure we are covering all bases.
I will add some here and there, but for the time being, I will focus on the CSS3 parser.
Writing tests should be simple. Here is an example of writing this test from css-parsing-test into our tests
Considering the tokenizer, we only interested in tests in component_value_list.json file
The text was updated successfully, but these errors were encountered: