SuffolkLITLab / ALKiln

Integrated automated end-to-end testing with docassemble, puppeteer, and cucumber.
https://assemblyline.suffolklitlab.org/docs/alkiln/intro
MIT License
14 stars 4 forks source link

Close #701, allow author to access the text of unexpected results in a portable way #911

Closed plocket closed 1 month ago

plocket commented 1 month ago

In this PR, I have:

What do these changes do?

  1. 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 .
  2. Fix how we handle tag expressions that have multiple tags in them.
  3. Add an actually failing test that we exclude and can test manually when needed.
  4. 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

The workflow was able to create the "failure" issues correctly.