GuiBrowser/en: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Ani (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „ == Start Windows applications == :In general, no applications are started via the GuiBrowser (*). Rather, it establishes connections to running applications. …“) |
Ani (Diskussion | Beiträge) |
||
| Zeile 6: | Zeile 6: | ||
:To start the application, it is best to create a new block in the test-suite, name it e.g. "Start Client2" and insert one of the existing "OS-Starte-Process" blocks (from the standard library). |
:To start the application, it is best to create a new block in the test-suite, name it e.g. "Start Client2" and insert one of the existing "OS-Starte-Process" blocks (from the standard library). |
||
[[Datei:faq_guibrowser1.png|600px]] |
|||
Version vom 12. April 2019, 12:58 Uhr
Start Windows applications[Bearbeiten]
- In general, no applications are started via the GuiBrowser (*). Rather, it establishes connections to running applications.
- If you have already started your client on your computer, select "Windows Automation" in the GuiBrowser when connecting and leave the default settings in the Connect dialog (localhost, 9988, 30). Then a process is started (WindowsAutomation Client) which connects expecco to your desktop. After connecting, you will see all applications on your computer in the GuiBrowser under the WindowsAutomation connection.
- To start the application, it is best to create a new block in the test-suite, name it e.g. "Start Client2" and insert one of the existing "OS-Starte-Process" blocks (from the standard library).
