-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Code coverage report is not showing up #128
Comments
No, that message is irrelevant. That message simply informs you that the report was partially truncated because it exceeded the internal limits of the GitHub Checks API. Strictly speaking, it is a warning message, not an error. I think the reason why the code coverage is not shown is that the XCResult bundle does not contain coverage. Can you confirm that the test bundle contains the coverage data? Or can you share the test bundle for me to investigate the problem? |
It does contain it When I run |
It seems the report generated is cut off |
Oh, that's probably why. GitHub Checks has a character limit, and I think it exceeded that limit just by reporting lots of test failures. That's probably why the test coverage was truncated. |
I see, Is there any workaround for this? |
If you set the However, the case where so many tests are failing is currently outside the scope of the use case. What kind of behavior are you expecting? Do you only want to see the test coverage? |
Yes tried with that flag, it improved a little bit, but still not covered all test classes and got cut off in details view |
I see. Thanks.
Yes, I agreed with you. I plan to do that eventually, but it will take some time because I need to rewrite parsing xcresult into a flexible code. |
Cool, Thanks for the tool |
@tonyarnold do you mean you are not getting the test results at all or is it like me just cut off in the middle? |
My results did show up (although I misunderstood that it overwrites the results if you try to capture more than one xcresult bundle), however they were truncated like yours @denil-ct. |
Is there anyway the tool can generate an output file that we can upload as an artifact to get around the git word limit? |
@Dharna We decided to go with this tool as it gave a file output that we could then ingest into our systems. This allowed us to overcome the truncation issue. Although, one thing to note is, that tool was not designed for Xcode or iOS development in general, more oriented towards windows, so you might need to install a couple of dependencies as needed. |
@denil-ct I see. Yeah I am mainly looking for iOS and macOS report generation. Thank you for the tool! Will take a look. |
I had 255 test cases and 77 cases failed
I had these errors, is it because of that?
The text was updated successfully, but these errors were encountered: