Meteor-Community-Packages / Meteor-Community-Packages/meteor-browser-tests
Feature: add tests + ci
Open
enhancement
help wanted
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
We should definitely add some self-tests to track any regression during pull requests and a linter. We can all set this up in a simple GitHub actions ci
Contributor guide
Research direction
No files, tests, or entry points are named. Start by inspecting the repository's existing JavaScript test entry points and package configuration, then determine how GitHub Actions should run self-tests and a linter. Done means regression tests, linting, and a repeatable CI workflow are defined and passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, testing, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100