You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because my tests are getting big and are running in a github action workflow, i was thinking about to optimise the way, they are displayed in github actions.
One thing i was thinking, is using github actions workflow commands to optimise output. Even subtests are a good option for grouping:
But till now, i was not realy able to extend the existing formater to extend the output.
The other thing i was thinking about is, having the error message in the review section linked to the line where the error occured.
There is a tool, named reviewdog which is capable of doing this. I think it shoud be possible to define the errorformat correctly to the tap output, but till now i had no luck specifying a multiline error format which captures the relevant things.
I have a question with the formatter.
Because my tests are getting big and are running in a github action workflow, i was thinking about to optimise the way, they are displayed in github actions.
One thing i was thinking, is using github actions workflow commands to optimise output. Even subtests are a good option for grouping:
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#example-setting-a-value
But till now, i was not realy able to extend the existing formater to extend the output.
The other thing i was thinking about is, having the error message in the review section linked to the line where the error occured.
There is a tool, named reviewdog which is capable of doing this. I think it shoud be possible to define the
errorformat
correctly to the tap output, but till now i had no luck specifying a multiline error format which captures the relevant things.https://github.com/reviewdog/reviewdog
I found no other aproaches, which confuses me. Are there any other ways to go.
The text was updated successfully, but these errors were encountered: