[meom code clinic] tests

[rcaneill]

This issue is open for the MEOM internal code clinic / review process

[rcaneill]

tests

• [ ] The package has tests:
  • [ ] Tests cover essential functions of the package and a reasonable range of inputs and conditions.
• [ ] Continuous Integration: Has continuous integration setup (We suggest using Github actions but any CI platform is acceptable for review)

[rcaneill]

@alexis-barge could you add the link of the example we should review?

[alexis-barge]

Test case NEMO-DINO : https://github.com/morays-community/NEMO-DINO Related doc: https://morays-doc.readthedocs.io/en/latest/getting_started.html

[rcaneill]

This issue is not easy to handle, as morays describes with documentation, and is not a package.

We discussed the following points:

• the doc provides a lot of code snippets (bash scripts to install, compile, etc) and produce an environment with all the necessary dependencies to run a coupled config bridging the gcm with ML componant. All these snippets are actually not tested. One way to test them, would be to try executing them all in a clean environment (e.g. clean debian).
• an easy solution for the user would be to provide containers (e.g. apptainer) with a working environment.

These 2 points are linked, as one could use the code snippets to actually build the container. This would thus test the code while providing a nice CI. How to actually do this is still an open question.

[rcaneill]

see https://stackoverflow.com/questions/33146202/get-code-from-rst-file-code-blocks