... | ... | @@ -52,7 +52,11 @@ We start off by creating our test class. |
|
|
self.driver.quit()
|
|
|
```
|
|
|
|
|
|
We'll also define some boilerplate setup logic. This will start the app org.kde.kcalc.desktop through its desktop file. You can also pass command lines to instead fork a process manually. For example you might start a Plasma applet with `"plasmawindowed org.kde.plasma.calculator"`.
|
|
|
We'll also define some boilerplate setup logic. This will start the app org.kde.kcalc.desktop through its desktop file. You can also pass command lines to instead fork a process manually. For example you might start a Plasma applet with `"plasmawindowed org.kde.plasma.calculator"`. Valid app options are:
|
|
|
|
|
|
- desktop file id: `desired_caps["app"] = "org.kde.kcalc.desktop"`
|
|
|
- command line: `desired_caps["app"] = "plasmawindowed org.kde.plasma.calculator"`
|
|
|
- pid: `desired_caps["app"] = "12356"` please note that you are in charge of ensuring that this pid actually terminates properly once your test is done!
|
|
|
|
|
|
Let's write our first test. A simple addition should do. To write selenium tests we need to tell the driver to find specific UI elements and interact with them (e.g. click them). There are a number of options for finding elements based on at-spi properties:
|
|
|
|
... | ... | |