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

Automation framework? #526

Open
bootstraponline opened this issue May 14, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@bootstraponline
Copy link
Contributor

commented May 14, 2019

Is there any information you can share on what UI automation framework Facebook is using with idb now that WebDriverAgent is archived?

facebookarchive/WebDriverAgent#1118

@lawrencelomax

This comment has been minimized.

Copy link
Contributor

commented May 22, 2019

We're using idb directly for Simulators. The idb ui family of commands provides primitives for tapping and getting UI hierarchies which is enough to write a UI testing framework on top. XCUI basically operates in a similar way, but it has more direct access to hierarchies. This is all about optimizing performance and throughput but also mirrors how we do things for Android.

For devices we do things a little differently and have launch plain XCUITests with idb xctest run ui. This is just running a regular UI test, except this also works for devices.

@bootstraponline

This comment has been minimized.

Copy link
Contributor Author

commented May 22, 2019

For devices we do things a little differently and have launch plain XCUITests with idb xctest run ui. This is just running a regular UI test, except this also works for devices.

To clarify, FB engineers are writing iOS UI device tests using the XCUITest APIs directly? There's no secret sauce reverse engineered magic like WDA? Or even a wrapper framework that abstracts away XCUITest?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.