Update workflows to run canary unit tests
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
### Summary
After https://github.com/mi6/ic-ui-kit/pull/4150 the canary unit tests should now be able to be added to the CI workflows.
### 💬 Description
I can't see any scripts in the package.json so we'll need:
- A regular test script
- A test coverage script (this might show a few components under the coverage - if it does, open a ticket to add tests to those components and don't add this script to the workflow until that's done)
- Add those to CI workflows (same places we run core unit tests)
### 💰 Use value
We'll be more confident in our canary components if we can run the unit tests without having to pull them into the core package.
### Additional information
Blocked by #4151, #4152, #4153
Contributor guide
Research direction
Start with package.json and the CI workflow locations where core unit tests currently run. Check the canary test setup after #4151, #4152, and #4153, then define regular and coverage scripts and verify their output. Done means both scripts work and CI runs the regular tests in the same places as core tests; add coverage to CI only if it does not expose untested components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100