Unittests

[psteinb]

What?

The test coverage is very low. There is no unified way to test e.g. invertibility, or Jacobian (has to be written once, and can work for all modules).

How?

Set up the proper structure to test all modules in a universal way, in addition to module specific tests that may be necessary. Ensure there is test coverage for everything, including FrEIA.framework.ReversibleGraphNet and FrEIA.framework.ReversibleSequential.

[psteinb]

I am happy to help with this one - see also this PR.

With the current setup, the main question is, which CI infrastructure to use. Travis CI is effectively gone for open-source projects. And github actions is the current place to run your scripts. That effectively also means, that all unit tests should be light weight to run on a single CPU.

[ardizzone]

The following issue can be closed once the new tests are done:
vislearn/FrEIA#45

[psteinb]

Please consider merging vislearn/FrEIA#55. It will trigger continuous integration with github actions. This will be the basis for further unit tests to build.

[psteinb]

Thanks @tbung for merging vislearn/FrEIA#55. I'd also like your thoughts to the unittest library being used. See vislearn/FrEIA#56

[ardizzone]

Hmm, the action appears under the 'Actions' tab, but it's not running. Does anyone have insights?

[psteinb]

Should be triggered by the next PRs coming in that use the workflow code. I'll see to something like this in the afternoon. But feel free to submit a PR and experiment.