feat: add node test reporter#909
Merged
Merged
Conversation
003e722 to
8f3ae30
Compare
This comment has been minimized.
This comment has been minimized.
c10ff0e to
623e2c4
Compare
This comment has been minimized.
This comment has been minimized.
623e2c4 to
5c5a2fb
Compare
Contributor
Coverage ReportReportReport Validation |
|
🎉 This PR is included in version 6.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a native Node.js test runner reporter (
src/reporters/node.js) that produces a schema v3 D2L test report, coveringname,location,taxonomy,started,duration,status,retries, andgithub.codeowners, alongside integration test fixtures, validation, docs, and a README entry. The reporter works both through the CLI via the--test-reporterflag (reading options fromD2L_TEST_REPORTING_*environment variables since the runner does not forward options to custom reporters) and programmatically through the namedreporterfactory composed onto therun()stream.Each test detail omits
configuration.timeoutsince the Node.js test runner does not expose the configured timeout, andretriesis always0with no test counted asflakysince the runner has no built-in retry mechanism.https://desire2learn.atlassian.net/browse/QE-2218