action #152296
closedOptimize gitlab repo CI
0%
Description
Currently, our gitlab repo for openqa job groups is running on a simple checks CI. There is a yamllint check, a check for schedule and data files existence and then the openqa-cli command that checks if it can post the job group . We should make some tests to see if the above checks provide failure and pass when expected.
Note: A specific scenario to look into is if we want to move a test suite to another Job group, within the repo , one MR with two commits, will it pass or will it provide error that the test suite already exists in another Job group?
Acceptance criteria
- Run tests for different scenarios to verify the CI functionality
- Open follow-up tickets for any improvements if needed.
Updated by JERiveraMoya 3 months ago ยท Edited
- Target version deleted (
Current)
we plan to have all our test suite in control version, so all the test suite should have testsuite: null and use anchor and alias, unlikely we need this for moving test suite. That problem described above I think only appears when the test suites are in db/ui. Please @syrianidou_sofia reject this ticket or share more specific example where this could be useful in current state of the repo, or what other improvement you have in mind if that was only an example.