GitLab Quality Department, 10 Dec 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: How to use GitLab QA to test a self-managed GitLab instance

Description

This video is a quick demonstration of how to use the GitLab QA orchestration tool to run our end-to-end tests against a self-managed instance.

Example of command used:

gitlab-qa Test::Instance::Any EE:13.6.2-ee http://gitlab.test -- qa/specs/features/browser_ui/3_create/merge_request/create_merge_request_spec.rb

For more info see:

GitLab QA README: https://gitlab.com/gitlab-org/gitlab-qa/-/blob/master/README.md
GitLab QA Scenarios: https://gitlab.com/gitlab-org/gitlab-qa/-/blob/master/docs/what_tests_can_be_run.md
E2E info for GitLab developers: https://docs.gitlab.com/ee/development/testing_guide/end_to_end/
Orchestrated end-to-end tests at GitLab - Part 1: https://youtu.be/wWC7r3l0u1Y
Orchestrated end-to-end tests at GitLab - Part 2: https://youtu.be/U8zCle_Up6I
How to run an end-to-end test interactively (debugging): https://youtu.be/SO2U8gpLSeM
Quality Department Handbook: https://about.gitlab.com/handbook/engineering/quality/

A

Hi folks, I'm markup here software engineering test and I'm going to show you how to use gitlab qa a test orchestration tool to run our end-to-end tests against a self-managed instance. So gitlab qa. As I mentioned, it's a test orchestration tool. If you want to learn more about the tool, what it does, how it does it all the different options or the different tests you can run and then please check out the links in the video notes so for now.

A

Firstly, I've exported the credentials for the user that the test is going to run as then, I execute the gitlab qa command tell it to run the test instance, any scenario that tells it to run our standard test suite and the ee option does it to use the enterprise edition tests, and I have the instance running at gitlab.test and so gitlab qa pulls the docker image that contains the tests and then executes the command. That starts the tests running in a docker container.

A

I'm going to stop that because there are about 276 tests and I don't want to keep you watching. While I wait for all of those to run so, instead, what I'll do is I'll run one specific test, so there's two things: I've changed here. One I've added a version to the release here, so I'm telling the tool to run the tests as they existed when version 13.6.2 was released.

A

So this is what you'll want to do if you're running tests against a particular version, you'll tell it to run the tests from the version that you have installed and I've also told you to run the test from one specific file. So that's only run the two tests that are in this spec file to test that we can create the merge request.

A

The tool uses our spec, so I can pass any other aspect commands any other aspect options. So in this case I'm telling it to run the tests that are tagged smoke. So we have a subset of tests that we use as smoke tests and we can run those specifically and that's something that won't take quite as long still uh a few minutes. So I'll show you the same thing that I've run here again: yeah five, almost six minutes to run the smoke test.

A

The command I used here was the same except I told it to run the test against our staging environment yeah and there the smoke tag and you can see 19 tests around two appending. So these two uh just in quarantine. We can see that so yeah. Those are tests that we're not currently running all right but yeah. That's a quick rundown. uh As I said, the links contain more information, but uh yes, please check out those links and uh get in contact with us in quality. If you have any questions thanks.