... | ... | @@ -92,11 +92,14 @@ can adapt an existing test. Here are some we know of: |
|
|
|
|
|
When adding or debugging tests you probably don't want to wait for a full Gitlab CI pipeline. You can run the test suite locally if you don't mind doing some preparations. You will need Docker / Podman to run the tests, and `jq`.
|
|
|
|
|
|
1. Clone [gnome-build-meta](https://gitlab.gnome.org/GNOME/gnome-build-meta/) repo.
|
|
|
1. Clone [openqa-tests](https://gitlab.gnome.org/GNOME/openqa-tests/) repo.
|
|
|
|
|
|
2. Clone [openqa-needles](https://gitlab.gnome.org/GNOME/openqa-needles/) repo, link or rename it to be inside gnome-build-meta folder at `./openqa/needles`.
|
|
|
2. Clone [openqa-needles](https://gitlab.gnome.org/GNOME/openqa-needles/) repo, link or rename it to be inside openqa-tests folder at `./needles`.
|
|
|
|
|
|
3. Get the `installer.iso` file you want to test. The simplest way is to build the 'iso-installer-x86_64` job in Gitlab CI, then use the 'Job artifacts' menu to download it.
|
|
|
3. Get the `installer.iso` file you want to test.
|
|
|
|
|
|
* If you ran the `iso-installer-x86_64` CI job, it will be available as a CI artifact
|
|
|
* The `s3-image` job uploads to https://os.gnome.org/, for a pipeline #123 you would download: https://os.gnome.org/download/123/gnome_os_installer_123.iso
|
|
|
|
|
|
4. Get the `vars.json` file from a successful OpenQA run. Visit https://openqa.gnome.org/tests to find the latest successful run, then visit the 'Logs & Assets' tab and download `vars.json`.
|
|
|
|
... | ... | |