Re: [community-group] How library and tooling authors do keep track of conformance and changes? (#247)

Is a shared test suite something that could help?

Each test could consist of:
- a tokens json file
- a token that is the focus of the test
- one or more expected representations of that token

Then tools could run their implementation against the test suite and check the result of parsing against the expected representation that matches their domain.

-----

For all things web we have the [web platform tests](https://github.com/web-platform-tests/wpt).

For my own work on CSS tooling I also try to publish and maintain shared tests so that other packages can more easily have correct implementations. (e.g. https://github.com/romainmenke/css-tokenizer-tests)

Such shared tests reduce the amount of work that each project needs to do and makes it easier to have interop.

-- 
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/247#issuecomment-2304377296 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 22 August 2024 10:57:48 UTC