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
Hello, first and foremost thanks a lot for the tool 🙏
In the project I work on the report is always way bigger than GitHub's limit. Constantly leading to failures and reports that are incomplete and not so actionable besides the annotations. Example:
$GITHUB_STEP_SUMMARY upload aborted, supports content up to a size of 1024k, got 8815k. For more information see https://docs.github.com/actions/using-workflows/workflow-commands-for-github-actions#adding-a-markdown-summary
The project is very modular, with 100+ modules and 8k+ unit tests, and due to the size of it the resulting test report only has a few modules shown.
I already limited as much as possible the output, by setting both show-passed-tests and show-code-coverage to false 👇 , but it's still quite over the limit
with:
title: Test results
show-passed-tests: false
upload-bundles: never
path: ./fastlane/test_output/Some-Workspace-merged.xcresult
token: ***
show-code-coverage: false
Question
Would you/or anybody that uses it be interested in a summarized report? That could be useful for similar large scale projects.
My suggestion would be to simplify the "Test Summary" section to do not list all test classes but rather the amount of successes and failures in the module level and potentially hide the Test Details section.
Example
SomeTestTarget
// device and SDK info also repeats often if using the same across the whole test suite, perhaps there could be an option to
// hide it or have a single entry for it when showing a summarized version of the report
Device: iPhone 14, 16.4 (20E247)
SDK: Simulator - iOS 16.4, 16.4
Total Success Failure Skipped Expected Failure Total time
340 337 2 1 0 2s
Hello, first and foremost thanks a lot for the tool 🙏
In the project I work on the report is always way bigger than GitHub's limit. Constantly leading to failures and reports that are incomplete and not so actionable besides the annotations. Example:
The project is very modular, with 100+ modules and 8k+ unit tests, and due to the size of it the resulting test report only has a few modules shown.
I already limited as much as possible the output, by setting both
show-passed-tests
andshow-code-coverage
tofalse
👇 , but it's still quite over the limitQuestion
Would you/or anybody that uses it be interested in a summarized report? That could be useful for similar large scale projects.
My suggestion would be to simplify the
"Test Summary"
section to do not list all test classes but rather the amount of successes and failures in the module level and potentially hide theTest Details
section.Example
Similar issues
This may potentially be a duplication of #145
The text was updated successfully, but these errors were encountered: