added upload artifact step to the test workflow

[borisnieuwenhuis]

So you can access the test result from the containing workflow and publish the test results

[Woody4618]

Thank you for this. Why do you need a test results file, when you can see the test results in the actions tab already? Whats the workflow that this helps with?

[borisnieuwenhuis]

@Woody4618 I would like to see it in the pr summary, see image below. The actions tab is far out of context, you have to also drill down in the run-tests step, there you see this report, but it is far away.

'''

Running test suite: "/home/runner/work/crunchdao-protocol/crunchdao-protocol/Anchor.toml"

PASS tests/crunch.spec.ts (51.567 s)
PASS tests/coordinator.spec.ts (10.579 s)
PASS tests/staking.spec.ts (5.276 s)
PASS tests/idlutils.spec.ts

Test Suites: 4 passed, 4 total
Tests: 2 skipped, 46 passed, 48 total
Snapshots: 0 total
Time: 68.403 s
Ran all test suites.
'''

Also I might want to publish code coverage report etc. Would like to have clearer and more prominent presentation for it then deep down in an action step.

[Woody4618]

I see, cool! Could you add to the readme how to set this up? How the test file should look like for anchor tests. Then i will try it out and then we can merge it. Great addition :)

[borisnieuwenhuis]

@Woody4618 I will change it a bit, now it is too much focussed on test results. I think you should be able to download any artifact that gets produced in the test run. I will come up with a more generic setup

[Woody4618]

I think its ok if its focused on test results. Running the tests should be as straight forward as possible if we can get an easy and nice test result that is a win. If someone wants to upload other artifacts they can also just add another step to their workflow probably. But happy to see what you come up with :)