Expose web5-spec tests reports in JUnit XML format #65
Assignees
Labels
cicd
CI/CD and Automation
Comments
finn-block
added a commit
that referenced
this issue
Nov 27, 2023
Fixes #65 and re-arranged some stuff: * split out all report renders to their own file * update result struct to track per-test runtime * disable failing web5-kt test * use web5-js test from web5-js repo, drop web5-js test from this repo * renamed the go package to reflect the current repo name
finn-block
added a commit
that referenced
this issue
Nov 28, 2023
Fixes #65 and re-arranged some stuff: * split out all report renders to their own file * update result struct to track per-test runtime * disable failing web5-kt test * use web5-js test from web5-js repo, drop web5-js test from this repo * renamed the go package to reflect the current repo name
finn-block
added a commit
that referenced
this issue
Nov 28, 2023
Fixes #65 and re-arranged some stuff: * split out all report renders to their own file * update result struct to track per-test runtime * disable failing web5-kt test * use web5-js test from web5-js repo, drop web5-js test from this repo * renamed the go package to reflect the current repo name
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we are discussing in discord, we landed in a tool to gather our tests trend: BuildKite Tests Analytics, sample can be seen here.
Now we just need to make sure our tests reports are also generating a junit xml artifact. (Which most tests frameworks do, even rust!)
For this issue we are asking to expand the web5-spec e2e tests (and soon to be developed tbdex-spec) to also generate the JUnit XML file.
The text was updated successfully, but these errors were encountered: