summaryrefslogtreecommitdiff
path: root/spec/features/issues/filtered_search/filter_issues_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@15-7-stable-eev15.7.0-rc42GitLab Bot2022-12-201-1/+1
|
* Add latest changes from gitlab-org/gitlab@15-6-stable-eev15.6.0-rc42GitLab Bot2022-11-171-0/+1
|
* Add latest changes from gitlab-org/gitlab@15-1-stable-eev15.1.0-rc42GitLab Bot2022-06-201-1/+0
|
* Add latest changes from gitlab-org/gitlab@15-0-stable-eev15.0.0-rc42GitLab Bot2022-05-191-193/+151
|
* Add latest changes from gitlab-org/gitlab@14-9-stable-eev14.9.0-rc42GitLab Bot2022-03-181-0/+10
|
* Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42GitLab Bot2021-09-201-6/+3
|
* Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42GitLab Bot2021-05-191-21/+1
|
* Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42GitLab Bot2020-12-171-0/+8
|
* Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot2020-07-201-5/+3
|
* Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot2020-06-181-1/+1
|
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-201-14/+33
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-061-8/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-041-36/+36
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-251-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-231-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-021-25/+139
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-201-52/+0
|
* Add frozen_string_literal to spec/featuresThong Kuah2019-07-261-0/+2
| | | | | Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
* Standardize token value capitalization in filter barOmar Bahareth2019-01-281-5/+5
|
* Sort issues and merge requests in ascending and descending orderFatih Acet2018-12-061-1/+1
|
* Fix secondary nav dropdown menu styling in tablet and mobile screensKushal Pandya2018-12-031-2/+2
|
* Rename some css classes that are shared between issues and mrsDmitriy Zaporozhets2018-09-211-1/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Resolve "Rename the `Master` role to `Maintainer`" BackendMark Chao2018-07-111-1/+1
|
* Bring changes from EEunify-filter_issues_spec.rbLin Jen-Shin2018-06-211-2/+34
|
* Export assigned issues in iCalendar feedImre Farkas2018-05-311-2/+2
|
* Fix filter issues specClement Ho2018-04-201-1/+1
|
* Allow assigning and filtering issuables by ancestor group labelsFelipe Artur2018-04-041-9/+0
|
* correct the issues list count for label:none filterMike Greiling2017-10-241-1/+1
|
* Replaces `tag: true` into `:tag` in the specsJacopo2017-10-071-1/+1
| | | | | | Replaces all the explicit include metadata syntax in the specs (tag: true) into the implicit one (:tag). Added a cop to prevent future errors and handle autocorrection.
* Improve list of sorting optionsVitaliy @blackst0ne Klachkov2017-09-231-9/+7
|
* Shorten the search input for "text with other filters" specrs-filtered-issue-search-speedRobert Speicher2017-09-011-1/+1
| | | | | | The assignee wasn't important to the test, and shortening the query allowed us to avoid the "horizontal scroll" failure without having to stub the `sidebar_collapsed?` helper.
* Turns out that short name was important, who knew!Robert Speicher2017-09-011-1/+6
| | | | We now document that fact.
* Combine multiple `it` blocks in filter_issues_specRobert Speicher2017-09-011-18/+9
|
* Remove more redundant specs in filter_issues_specRobert Speicher2017-09-011-72/+17
| | | | | We were essentially testing "all of the filters" four times, so now we just do it once at the top level.
* Re-order top-level `let`s, so that labels are groupedRobert Speicher2017-09-011-1/+1
|
* Remove unused select_search_at_index helperRobert Speicher2017-09-011-4/+0
|
* Reduce duplication in RSS feed specs for filter_issues_specRobert Speicher2017-09-011-26/+24
|
* Remove the top-level closed issue from filter_issues_specRobert Speicher2017-09-011-6/+6
|
* Remove unused labels from filter_issues_specRobert Speicher2017-09-011-4/+1
|
* Reduce issues and milestones created in global filter_issues_spec setupRobert Speicher2017-09-011-18/+24
| | | | | | Three issues were only used in one test each, and one milestone with its accompanying issue were only used in one test, so we now scope those locally.
* Clean up the still-way-too-complex filter_issues_spec setupRobert Speicher2017-09-011-33/+26
| | | | | | | | | | | Removes unnecessary `let!` usage since we explicitly access these in the `before. Re-uses `user2` as the author for issues we otherwise don't care about the author for, to avoid creating a new user in each one. Makes use of the `labeled_issue` factory to avoid assigning variables just so we can add labels to an issue.
* Remove an unnecessary issue creationRobert Speicher2017-09-011-4/+3
| | | | This seemed to only exist to increment an issue counter by 1.
* Remove unnecessary attributes from factoriesRobert Speicher2017-09-011-3/+4
|
* Scope group creation to the specs that actually require itRobert Speicher2017-09-011-4/+8
| | | | | Only one context tested group behavior, but we were performing group and membership creation on every example unnecessarily.
* Use a positive assertion for have_no_selector rather than the inverseRobert Speicher2017-09-011-1/+1
|
* Remove unnecessary include from filter_issues_specRobert Speicher2017-09-011-1/+0
|
* Remove redundant specs from filter_issues_specRobert Speicher2017-09-011-254/+10
| | | | | | | | | | | | | | While testing the various search tokens, we would add the token and a search term, then verify the correct issues were returned. Then we'd add a new token, search again, and verify again. Then another, and another. This was entirely redundant. If the search with higher specificity returned the same results as the search with lower specificity, we can be sure the lower specificity searches also worked without actually testing them. Because this entire spec performs very extensive setup, it's important to limit the number of times we perform that setup.
* spec updatesPhil Hughes2017-08-291-0/+2
|
* more spec fixesPhil Hughes2017-08-291-1/+1
|
* Remove skipped examples in filtered issues feature specrs-remove-filtered-issues-skipsRobert Speicher2017-08-251-50/+0
| | | | | | | | | | | We perform a ton of expensive setup in this spec, via both `before` and `let!`. When we use `skip` inside an `it` block, rather than skipping the block entirely via `xit`, we still perform this expensive setup, only to do absolutely nothing with it, resulting in wasted time. Minutes, in this case. Further, these specs have been sitting in our test suite for about seven months now, so the likelihood of them being addressed soon seems low.