API tests discussion :)

[manonthegithub]

I have briefly reviewed tests. https://github.com/dbpedia/databus/tree/master/server/app/test

Looks already pretty good, but I got a few comments on that.
I think using test frameworks is generally a very good practice, as they not only help to write test more easily, but also simplify separation of the test code from the production (not sure how it is done in databus atm):
https://blog.logrocket.com/comparing-best-node-js-unit-testing-frameworks/
maybe you could consult with Jan which framework is better to use in node.js.
Some more comments:

• single action = one test with description (no long tests with lots of different function calls)
• code should not contain commented out long parts of code (that is universal for tests and for production code)

[manonthegithub]

For the release I would definitely at least rearrange tests with a test framework

[kurzum]

Clarify when the current tests are actually executed. Next time we extend tests, we will refactor the testing framework.

[holycrab13]

Refactoring our tests to be executed in the context of a framework is a good idea. Should be fairly easy to transform the current "assert" setup to somthing like Jest (https://jestjs.io/docs/getting-started)

[holycrab13]

using nodejs test framework uvu