Integration and Release testing concept

We have two collection of CPACS files, one is in https://github.com/DLR-SC/tigl-examples for public files, the other one is in the DLR gitlab
Each repository has a collection of integration tests that test specific issues for each geometry
The gitlab repository contains the github repo as a submodule.

Integration tests:

In github, we run the public integration tests as nightly runs.
In DLR gitlab, we run both public and private integration tests as nightly builds on all test cases based in TiGL master.
We also use the cpacs examples files from tigl/tests/unittests/TestData for integration tests.
~~Run valgrind on unittests or unittest selection (tbd)~~
Use Adress sanitizer on nightly tests in private repo

Each file has to load successfully in TiGL Viewer without crashing -> Script required. TiGL Viewer should make a screenshot with zepra stripes of each configuration. If possible: All images are collected into one pdf. Question: Can we compare screeshots against reference images in sensible way?
Run integration for example repositories
Bindings must be tested
Artefacts have to be tested (to be decided how, automatized in CI, part of unittests testing stage)
Screenshots must be looked at before release