-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is needed
Description
Since our code is going to be used in real tournaments, it would be nice to know, if it works (obviously). Rust is very bug-resistant, but it cannot detect business-logic-related issues (I've already managed to create some). Therefore we should complement out project with automatic tests. We should test endpoints, i.e. send requests to the server and check, whether the responses are correct.
There are a few issues to tackle here:
- Figuring out how to write these tests in the first place. I tried to research that on my own, but with little success.
- DB issues – running the tests would require either mocking the database (which would substantially increase the workload and make the tests less credible) or having a deployed database run the tests on (which might cause problems with GitHub Actions).
- Test coverage – the bare minimum should be testing a happy path for each endpoint. On top of that, we should write a bunch of tests for entire flows (ones described on FigJam). This way we'll be able to guarantee that the app meets requirements we set for it.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is needed