Skip to content

Conversation

@tomerqodo
Copy link

@tomerqodo tomerqodo commented Jan 21, 2026

Benchmark PR from qodo-benchmark#240


Note

Refactors the XCUITest suite for Swift 6 concurrency and main-actor safety.

  • Convert setUp/tearDown across Base and all test classes to async throws, invoking try await super.setUp()/tearDown(); adjust platform-specific subclasses accordingly
  • Add @MainActor to UI-bound globals, helpers, screen graph/navigation registration functions, and utilities (e.g., BaseTestCase globals, Today Widget selectors, navigation helpers, A11yUtils, FxScreenGraph files)
  • Minor setup ordering/initialization tweaks (e.g., FeatureFlaggedTestBase.setUp() call order, launch arguments placement) and small cleanups; no functional test logic changes intended

Written by Cursor Bugbot for commit 5d69751. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

continueAfterFailure = false
setUpExperimentVariables()
setUpApp()
setUpExperimentVariables()
Copy link

Choose a reason for hiding this comment

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

Method call order swapped causes nil unwrap crash

High Severity

The order of setUpApp() and setUpExperimentVariables() has been accidentally swapped during refactoring. setUpApp() calls addLaunchArgument(jsonFileName: jsonFileName, featureName: featureName), which requires these implicitly unwrapped optionals (String!) to be set first. Since setUpExperimentVariables() is now called after setUpApp(), accessing the nil values will cause a runtime crash.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants