summaryrefslogtreecommitdiff
path: root/qa/spec
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-272-11/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-241-0/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-041-0/+32
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-211-3/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-142-0/+35
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-069-11/+11
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-243-26/+8
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-231-0/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-174-10/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-152-13/+13
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-131-0/+20
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-102-4/+20
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-096-17/+553
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-202-0/+57
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-091-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-031-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-201-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-181-0/+18
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-151-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-081-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-311-0/+18
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-181-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-151-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-251-0/+8
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-181-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-131-3/+18
|
* Reduce the CE/EE diff under qa/qa-reduce-ce-ee-diff-in-qa-folderRémy Coutable2019-08-142-1/+29
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Enable Rubocop Performance/InefficientHashSearchsh-enable-rubocop-hash-searchStan Hu2019-07-241-1/+1
| | | | | | | | | When used with a Hash, `.keys.include?` is bad because: 1. It performs a O(n) search instead of the efficient `.has_key?` 2. It clones all keys into separate array. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64975
* QA: Prefer `flat_map` over `map` + `flatten`Peter Leitzen2019-07-221-2/+2
|
* Treat element#selector_css string appropriatelyqa-dd-data-qa-selector-replacementddavison2019-07-101-1/+1
| | | | | Proper escaping should be used for page/base.rb#scroll_to as it is a single quoted JS string
* Introduce data-qa-selector to supplant .qa-classddavison2019-07-101-1/+12
| | | | | | | | | | | | | | | | | | | | | In order to break away from using CSS classes as our primary method of element identification, we need to provide the ability to search for data attributes. Make Test::Sanity::Selectors now work Utilize regex to match on literal strings of the element name Suggest the data-qa-selector pattern vs the qa- Add data-qa-selector to login page to start We need a page that is heavily used in order to be confident that this functionality works. Let's start with the Login page Use appropriate HAML data tag practices
* Run tests in parallel via parallel_testsMark Lapierre2019-07-094-8/+70
| | | | | | | | | | | | | Uses the parallel_tests gem to execute tests in multiple processes simultaneously on the same machine. Adds the `--parallel` CLI option that instructs the QA framework to use the parallel_tests executable. Tests need access to global state contained in `Runtime::Scenario` so when `--parallel` is invoked `Runtime::Scenario` is serialized to an environment variable, which is passed to parallel_tests, and then deserialized in `spec_helper`.
* First pass at new automated QA API test for #52703Grant Young2019-07-011-3/+33
| | | | | | Checks that archives of two different user projects with the same name aren't the same via checksum. I.E. a user can't download the archive of another's project by mistake. To enable the test some enhancements were made. Namely updating the client module to handle more than one API instance and the creation a custom rest call method that downloads to tmp.
* Test push limit with admin userMark Lapierre2019-06-182-14/+60
| | | | | | | | | | | Uses `:requires_admin` metadata to specify that a test needs an admin user. Sets the push file size limit test to require an admin user. With an admin access token set as the env var GITLAB_QA_ADMIN_ACCESS_TOKEN, the push size limit test now only uses the API and CLI
* Backport of EE changes from MR 13763Walmyr2019-06-141-2/+2
| | | | https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13763
* Fix Web IDE add template testMark Lapierre2019-06-051-1/+11
| | | | | | | | | Wait for the new file modal to stop animating before clicking it We now need to click the commit button 3 times: 1. To enter commit mode 2. To being staging changes 3. To submit the commit
* Generate knapsack report for review-qa-allMark Lapierre2019-06-032-0/+29
| | | | | | | | | | | | | | | | | | | | | | Add knapsack qa report and use it to run tests in parallel Use the RSpec runner with knapsack The way the Knapsack runner uses exec to start rspec seems incompatible with the way we expect it to work. Plus, it requires specifying KNAPSACK_TEST_DIR. Instead, we use knapsacks AllocatorBuilder to select the spec files to run, and then start rspec as normal, via RSpec::Core::Runner.run This also means we can incorporate tags. Let the job run automatically Include KNAPSACK_TEST_FILE_PATTERN in vars Check all defined knapsack env vars before requiring knapsack
* Implement dynamic validation on QA Pagesddavison2019-05-201-0/+56
| | | | | | Elements now have the ability to be required on pages or not Currently using the default wait mechanism Altered the ElementWithPattern Cop to fit new splat for init
* Only retry failing QA tests in CIqa-retry-in-ci-onlyMark Lapierre2019-05-201-3/+5
| | | | No need to retry automatically when running tests locally
* Merge branch 'qa-ml-fix-branches-test' into 'master'Sanad Liaquat2019-05-131-1/+8
|\ | | | | | | | | Fix E2E test - wait for branches to not be present See merge request gitlab-org/gitlab-ce!27805
| * Add branch_name qa selectorqa-ml-fix-branches-testMark Lapierre2019-05-071-1/+8
| | | | | | | | | | | | Uses the branch_name element to find a branch with a specific name, instead of using a dynamic CSS class that can't be validated by the sanity selector test
* | Swap brackets to avoid false positiveqa-escape-netrc-regexMark Lapierre2019-05-061-1/+1
| |
* | Escape arg used in regexMark Lapierre2019-05-061-0/+9
|/
* Merge branch 'frozen_string_literal_qa' into 'master'Sanad Liaquat2019-04-1521-0/+42
|\ | | | | | | | | Add frozen_string_literal to qa/ See merge request gitlab-org/gitlab-ce!27266
| * Add frozen_string_literal to qa/frozen_string_literal_qaThong Kuah2019-04-1321-0/+42
| | | | | | | | | | This will be default in Ruby 3, so will be good to apply in QA ahead of time to be consistent.
* | Enable RSpec/ExampleWording copThong Kuah2019-04-121-2/+2
|/
* Reduce number of rspec retriesSanad Liaquat2019-04-091-1/+1
| | | | | In both e2e QA tests and unit tests, reduce the number of retires to 2 (i.e., 1 initial and one retry)
* Allow token env var from gitlab-qaMark Lapierre2019-03-281-3/+3
| | | | | | | gitlab-qa accepts an env var named GITLAB_QA_ACCESS_TOKEN, but here we only accepted PERSONAL_ACCESS_TOKEN. This change replaces PERSONAL_ACCESS_TOKEN with GITLAB_QA_ACCESS_TOKEN
* Set feature flag via command lineMark Lapierre2019-03-277-12/+127
| | | | | | | | | | | First attempt at allowing a feature flag to be set via the command line when running tests. This will enable the flag, run the tests, and then disable the flag. Using OptionParser meant changing how scenarios get the instance address, so this also allows the address to be set as a command line option. It's backwards compatible (you can still provide the address as the command line option after the scenario)
* Skip contexts in quarantineMark Lapierre2019-03-113-401/+272
| | | | This avoids running before/after blocks for tests that are in quarantine