Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
[Testing] - Write Unmocked Tests for Get Blocking Work Packages Endpoint
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
We want to ensure our endpoints communicate with our database correctly and handle all appropriate business logic. You can setup the testing environment by running yarn test:setup. Then you can run yarn test as many times as you wish. Once done you may run yarn test:teardown to shutdown the testing environment and be able to use the normal dev environment again.
Acceptance Criteria
- Tests that force all exceptions to occur
- Test that successfully invokes the function for the expected output.
Proposed Solution
Look at how unmocked tests are currently used. You may want to look at test.utils.ts to see how we create test projects and setup organizations.
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
Run yarn test:setup, then inspect existing unmocked tests and test.utils.ts for test-project and organization setup. Exercise the Get Blocking Work Packages endpoint through its expected successful response and each exception path, using yarn test to verify coverage; run yarn test:teardown when finished.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, database, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100