ilaflott
commented
3 weeks ago There are two possible solutions to this issue as written. Ideally in the long run, both of these tests would exist- as one failing (but not the other) would instantly point us towards/away from click machinery being part of the problem
using click.testing.CliRunner
This approach literally tests the CLI call shown in the bash script above, and would go in fre/tests/test_fre_cmor_cli.py. This soluition must not use subprocess.run to execute the call, as this is what CliRunner is for.
using from fre import cmor
This approach would test the equivalent functionality of the CLI call shown in the bash script above, using standard module imports and python packaging structure. It would not use the CliRunner, as it's testing the module functionality and not the CLI one. This would be a test written in a file like fre/cmor/tests/test_fre_cmor_run.py
The following script shows a working example of a
fre cmor runcall. Note that this script only illustrates usage- probably wont work out of the box for everyone:The
stdoutproduced byfre cmor runitself should look something like:the metadata differences introduced: