ComputerScienceHouse / ComputerScienceHouse/packet
Actual Unit tests
- Dominant language
- Python
- Stars
- 25
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Lord how annoying it is to write tests, but this application and it's importance requires some basic unit tests. We should have edge cases tested against.
- Underclassman tries to sign as upperclassman
- Off Floor Underclassman tries to sign packet
We will also need some kind of mocking database system to create the logic for this
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the application logic for the two listed cases: an underclassman signing as an upperclassman and an off-floor underclassman signing a packet. Then identify how database access is handled and choose a mocking approach; done means both edge cases have unit-test coverage and the tests run reliably without the real database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python, sqlalchemy
- Domain
- backend, database, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100