Our current testing environment only provides very limited testing of the different language bindings.

What we have

systemtests that run the solverdummies for the different language bindings in precice/systemtests/tree/master/Test_bindings.

What we want

Bindings tests that can be run easily:

• for c, cpp using ctest (either independently or in the main build directory)
• for python using python3 setup.py test (compare to fenics-adapter, testing)
• for fortran?
• coming soon: MATLAB bindings (Implement a Matlab API #102). Currently, no tests.
• for other?
• run all tests automatically for each commit in Travis (just like the preCICE unit tests)

The main problem

Currently, we have to run two solverdummies in order to be able to test the bindings. Isolated tests for testing the API calls independently cannot be realized. We do not want to spoil the solverdummies as their purpose is to show how the API can be used, not testing.