Skip to content

Fix flaky spec: explicitly set group names

Rutger Wessels requested to merge 444846-explicitly-name-groups into master

What does this MR do and why?

This test is flaky and fails with:

  1) searching groups Query groups(search) includes accessible private groups ordered by name
     Failure/Error: expect(names).to eq([public_group.name, private_group.name])
       expected: ["group99", "group100"]
            got: ["group100", "group99"]

These names are generated names using a FactoryBot sequence. So if the groups are created in a different order, the names are no longer in order. By using Group A and Group B, the order should be guaranteed.

Related to #444846 (closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports