... | ... | @@ -44,13 +44,15 @@ If you think the test failure represents a bug, open an issue against the releva |
|
|
|
|
|
## How to update a test
|
|
|
|
|
|
**FIXME: this workflow doesn't yet work. You will need to SSH into openqa.gnome.org and manually update its clone of openqa-needles.git. See https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/409 and https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/408**
|
|
|
|
|
|
Test scripts live in [gnome-build-meta](https://gitlab.gnome.org/GNOME/gnome-build-meta/) in the `openqa/` folder. If you need to modify the test itself, create a branch of gnome-build-meta as normal with your change. The test pipeline will run with your version of the tests, and once it passes we can merge this to master.
|
|
|
|
|
|
Needles live in [openqa-needles](https://gitlab.gnome.org/GNOME/openqa-needles) folder, and the `master` branch is used by all tests. Multiple needles can have the same name, and OpenQA will pass a test if any one needle matches. If you need to modify a needle, the workflow is to create a new one, and the preferred way is to use OpenQA's [developer mode](http://open.qa/docs/#_developer_mode) as follows.
|
|
|
|
|
|
1. Ensure you have 'operator' permissions on OpenQA - ask an admin or open an issue if you don't have this.
|
|
|
2. Open the failed test in the Web UI.
|
|
|
3. Click the 'Create new needle' button to open the developer mode page
|
|
|
3. Click the 'Create new needle' button (pin with a green plus) to open the developer mode page.
|
|
|
4. Use the 'Screenshot and Areas' section to create a new needle
|
|
|
* Usually you 'Take image from' the screenshot and 'Copy areas from' the most recent needle.
|
|
|
* Click and drag on the screenshot to create, move and resize match areas
|
... | ... | |