-
Notifications
You must be signed in to change notification settings - Fork 189
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
Add more structured output for tests #626
Conversation
75a2ccb
to
4b376ed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be good to go after a rebase.
const state = event.pass | ||
? 'passed' | ||
: event.messages?.length | ||
? 'errored' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would failed due to errors
or failed to run
be more meaningful for the user? I had to think about the difference between 'errored' and 'failed' for a moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That won't work. state
is a property of the TestEvent
interface and only allows 'running' | 'passed' | 'failed' | 'skipped' | 'errored'
. The hope is that the messages will be more explicit as to what happened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh fair enough. We can consider having more detail in the way message
is constructed below, but no need to block this PR.
f0ad23b
to
4d24f85
Compare
The diff and the errors were always available, but they were not being sent to the output. Additionally, make sure to send output to both the test explorer log and the codeql test log.
4d24f85
to
11517ee
Compare
The diff and the errors were always available, but they were not being sent to the output.
Additionally, make sure to send output to both the test explorer log and the codeql test log.
Resolves #582.
Checklist
@github/docs-content-dsp
has been cc'd in all issues for UI or other user-facing changes made by this pull request.