Appium+python Automation 22-appium Desktop "Reprint"

Appium Desktop

Official documents of the original flavor

Appium Desktop is an open-source application for Mac, Windows, and Linux that provides the power of Appium Automation servers in a beautiful, flexible UI. It is a combination of some of the tools associated with Appium:

The graphical interface of the Appium server. You can set options, start/Stop servers, view logs, etc... You also do not need to use NODE/NPM to install Appium because the node will be bound to the Appium desktop when it is run.

You can use an inspector to view the elements of an application, understand their basic information, and interact with them in basic. This is a way to learn appium, or a way to learn about your application, so you can write tests for it.

Download Appium Desktop

You can always find the latest release version on GitHub on the publishing page.

If you're on Windows or MacOS, the Appium desktop will automatically provide you with the latest version of the app. If you're having trouble updating, simply remove or uninstall the app and download it again from the link above.

Note that the Appium desktop is not the same as Appium. The Appium desktop is a graphical interface that uses additional tools. Appium Desktop is published on its own cadence, it has its own version control system. If you are reporting problems with the Appium desktop, be sure to include the version of the Appium desktop and the version of the Appium server used (see below).

If you are on MacOS, you need to install Appium desktop, copy from downloaded DMG files to your own file system (the best place is the "Applications" folder). Running Appium on the attached DMG itself is not supported and will not work.

Known Issues

• Automatic Update no HTTPS://GITHUB.COM/APPIUM/APPIUM-DESKTOP/ISSUES/74)

Instructions for use

These instructions assume that you are already familiar with the Appium and appium-related concepts. If you have a new understanding of Appium, please visit Appium.io to read our introductory materials.

This app provides a convenient way to download and run the Appium Automation server, as well as a tool to check your Android or iOS apps. The following sections describe a variety of features.

Simple setup of the Server Start window

When you open the Appium desktop, you will be welcomed by the Server Startup window. The basic option is to start a appium server with all the default values and capabilities to modify the host and port. The Start button will also let you know which version of the Appium server you are running, which is useful for reporting problems to the Appium team.

Advanced options

By clicking on the "Advanced" tab, you will be able to set all the flags that are available in the Appium server. This is for advanced users who have consulted the Appium documentation for modifications.

Server Presets

If you use the Advanced Server option, you have the ability to save the configuration for later use. Simply save the Presets on the Advanced tab and then you can recall and start the server from the Preferences tab.

The Server Console Output window

After you start the server, it starts on the host and port you specify, and opens a new window that displays the server log output.

It is quite simple that no real interaction is possible, beyond the use of buttons to stop the server. You can also copy and paste these logs this window is useful when reporting appium issues. Another button is available: "Start a new session." Clicking this will open a new session window allowing you to start a check session of the server that is currently running.

The New Session window

The new session window allows you to build the functionality you need for a set of Appium to start a appium session. You can initiate an objection to a meeting that is currently running the Appium Desktop Server (default), or you can start a session for a variety of other endpoints.

Because you do not need to run the Appium desktop on your own server, you can get a new session window without starting the Appium desktop server. Simply go to "file" (Windows/linux) or "Appium" (MAC) and select "New Session ...", which opens a new session window without having to start the local server. In this scenario, attaching to the local server is disabled.

Appium Endpoints

The following are the options for starting a session for a non-local appium server:

• Custom Host/Port configuration: This is useful if you want to run a Appium server on another machine in your network.

If you can't access the iOS emulator on your machine, you can use your sauce Labs account to start a appium session in the cloud.

• Testobject: You can also use Testobject which is a true device-based examiner meeting of the real device cloud.

To set these options, it should be simple. Simply enter your details in the input field.

Desired capabilities

The concept of not being familiar with the required competencies, or the need for the concepts you need to have various types of appium sessions should consult the application documentation.

The Appium desktop does not restrict you from creating the required functional methods in any way, nor does it validate them for you. It just provides a good UI to enter them and save them for later use.

The expected features tab below, you can use form fields and the "+" button to enter multiple required capabilities. You will also see a representation of the resulting JSON, which is actually sent to the Appium server.

This can be useful for verifying your functionality, or for reporting problems when copying and pasting. Once you have set the ability you want, you may want to save them so that you can run the same type of session later.

Just click on the "Save as ..." button to give your ability a name. You can access it under Save to use the ability Settings tab for post-editing or Session initiation. After setting up the server type and features, click Start Session to start the Appium desktop.

Attach to an Existing Session

The following is the option to start a session for a non-local appium server: The required feature is how to configure the Appium session. They tell the Appium server that you want to automate the platforms and applications. If you are unfamiliar with the concept of required competencies, or need concepts you need to have all types of

The Appium session function should consult the application documentation. The Appium desktop does not restrict you from creating the required functional methods in any way, nor does it validate them for you. It just provides a good UI to enter them and save them for later use. The expected "Features" tab below, you can

Use the form fields and the "+" buttons to enter multiple required forces. You will also see a representation of the resulting JSON, which is actually sent to the Appium server. This can be useful for verifying your functionality, or for reporting problems when copying and pasting. If you click on the "Attach to Session ..." tab, you can

To select an existing session from the currently running list of sessions to the server of your choice, or you can enter the session ID of the currently running session. The meeting should run the server details specified in the Server type section above. Because the inspector is just one, it may be attached to an existing

