Skip to content
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

Make sure the BugReportScreen allows the user to retry if sending fails. #3012

Merged
merged 2 commits into from
Jul 8, 2024

Conversation

pixlwave
Copy link
Member

@pixlwave pixlwave commented Jul 8, 2024

Fixes #2974

@pixlwave pixlwave requested a review from a team as a code owner July 8, 2024 09:05
@pixlwave pixlwave requested review from Velin92 and removed request for a team July 8, 2024 09:05
Comment on lines -128 to -134
XCTAssertEqual(mockService.submitBugReportProgressListenerReceivedArguments?.bugReport.userID, "@mock.client.com")
XCTAssertEqual(mockService.submitBugReportProgressListenerReceivedArguments?.bugReport.deviceID, nil)
XCTAssertEqual(mockService.submitBugReportProgressListenerReceivedArguments?.bugReport.text, "")
XCTAssertEqual(mockService.submitBugReportProgressListenerReceivedArguments?.bugReport.includeLogs, true)
XCTAssertEqual(mockService.submitBugReportProgressListenerReceivedArguments?.bugReport.canContact, false)
XCTAssertEqual(mockService.submitBugReportProgressListenerReceivedArguments?.bugReport.githubLabels, [])
XCTAssertEqual(mockService.submitBugReportProgressListenerReceivedArguments?.bugReport.files, [])
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These didn't really seem necessary for testing what happens when sending fails as they're already checked on the success path.

@pixlwave pixlwave added the pr-bugfix for bug fix label Jul 8, 2024
Copy link

github-actions bot commented Jul 8, 2024

Warnings
⚠️ Some of the commits are missing ticket numbers. Please consider squashing all commits that don't have a tracking number.

Generated by 🚫 Danger Swift against 1069bd9

@pixlwave pixlwave force-pushed the doug/retry-rageshakes branch from 17df053 to b5891c1 Compare July 8, 2024 12:00
@pixlwave pixlwave force-pushed the doug/retry-rageshakes branch from b5891c1 to 1069bd9 Compare July 8, 2024 12:10
Copy link

sonarqubecloud bot commented Jul 8, 2024

Copy link

codecov bot commented Jul 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.73%. Comparing base (bf9e1d6) to head (1069bd9).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3012      +/-   ##
===========================================
- Coverage    77.78%   77.73%   -0.05%     
===========================================
  Files          695      695              
  Lines        53851    53849       -2     
===========================================
- Hits         41886    41858      -28     
- Misses       11965    11991      +26     
Flag Coverage Δ
unittests 68.58% <100.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pixlwave pixlwave merged commit 74a078b into develop Jul 8, 2024
10 checks passed
@pixlwave pixlwave deleted the doug/retry-rageshakes branch July 8, 2024 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-bugfix for bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

If a rageshake upload fails, there is no way to retry
2 participants