Suacelab Integration #248
Unanswered
Ayushkumarjob
asked this question in
Q&A
Replies: 1 comment
-
|
Hey @Ayushkumarjob , thank you for this question. Right now mobile-mcp requires that you have xcrun, adb, and go-ios. Neither of these would work with Sauce Labs' solution. You can however use their virtual-usb solution. In the future, if any of these providers have an API that can be used to mimic some/all of mobile-mcp functionality, then integration would be possible. Regardless, can you please hop onto our Slack (https://mobile-next.slack.com/ssb/redirect) and ping me directly? I'd like to talk to you about this 🙏 . |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team,
I'm currently working on integrating mobile-mcp into my testing CI/CD pipeline that uses SauceLabs for remote device execution.
I have a couple of questions:
Does mobile-mcp currently support SauceLabs integration? Specifically, can it connect to remote devices hosted on SauceLabs cloud infrastructure?
If not currently supported, are there plans to add SauceLabs (or other cloud device providers like BrowserStack) in the future roadmap?
For context, we're using:
CI/CD: Looper
Devices: SauceLabs cloud simulators/emulators
Goal: Replace or complement Appium setup with mobile-mcp's natural language capabilities
Any guidance or insights would be greatly appreciated!
Thanks,
Ayush
Beta Was this translation helpful? Give feedback.
All reactions