shift-org / shift-org/shift-docs
calendar: Create tests for API and front-end
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
It would be helpful to have a suite of tests that we can run to verify that important functionality still works. They should at least be available to run manually in your local dev environment; bonus points for automatically running on PRs, etc.
There are two main classes of tests needed:
- API
- website front-end
Conventional wisdom is to write tests in the same language as the application, so the dev environment and dev knowledge can be maximized. (So, PHP or Javascript in our case.) In practice, the best tests are the ones you actually run, so whatever we can reliably maintain is best. A lot of test frameworks use custom DSLs anyway, so aside from some syntax familiarity there may not be a ton of efficiency either way.
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 locating the API and website front-end entry points and checking what development and test tooling already exists. Define a maintainable suite that can run manually locally, with PR automation as an optional follow-up; done means important API and front-end behavior is covered and the commands are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- api, frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100