-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Delete TestSummary #237
Delete TestSummary #237
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #237 +/- ##
==========================================
+ Coverage 85.76% 87.79% +2.02%
==========================================
Files 15 14 -1
Lines 1665 1614 -51
==========================================
- Hits 1428 1417 -11
+ Misses 237 197 -40 ☔ View full report in Codecov by Sentry. |
9585694
to
0121351
Compare
a2a5342
to
cac7965
Compare
5e1180a
to
c342784
Compare
307c9e7
to
796761c
Compare
81d55fa
to
492afd1
Compare
492afd1
to
84c210e
Compare
84c210e
to
cd91c1e
Compare
cda9383
to
6822557
Compare
b12bccb
to
1418143
Compare
1418143
to
02b831b
Compare
1418143
to
2c6f909
Compare
2c6f909
to
cd02d55
Compare
That's regression, changes like that should be published as a major SemVer update. I relied on this summary line as source for auto test scheme size dynamic metrics. Now I have to grep Test_Scheme_run.log and use counter. |
Changes
Delete custom
TestSummary
logic. Instead, parse and use the output given byxcodebuild
. This'll significantly simplify xcbeautify's codebase, give users more information, and more closely matchxcodebuild
's raw output.Testing
Test 1
Test 2
Example Output
Old
New