Session Appium Client. This can be useful for testing if you want to debug the middle part of a run. When you exit the inspector window for an existing session, the Appium desktop does not exit the session as usual.

The Inspector

The inspector is a visual representation of the state of the application that has the ability to perform certain interactions in the application Appium.

Appium sessions may take some time to load, especially if you are waiting patiently on the cloud service. When the session loads, your application's screen will appear on the left. You can use the mouse in your application to work with various UI elements

See them stressed. In the middle of the inspector window is the hierarchy of your application, expressed as XML. You can navigate the elements in this tree screen view by clicking it or by clicking it. Then they will be emphasized. When an element is highlighted, its information is displayed in the detail view

On the right side of the inspectors. This detail view includes the potential to take action on elements, as well as the table of element attributes. These properties are valuable in determining how elements are accessed using a specific appium targeting strategy. Select an element, you can also "click" the element, or "Send key" to the element (such as

It is a text field). When you use an element to perform such an operation, the inspector sends a command to Appium, which executes it. If the action succeeds, that is the new screen will be generated, you should see the updated status and XML your application, and if it does not succeed, you will

Have the opportunity to see the error message. The top of the inspector window contains a small toolbar with an icon that represents the ability to take certain actions in the Inspector: return (called "Driver.back") Refresh (refresh source and screen) * Start recording (turn on the recorder and review the next section for more

Information) to exit the session (call "Driver"). Exit and close the inspector

The Recorder

Appium's desktop has a very basic action recorder, that is, the watch uses the Appium desktop operation, and displays the language and the framework's specific functions to represent the code of these operations. You can then copy and paste the code into the appropriate Appium client code in your code and use it for testing.

NB: The goal of the recorder is not to produce a production-ready test code. It is designed to help explore the tools of the Appium API and demonstrates how to implement certain automation behaviors that correspond to specific method invocation languages and appium libraries. In short, it is a learning tool, not a robust

Code generation features, which should be used in this way. When you start recording, the inspector displays an extra window:

At first, the logger did not display any code. You have to eat something first, like finding an element in the hierarchy, then clicking it, or sending a keystroke. When you do this, the code appears in the record window, as opposed to the specific language and frame that you selected

You can adjust it in the drop-down menu in the upper-right corner of the record:

You can use the appropriate buttons to copy this code to the Clipboard in the upper-right corner of the Sound Recorder. Note that by default it shows a simple line of code that corresponds to the specific action you take-in general, you cannot paste these lines into an empty text file to run the code. To be on behalf of

Code to run the Appium test script, you need to have a variety of test script attachments (such as the Appium client library) to be installed, this script template file (such as instantiating a driver and initialization session) is a gift. To display this additional code, you can click "Show boilerplate"

Button. Using the boilerplate code shown, you can copy and paste the code into a new file and run it.

As we add more languages, the power of the recorder will continue to increase, the framework, and the operation on the Appium desktop.

Conclusion

This is what you need to know all you need to know to use Appium Desktop success!

Remember, Appium desktop is not a substitute for understanding appium it is itself a handy tool for using Appium desktop on your application, and an inspector to check your application.

Reporting issues and requesting Features

Appium Desktop is open source, we use GitHub to track problems. Please simply report our problem tracker) (https://github.com/appium/appium-desktop/issues). We will try to determine if the problem you are reporting is related to Appium desktop

Appium server. If it is not related to the Appium desktop, we will close the issue and ask you to open a common Appium problem Tracker (https://github.com/appium/appium/issues) on Main (Appium). Please save

You and we have valuable time to figure out what your problem experience is related to Appium desktop, or a general appium problem. You can do this by looking at whether the problem is regenerated with the problem appium command-line server. If it is, go straight to Appium.

Report the issue tracker. Do you have a feature request? Follow the same process and submit a question to it for proper tracking! (If it is a special request, you can do it here for Appium desktop, or Appium's main tracker, if more general is required).

Advanced Topics and Troubleshootingappium can ' t detect environment variables on MAC

Appium uses environment variables such as "Android_home" and relies on the various binaries in your "path" and so on. When running from the command line, in an environment where these variables are set appropriately, Appium has

It's no problem to pick them up. However, the Appium desktop does not run in the shell or the command-line environment, so by default it cannot access the environment variables that you set in the Shell startup script or profile. We'll use this to solve this problem.

SHELL-ENV package The environment variables defined in the shell. This package seems to be sure, however, common init scripts, such as "~/". BASHRC ', ' (~/. Bash_profile ', ' ~/. ZSHRC ". If you set the Appium ring in a different way

settings, you need to create a default init script and set up your environment as well as some variables, so the Appium desktop will be able to successfully pick them up.

About warnings that exist in a read-only file system

This may mean that you try to start the Appium desktop image from the downloaded disk (". DMG file). This is not a supported mode for running Appium desktops. To properly install the Appium desktop, copy the application from disk image to your local file system,

To a location similar to "/application". Then, run the application from this new location.

Developer directive

Want to sponsor a Appium desktop? It's great! Please go to our (donation) for information on how to set up the development environment (contribution. MD) and submit changes back to the project.

Appium+python Automation 22-appium Desktop "Reprint"