Test strategy

What to test?

In the other chapters it is described how to test (pytest, playwright for frontend, svelte unit tests).

This chapter discusses, what exactly should be tested, and what should not.

What to test

What not to test

Libraries

We expect libraries to have their own test suites that make sure, the library works works as intended.

However, there are some cases where a library function might be ambiguous and that should be tested.

TODO Example

Implementations

We should not test the implementations.

Input -> function / algorithm -> Output

We should only test, if we get the expected output with a given input. We should not test, if a function has been called and how many times and with what arguments.

Instead, focus on the input types and values, and check if the output is as expected.