- From: Drew Powers via GitHub <noreply@w3.org>
- Date: Thu, 11 Dec 2025 16:01:42 +0000
- To: public-design-tokens-log@w3.org
> I wasn't able to find any existing set up for tests in this repo. Do you have any guidance where/how to set it up? I don't think transitioning to Vitest should be an issue. Ah so we have a pnpm workspace. In the root level there’s no test framework, but inside `www/` there is Vitest configured (if you rebase off latest `main`; I forget when it was merged in). For tests in `public` I’d recommend just adding a new `www/tests` folder they can run from, that way we don’t deploy our tests to the website 😄. They should get picked up automatically, but if not, it’s just modifying Vitest’s [include](https://vitest.dev/config/include.html) option. I do think the tests are optional—if you have some that are ready, or they wouldn’t take much time, we’d love to add them! But I don’t want to make this PR blocking. I tested it again and it works great 🙂 -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/360#issuecomment-3642612224 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 December 2025 16:01:43 UTC