Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
32c30203
Commit
32c30203
authored
Oct 05, 2017
by
Robert Speicher
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Use the default password from the GDK's root user
[ci skip]
parent
6ba96149
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
24 additions
and
8 deletions
+24
-8
qa/README.md
qa/README.md
+23
-7
qa/qa/runtime/user.rb
qa/qa/runtime/user.rb
+1
-1
No files found.
qa/README.md
View file @
32c30203
#
#
Integration tests for GitLab
#
GitLab QA -
Integration tests for GitLab
This directory contains integration tests for GitLab.
It is part of
[
GitLab QA project
](
https://gitlab.com/gitlab-org/gitlab-qa
)
.
It is part of
the
[
GitLab QA project
](
https://gitlab.com/gitlab-org/gitlab-qa
)
.
## What
GitLab QA is
?
## What
is it
?
GitLab QA is an integration tests suite for GitLab.
...
...
@@ -20,18 +20,34 @@ against any existing instance.
## How can I use it?
You can use GitLab QA to exercise tests on any live instance! For example, the
follow
call would login to the local GitLab
instance and run all specs in
follow
ing call would login to a local [GDK]
instance and run all specs in
`qa/specs/features`
:
```
GITLAB_USERNAME='root' GITLAB_PASSWORD='5iveL!fe' bin/qa Test::Instance http://localhost
bin/qa Test::Instance http://localhost:3000
```
You can also supply a specific tests to run as another parameter. For example, to
### Running specific tests
You can also supply specific tests to run as another parameter. For example, to
test the EE license specs, you can run:
```
EE_LICENSE="<YOUR LICENSE KEY>" GITLAB_USERNAME='root' GITLAB_PASSWORD='5iveL!fe' bin/qa Test::Instance http://localhost qa/ee
EE_LICENSE="<YOUR LICENSE KEY>" bin/qa Test::Instance http://localhost qa/ee
```
### 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
](
https://gitlab.com/gitlab-org/gitlab-qa#supported-environment-variables
)
.
[
GDK
]:
https://gitlab.com/gitlab-org/gitlab-development-kit/
qa/qa/runtime/user.rb
View file @
32c30203
...
...
@@ -8,7 +8,7 @@ module QA
end
def
password
ENV
[
'GITLAB_PASSWORD'
]
||
'
test1234
'
ENV
[
'GITLAB_PASSWORD'
]
||
'
5iveL!fe
'
end
end
end
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment