@mikhailnersesov thatās a good question!
It depends on what do we understand as āmobile automationā in the question.
- Real mobile applications?
- Hybrid apps?
- Mobile websites?
If we include mobile websites then Playwright could be useful!
@mikhailnersesov thatās a good question!
It depends on what do we understand as āmobile automationā in the question.
If we include mobile websites then Playwright could be useful!
It would be interesting to run other polls to tease out things like which tools people use for which tasks. Using a hammer is fine if all you test is just a web-wrapper-app. But many testers are trying to use the āhammerā tool, when in fact they do have to dive into WebDriverIO and into ideviceinstaller library as well as adb, and those 2 tools are completely omitted from this graph.
TestArchitect supports mobile native apps and web apps. https://testarchitect.com
disclose: posted by the TestArchitect team
Thereās no info about apps support in pricing table, any documentation to back it up?
btw. You should probably disclose that youāre working for the company.
Thank you for the reply. The details of apps support can be found here Supported Platforms
(btw, added disclose)
Oh, so youāre just using Appium. Yeah that makes a lot of sense. Thanks!