billimarie / billimarie/prosecutor-database

[CODE] Create Unit Tests, Consider Continuous Integration

Open
#150 4 comments 1 reaction 0 assignees View on GitHub
CODE Hacktober Hacktoberfest HELP-WANTED JS
Dominant language
JavaScript
Stars
95
Forks
91
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
This project is quickly acquiring collaborators, and tests will help align the outcomes of our work and hopefully make @billimarie's role a little easier!

**Describe the solution you'd like**
Write [Mocha](https://atmospherejs.com/meteortesting/mocha) Unit Tests as per [Meteor/Testing](https://guide.meteor.com/testing.html). This could be a continuous project, as more and improved tests will always be necessary!

Perhaps a separate issue could be used to integrate continuous testing (CircleCI).

Contributor guide

Open the contributing guide

Research direction

No files, existing tests, or entry points are named. Start by inspecting the repository structure and current test setup, then review the linked Mocha and Meteor/Testing guidance. Done would require an agreed test scope with working Mocha unit tests; CircleCI integration is suggested as a separate issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
ci-cd, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.