Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
Test Suite - Unmocked Tests for Delete Unit Endpoint
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
We are making tests in a new way that uses an actual database rather than mocking calls to prisma. You can run these tests by running yarn test:setup, then running yarn test (make sure to run yarn test:teardown whenever you're done). You can see examples of how to do these new tests in src/backend/tests/unmocked/
This ticket is to make tests of this new type for the delete unit endpoint
Acceptance Criteria
- Tests that force all exceptions to occur
- Test that successfully invokes the function for the expected output
Proposed Solution
Look at how other unmocked tests are writen. Put this in a bom tests file if it does not exist (not projects)
Mocks
No response
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 reviewing the examples in src/backend/tests/unmocked/ and run yarn test:setup before exploring the existing BOM tests file, creating it if needed rather than using projects tests. Add unmocked coverage for the delete unit endpoint, including every exception path and the successful expected output, then run yarn test and yarn test:teardown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100