Refactor tests to use proper "build-up" and "tear-down" hooks to reset the db before/after each test suite is run.

[r002]

Eventually, "npm test" will run all test suites in parallel. I have two options:

1. Either refactor the code to use "clients" from the pool which will give me transaction management. This way I can easily commit transactions and roll them back after every test-suite is run without having to reset the db each time.

2. Spin up a new db instance (Docker?) for each individual test-suite. After each test-suite finishes, I then just discard its db image.

---

• https://node-tap.org/docs/cli/
• https://node-tap.org/docs/api/subtests/
• https://stackabuse.com/executing-shell-commands-with-node-js/
• https://www.freecodecamp.org/news/node-js-child-processes-everything-you-need-to-know-e69498fe970a/
• https://scotch.io/courses/10-need-to-know-javascript-concepts/callbacks-promises-and-async