search

usnistgov / oscal-xproc3

OSCAL (Open Security Controls Assessment Language) on an XProc3 platform
Other
9 stars 3 forks source link

Enhance traceability of XSpec reports #12

Open wendellpiez opened 5 months ago

wendellpiez commented 5 months ago

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 https://github.com/usnistgov/oscal-xproc3/issues/11#issuecomment-2186703971

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 commented 5 months ago

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., https://github.com/usnistgov/metaschema-xslt/pull/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 commented 5 months ago

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.