QA » openQA Project

I assume this is about test suites that are only used in one job group? We want to eliminate those anyway

Could be related, but it is behavior change and unaware(used to old things) user can be surprised.
For example I was adding new test suite to YAML schedule and editor complained about other not existing test suite.
It was easy to fix(just removed it), but it means that users don't expect it (to manually go over all job group definitions and delete/rename test suite).

The yaml config file is user input and we won't touch it. But what we can do is forbid deleting/renaming test suites if they are used.

coolo wrote:

The yaml config file is user input and we won't touch it. But what we can do is forbid deleting/renaming test suites if they are used.

We can point out the job group(s) the respective test suite is being used in. And as a side effect users will be more aware of where a test suite is being used rather than silently changing all affected job groups.

coolo wrote:

The yaml config file is user input and we won't touch it. But what we can do is forbid deleting/renaming test suites if they are used.

If I understand well, it means manually remove test suite from all YAML job groups, rename and add back again with new name.
Quite difference in action when you compare to non-yaml solution(almost one click action).

As I mentioned: the trend is to eliminate the need for frequent test suite changes

coolo wrote:

As I mentioned: the trend is to eliminate the need for frequent test suite changes

Despite the trend, sometimes changes are needed (sometimes even complex changes).
I should have checked the code & doc for this feature better before. If I had known this feature, I wouldn't have voluntarily changed it to yaml.

Is this incompatibility change documented somewhere?

pvorel wrote:

Is this incompatibility change documented somewhere?

This actually needs to be documented explicitly. The Job group editor section only mentions configuring a group in YAML, but it doesn't mention how this affects test suites. I would indeed suggest to cover this in this ticket as well.

Additions to the docs here https://github.com/os-autoinst/openQA/pull/2372