QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

# Gitlab Need To Know

The [Gitlab QA SLE Functional repo](https://gitlab.suse.de/qsf-y/qa-sle-functional-y) is used to create the job group definition for SLE15 on openqa.suse.de. 

## How are the group definitions organized?

The definitons are stored under the `JobGroups` directory.

### Test suites

The file `test_suites.yaml` holds the test suites definitions in alphabetical order. 

Every test suite has an **anchor** that has the name of the test suite:

~~~ yaml

  generic_testsuite: &generic_testsuite

    descriptin: >-

      just for demonstation

~~~

### Job group definitions

The directory `SLE15` contains the architecture specific parts of the job groups file and the defaults.

Test suites in the `../test_suites.yaml` file are referenced with an **alias** there:

~~~ yaml

x86_64:

  sle-15-SP4-Full-x86_64:

    - generic_testsuite

        <<: *generic_testsuite

        settings:

~~~

## Fork & Merge workflow

When you want to change the definitions, you need to

* [fork](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) the repository. **Important**: After forking the repository you need to [define the variables](https://docs.gitlab.com/ee/ci/variables/) APIKEY and APISECRET and fill them with your keys for openqa.opensuse.de! The variables will be needed in the CI workflow.

* create a branch for your edits

* do the editing and commit the changes

* create a merge request. The merge request will trigger the CI pipeline and the test part of the pipeline relies on the variables (see above) that you need to set after forking the repository.