| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [QA] Improve the fork scenario to take a username and password instead of ↵qa-staging-2 | Rémy Coutable | 2018-08-20 | 1 | -0/+25 |
| | | | | | | | | | always creating a new user Fixes https://gitlab.com/gitlab-org/quality/staging/issues/2. Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | [QA] Add a new scenario to test GitHub import | Rémy Coutable | 2018-07-06 | 1 | -0/+23 |
| | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | GitLab QA: Add GITLAB_USER_TYPE to support different login types (e.g. ↵sh-add-login-types-qa | Stan Hu | 2018-02-11 | 1 | -0/+21 |
| | | | | | | | | standard, LDAP) GITLAB_USERNAME and GITLAB_PASSWORD may be specified for an LDAP login, but QA scenarios may need to know which type it is in order to log in successfully. | ||||
| * | Add ability to drive the API in QA specs | Brett Walker | 2018-01-23 | 1 | -7/+1 |
| | | |||||
| * | Resolve "Allow QA tests to run with `CHROME_HEADLESS=false`" | Brett Walker | 2018-01-08 | 1 | -0/+64 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |