Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance traceability of XSpec reports #12

Open
wendellpiez opened this issue Jun 24, 2024 · 2 comments
Open

Enhance traceability of XSpec reports #12

wendellpiez opened this issue Jun 24, 2024 · 2 comments

Comments

@wendellpiez
Copy link
Collaborator

XSpec Test Results

2 tests  ±0   2 ✅ ±0   0s ⏱️ ±0s 1 suites ±0   0 💤 ±0  1 files   ±0   0 ❌ ±0 

Results for commit 2497040. ± Comparison against base commit ff8255d.

Is there supposed to be a link to a page that shows which tests were run and maybe the log details?

Originally posted by @galtm in #11 (comment)

This may require some research into JUnit in GH and how it can be enhanced coming out of XSpec's XSLT - so actually an XSpec issue, albeit easier to test out in this repository.

More modestly, there might be settings or other points of control to improve this or help users.

@galtm
Copy link
Collaborator

galtm commented Jun 24, 2024

Is there supposed to be a link to a page that shows which tests were run and maybe the log details?

My mistake: When I made that comment, I had in mind the logs I had seen in the metaschema-xslt repo (e.g., usnistgov/metaschema-xslt#116), and I thought I had reached the logs through a link in the automated comment. But in fact, I reached the logs by clicking the Checks tab on the pull request. That mechanism works in this repo, too. The log is not perfect, as it doesn't seem to show the test file name, which is something that one might want to search for in the log. But at least the log is reachable!

@wendellpiez
Copy link
Collaborator Author

Well yeah, but there are still significant improvements that could be made aiding in transparency in general, and some of them might be straightforward ...

Here, the process is only making the JUnit report files available but HTML results per XSpec could also be posted. Question is where, for them to be reachable.

wendellpiez added a commit to wendellpiez/oscal-xproc3 that referenced this issue Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants