stawuah
commented
9 months ago When testing data insertion into the database, I prefer writing unit tests for individual functions, treating them as edge cases instead of testing the entire insertion process as a whole.
A good first issue should be :
- Handling database connection failures.
- Dealing with duplicate entries.
- Testing performance with large datasets( if it's a working application )
- Inserting invalid or incomplete data.
When tests hitting the db are ran together they fail. I'm thinking it has to do with the connection being open/closed on hits. Need to research this and figure out what's happening. I tried awaiting the db.close but that's not likely possible in some instances when we're returning a promise from a non async function. Again, need to research a bit and possibly refactor the route code. Currently it's modular, in that the function that hits the db is in the DAL. It may be that we just need to put it directly in the route so that we can close it then without having to worry about defining additional async functions.