LMR QA | Main | Importing a project and tagging Tests

This is part of the FY22 KR Large Merge Request.

I have added a resource creation method for importing an already exported Gitlab project. This is done through the browser ui. The file is stored inside the projects QA folder under fixtures. To be able to use already existing tests for large merge request testing, I have used a Scenario Argument that is set to true if we are using the tag can_use_large_setup. This is checked upon creating a merge request and in case the Argument is true, it uses the imported resource.

To mark tests that are ready to be used in large MR testing, one simply has to tag them with the keyword can_use_large_setup

What is not done

In this MR I am using a small project that I exported. This is due to two reasons. I am still waiting for the rights to export the chosen large MR project and, I believe that it is possible upon adding the correct project, that we might have to tweak some numbers on the wait timers for this, so it might not be a bad idea to do this in a separate MR.

Related links

• The main KR Issue: gitlab-com/www-gitlab-com#11448 (closed)
• The sample merge request: https://staging.gitlab.com/gpt/large_projects/gitlabhq1/-/merge_requests/8785
• Follow ups: #333925 (closed), #333929, #333926 (closed), #333926 (closed)