Test workflow

[eriktks]

DRAFT

Description

Adding a test workflow. Approach:

1. No test has been written for testing if the action succeeds or fails (seemed unnecessary)
2. The existence of the report was tested with ls -l. If report is not there, the command fails and the action fails
3. Pending discussion, the contents of the report has been compared against a fixed file. This will fail when the target repository (howfairis) is updated. However, a more flexible approach would require rebuilding tortellini for this test which feels like too much work. The comparison code with jq was taken from https://stackoverflow.com/questions/31930041/using-jq-or-alternative-command-line-tools-to-compare-json-files

Refs: #32

---

Before you get started

• [x] I read and I followed contributing guidelines
• [x] ☝ Create an issue to discuss what you are going to do

Checklist

This section should be filled in by the creator of this pull request to make sure the pull request is ready to review.

• [x] This pull request has a descriptive title
• [x] Code is written according to the code quality guidelines
• [ ] Documentation if applicable is available
• [ ] Tests run successfully
• [ ] All checks below this pull request were successful

Instructions to review the pull request

Action should run and complete without errors

DRAFT

[eriktks]

Work on this task is continued in the branch PR #132