summaryrefslogtreecommitdiff
path: root/qa/spec/runtime
Commit message (Collapse)AuthorAgeFilesLines
* Log page actionsml-qa-loggingMark Lapierre2018-10-192-4/+47
| | | | | | | | | | | | | | | Override page object methods to log the actions taken by the methods before or after the action, as appropriate. Allow page object action logging to be turned on via a QA_DEBUG env var. Unlike CHROME_HEADLESS (and the soon to arrive VERBOSE), QA_DEBUG is false by default. QA_DEBUG is used instead of just DEBUG because that enables Selenium debug logging. Mask passwords entered into fields with a QA selector with 'password' in the name. Doesn't mask sensitive data entered into any other field.
* First iteration to allow creating QA resources using the APIRémy Coutable2018-10-174-14/+80
|
* Allow the registration e2e test to be skippedMark Lapierre2018-10-081-16/+24
| | | | | | | If SIGNUP_DISABLED is true skip any tests with a context :skip_signup_disabled. The context is set for the registration tests. This allows the tests to be skipped when run on the staging, which doesn't allow registration
* Enable signing in as admin when adding a licenseMark Lapierre2018-09-101-21/+0
| | | | | | | | Adds the ability to use admin credentials to add a license so that when testing an LDAP user on EE the LDAP user does not have to be an admin. Admin credentials default to GDK's root user. Can be overriden via ADMIN_USERNAME and ADMIN_PASSWORD environment variables.
* Allow to pass --tag to bin/qa runRémy Coutable2018-08-281-0/+4
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* [QA] Improve the fork scenario to take a username and password instead of ↵qa-staging-2Rémy Coutable2018-08-201-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 importRémy Coutable2018-07-061-0/+23
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Improve the Runtime::API classesRémy Coutable2018-06-063-42/+44
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Removed API endpoint and specsfj-36819-remove-v3-apiFrancisco Javier López2018-05-301-1/+1
|
* It's actually raising QA::Service::Shellout::CommandErrorLin Jen-Shin2018-04-201-1/+2
|
* Remove test against DSA ssh keys becauseLin Jen-Shin2018-03-291-9/+0
| | | | | we're not really supporting them out of the box. See: https://gitlab.com/gitlab-org/gitlab-ce/issues/44363
* Implement other ssh keys and use ssh-keygen insteadLin Jen-Shin2018-03-294-1/+36
|
* Introduce Key namespace so we could put more keysLin Jen-Shin2018-03-291-1/+1
|
* GitLab QA: Add GITLAB_USER_TYPE to support different login types (e.g. ↵sh-add-login-types-qaStan Hu2018-02-111-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.
* Enable RuboCop Style/RegexpLiteralTakuya Noguchi2018-02-011-1/+1
|
* Add an test for QA::Runtime::RSAKeyLin Jen-Shin2018-01-241-0/+9
|
* Add ability to drive the API in QA specsBrett Walker2018-01-233-7/+73
|
* Resolve "Allow QA tests to run with `CHROME_HEADLESS=false`"Brett Walker2018-01-081-0/+64
|
* Make it possible to define global scenario attributesGrzegorz Bizon2017-11-091-0/+27
|
* Add GitLab QA CE strategy and simplify inflectorfeature/gb/gitlab-qa-integration-testsGrzegorz Bizon2017-03-131-39/+14
|
* Do not use GITLAB_RELEASE env to define QA strategyGrzegorz Bizon2017-03-131-19/+26
| | | | [ci skip]
* Fix GitLab QA release inflector strategyGrzegorz Bizon2017-03-091-0/+6
|
* Implement GitLab QA release inflection strategyGrzegorz Bizon2017-03-091-0/+62