tests: Reenable testAddAndRemoveData #2533
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## 8.0.0 #2533 +/- ##
==========================================
- Coverage 78.92% 78.79% -0.13%
==========================================
Files 241 241
Lines 22118 22129 +11
Branches 9767 9775 +8
==========================================
- Hits 17457 17437 -20
- Misses 4217 4243 +26
- Partials 444 449 +5
Continue to review full report at Codecov.
|
So by adding more tests the coverage went down? Doesn't make sense. |
Yeah, I also don't get this. Sometimes it's just bogus. |
kevinrenskers
added a commit
that referenced
this pull request
Dec 16, 2022
* 8.0.0: (31 commits) tests: Reenable testAddAndRemoveData (#2533) feat: support SENTRY_DSN environment var on macOS (#2534) Remove duplicate entry (#2532) fix: ARC issue for FileManager (#2525) feat: Add SwiftUI performance tracking (#2271) fix: Remove all permission checks (#2529) Remove the automatic `viewAppearing` span (#2511) Fix and reenable testANRDetected_UpdatesAppStateToTrue (#2526) fix: Don't add out of date context for crashes (#2523) ref: Rename isOOM to watchdog in Client (#2520) test: Fix disabled failing watchdog test (#2521) build(deps): bump github/codeql-action from 2.1.35 to 2.1.36 (#2516) Rename the watchdog option and integration (#2513) feat: Enable CaptureFailedRequests by default (#2507) test: Fix asserts for SentryCrashTestInstallation (#2500) meta: User interaction tracing enabled per default (#2506) ref: Rename OOM to Watchdog Terminations (#2499) feat: enableUserInteractionTracing is GA (#2503) build(deps): bump nokogiri from 1.13.9 to 1.13.10 (#2505) perf: Don't attach headers for SentryNoOpSpan (#2498) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I initially thought the test had failed twice, but it was actually only once. And the test failure wasn't a real test failure I think:
But absolutely nowhere is there any information on which assert failed, and how. But since the test only uses
XCTAssertEqualandXCTAssertNil, we should get proper failure messages.So I don't know why the test failed in https://github.com/getsentry/sentry-cocoa/actions/runs/3530734813/jobs/5923080490, but I don't think it's because the actual test function is flaky.
#skip-changelog