Loading content
Appium is an open-source test automation framework for running UI tests on native, hybrid and mobile web apps for iOS and Android. It uses WebDriver protocols to enable cross-platform test scripts in common programming languages. Appium supports real devices, emulators and integration with CI/CD and cloud device farms.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Appium is an open-source ecosystem for automating mobile, desktop, and some TV applications through WebDriver-compatible interfaces.
Appium was shaped by Dan Cuellar and later Jonathan Lipps to make mobile UI automation accessible through a cross-platform WebDriver interface. The project grew from iPhone automation work and joined the JS Foundation in 2014.
Appium acts as a translator: a test sends standard WebDriver commands, and a suitable driver turns them into native actions on the target platform. Test code stays largely stable while drivers and platform details vary.
A driver maps WebDriver commands to a concrete platform.
Tests perform interactions repeatably.
One protocol supports multiple target systems.
Appium helps verify critical mobile flows repeatedly on real devices or emulators. UI tests remain sensitive to layout and platform changes and do not replace unit or domain tests.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.