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
Currently xcbeautify (with the GitHub Actions parser) parses errors inline where they occur. This makes it difficult to get a quick summary of the failed cases and reasons, like what we had with xcpretty.
Part of the issue is that, for GitHub Actions, the summaries only show up in the Summary view, and in that case they're all lumped together. I'd like to be able to click on a particular job, which automatically scrolls to the bottom, and see exactly which tests failed and why.
The text was updated successfully, but these errors were encountered:
Hey @jshier! Thanks for filing this issue. I just recently released 2.0.0 which has been my focus for the past few weeks. Your concern is definitely on the roadmap, and I have encountered the same frustration. I have this draft PR that starts the process, and it was waiting on the 2.0.0 release. I'll post an update as soon as it is available.
Currently
xcbeautify
(with the GitHub Actions parser) parses errors inline where they occur. This makes it difficult to get a quick summary of the failed cases and reasons, like what we had withxcpretty
.Part of the issue is that, for GitHub Actions, the summaries only show up in the Summary view, and in that case they're all lumped together. I'd like to be able to click on a particular job, which automatically scrolls to the bottom, and see exactly which tests failed and why.
The text was updated successfully, but these errors were encountered: