Skip to content

[module_test_ios] On UITests add an additional tap on the application before tapping the element#90149

Merged
fluttergithubbot merged 1 commit intoflutter:masterfrom
cyanglaz:module_test_ios_delay
Sep 17, 2021
Merged

[module_test_ios] On UITests add an additional tap on the application before tapping the element#90149
fluttergithubbot merged 1 commit intoflutter:masterfrom
cyanglaz:module_test_ios_delay

Conversation

@cyanglaz
Copy link
Contributor

Adding an additional self.app tap see if it fixes the flake. If this doesn't, we can try to add a delay.

#89175

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I signed the CLA.
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@flutter-dashboard flutter-dashboard bot added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Sep 15, 2021
@google-cla google-cla bot added the cla: yes label Sep 15, 2021
[self waitForExpectationsWithTimeout:30.0 handler:nil];
// Sometimes, the element doesn't respond to the tap, it seems an XCUITest bug. Trying tap
// the app first to fix it.
[self.app tap];
Copy link
Member

Choose a reason for hiding this comment

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

Does this tap on a random spot in the app?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

https://developer.apple.com/documentation/xctest/xcuielement/1618666-tap?language=objc "a hittable point", so I guess a random spot. Are you worried about this hitting other elements. I think the XCUITest framework should somehow find a spot that is not covered by other elements.

Copy link
Member

Choose a reason for hiding this comment

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

I'm suspicious that this won't cause problems and tap other elements, but let's try it, I don't have any better ideas.

Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

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

LGTM

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

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants