kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/qa
History
Rémy Coutable dcb79741a1 Merge branch 'qa/gb/ci-cd-qa-pipelines' into 'master' 
CI/CD end-to-end tests

Closes gitlab-qa#18

See merge request gitlab-org/gitlab-ce!16619
2018-01-25 09:55:39 +00:00
..
bin Fix bootable scenario arguments for OptionParser 2017-11-10 11:11:22 +00:00
qa Merge branch 'qa/gb/ci-cd-qa-pipelines' into 'master' 2018-01-25 09:55:39 +00:00
spec Merge branch 'master' into qa/gb/ci-cd-qa-pipelines 2018-01-23 13:04:58 +01:00
.gitignore Make it possible to define global scenario attributes 2017-11-09 11:53:57 +00:00
.rspec
Dockerfile Use new Ruby version 2.4 in GitLab QA images 2017-12-14 11:21:57 +01:00
Gemfile Add ability to drive the API in QA specs 2018-01-23 10:23:23 +00:00
Gemfile.lock Add ability to drive the API in QA specs 2018-01-23 10:23:23 +00:00
qa.rb Merge branch 'master' into qa/gb/ci-cd-qa-pipelines 2018-01-23 13:04:58 +01:00
README.md Add a note about GitLab QA page objects validator to docs 2018-01-12 11:04:41 +01:00

README.md

GitLab QA - Integration tests for GitLab

This directory contains integration tests for GitLab.

It is part of the GitLab QA project.

What is it?

GitLab QA is an integration tests suite for GitLab.

These are black-box and entirely click-driven integration tests you can run against any existing instance.

How does it work?

  1. When we release a new version of GitLab, we build a Docker images for it.
  2. Along with GitLab Docker Images we also build and publish GitLab QA images.
  3. GitLab QA project uses these images to execute integration tests.

Validating GitLab views / partials / selectors in merge requests

We recently added a new CI job that is going to be triggered for every push event in CE and EE projects. The job is called qa:selectors and it will verify coupling between page objects implemented as a part of GitLab QA and corresponding views / partials / selectors in CE / EE.

Whenever qa:selectors job fails in your merge request, you are supposed to fix page objects. You should also trigger end-to-end tests using package-qa manual action, to test if everything works fine.

How can I use it?

You can use GitLab QA to exercise tests on any live instance! For example, the following call would login to a local GDK instance and run all specs in qa/specs/features:

bin/qa Test::Instance http://localhost:3000

Writing tests

  1. Using page objects

Running specific tests

You can also supply specific tests to run as another parameter. For example, to run the repository-related specs, you can execute:

bin/qa Test::Instance http://localhost qa/specs/features/repository/

Since the arguments would be passed to rspec, you could use all rspec options there. For example, passing --backtrace and also line number:

bin/qa Test::Instance http://localhost qa/specs/features/login/standard_spec.rb:3 --backtrace

Overriding the authenticated user

Unless told otherwise, the QA tests will run as the default root user seeded by the GDK.

If you need to authenticate as a different user, you can provide the GITLAB_USERNAME and GITLAB_PASSWORD environment variables:

GITLAB_USERNAME=jsmith GITLAB_PASSWORD=password bin/qa Test::Instance https://gitlab.example.com

All supported environment variables are here.