sillsdev / sillsdev/languageforge-lexbox
Set up Svelte component tests
Open
Nobody has claimed this yet.
📦 Lexbox
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
We want infrastructure for doing component testing in Svelte:
- Choose framework (Testing library, Playwright Storybook?)
- CI / GitHub action
Contributor guide
No contributing guide indexed for this repository
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
Start by comparing the candidate approaches named in the checklist: Testing Library, Playwright, and Storybook, then inspect the repository's existing CI configuration. Done means a testing framework is selected, component tests can run, and a GitHub Action executes them in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, playwright, storybook
- Domain
- ci-cd, frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100