lgartrell
commented
3 years ago Test Setup:
- [ ] complete
routes hit:
- User Register
- Admin Register
- Create for all types of appointments (celestial body, coordinate, drift scan, raster scan)
- All manual types of appointments? maybe another test?
- All appointment requests? maybe this is in another test?
- Create radio telescope object - can we do this through a route? need postman to run a SQL seed script?
- Create users - how many do we need? what types?
- Create appointments for users - how many do we need? types?
- Fake / generate sensor, weather, spectracyber data, rf data, feedback, and celestial bodies - how many, types?
Overview
Work related to end-to-end testing of the back-end application. Test cases are to be made from the paths below
Things to keep in mind
1. This needs to be flexible, and not break on new additions
To get to this point, we need to have a set database configuration we will be running tests on. My idea is to have the setup for the database also be run through the routes. The test routes create the test users, appointments, sensors, etc. we will be accessing and modifying through the routes.
2. We need as close to 100% code coverage as it gets
This will be a multi team effort, mainly by other teams describing test cases for how they touch the backend. I know I do not have the knowledge needed to write out every test case possible, there is just too much I don't know. Group effort on this one
3. Hard to test parts of our application
Things like sending emails, admins interacting with links sent through email, and testing the routes directly related to hardware are all going to be difficult to isolate in a "unit" style test. Until we get to the point where we have everything easily testable written down in a collection, we can let this slide. After that, I think the best case will be to create a dummy endpoint that has identical functions as the real routes. The dummy endpoints can be hard coded so they behave in the edge cases we decide.