Give the user access to the artifact files and give them the paths to various reports so they can get those files and use them or their contents in whatever way they choose. For example, they can include the output in an issue. This includes paths to a new unexpected results[^1] file, but also other files .
Fix how we handle tag expressions that have multiple tags in them.
Add an actually failing test that we exclude and can test manually when needed.
See the changelog for more details.
[^1]: Note: Unexpected results means non-passing tests. For example, failures and undefined steps (typos).
Links to any solved or related issues and/or (other) reasons for this PR
Close #701
Any manual testing I have done to ensure my PR is working
Tested with error that wasn't from a cucumber test (which meant no artifacts existed at all). run: exit 55
Tested with cucumber test error
Tested with no errors
The workflow was able to create the "failure" issues correctly.
In this PR, I have:
What do these changes do?
[^1]: Note: Unexpected results means non-passing tests. For example, failures and undefined steps (typos).
Links to any solved or related issues and/or (other) reasons for this PR
Close #701
Any manual testing I have done to ensure my PR is working
run: exit 55
The workflow was able to create the "failure" issues correctly.