Orange-OpenSource / Orange-OpenSource/Orange-Boosted-Bootstrap
Investigate tests rationalisation (all jasmine or all vitest)
Open
Nobody has claimed this yet.
🔍 study
- Dominant language
- CSS
- Stars
- 219
- Forks
- 61
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 12
Description
Port jasmine tests to vitest ? or the other way around ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, test paths, or entry points are named. Start by inventorying the existing Jasmine and Vitest configuration and test suites, then compare migration effort and project fit. Done means the project has a documented decision and a defined, consistently applied test setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100