Add test scripts

[kretep]

This adds mainly:

• a script (test.sh) that traverses all the tools, executes their CWL description with the provided input.yml, and reports test results.
• a github actions workflow to execute the tests

[kretep]

The tests are failing as expected, as the sage config.json is not available on main yet.

[vedran-kasalica]

Do we want to have this file in the repo? If I understood correctly, actions using act do not work locally, right?

[kretep]

I removed it, since it's mainly for convenience and only one command.

I guess in theory it could work, but it failed because of Docker in Docker limitations. You'd have to mount the docker socket inside the first container somehow, but I didn't manage to get it working.

[vedran-kasalica]

Does it make sense to move this script to .github? I am not sure what is the policy of .github content. It would also be nice to rename the script to something a bit more descriptive.

[kretep]

The idea is that the script is also runnable locally (it is) if you want to run the tests, so I wouldn't put it in .github. What would you suggest for a name? Maybe we should move it to a test folder or something

[vedran-kasalica]

I see, in that case I would suggest maybe naming it test_cwl_annotations.sh, what do you think? If the idea is that you can test it locally, we should add a line in the readme that describes how (and why) to run it locally.

I guess the following 3 would be sufficient:

• a line describing the script
• mention the cwltool dependency
• provide a command on how to run it

[magnuspalmblad]

I agree with a more specific name, since there are probably many test.sh scripts around.

[vedran-kasalica]

The added tests are really useful, and the only thing that I would recommend updating is the test.sh and the readme to document it (as discussed in the comments). After that, the PR can be merged.