Aravindanath aravindanath

Appium 2.0

As described in the Appium 2.0 Epic, Appium needs to evolve from being a server which bundles many drivers to one which by default doesn't bundle any drivers, and instead provides an interface for retrieving and using drivers. Essentially, "Appium" will become:

A set of spec extensions to the WebDriver W3C protocol (eventually upstreaming those extensions to the official protocol)
A set of code libraries (like BaseDriver or jsonwp-proxy that make it easy to write Appium drivers)
A driver runner (this is what the main Appium package currently does); the difference is that drivers will not come bundled with the runner by default
A plugin interface based around command-level hooks
An API and CLI interface for retrieving and managing different versions of Appium-compatible drivers and plugins

	Hi All!

	I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future.
	Feel free to request any features you'd like to see, and I'll prioritize them accordingly.
	One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it.

	Here's the link to the repository: https://github.com/Pulimet/ADBugger

	App Description:
	ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups.