summaryrefslogtreecommitdiff
path: root/rubocop/cop/rspec
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-201-0/+64
|
* Add latest changes from gitlab-org/gitlab@12-10-stable-eeGitLab Bot2020-04-201-0/+50
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-311-25/+61
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-151-0/+119
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-071-0/+78
|
* Remove Rubocop::SpecHelper fileVitali Tatarintev2019-08-281-4/+0
|
* Refactor BeSuccessMatcher specs for readabilityVitali Tatarintev2019-08-281-1/+1
|
* Utilize Rubocop's Include for BeSuccessMatcherVitali Tatarintev2019-08-281-1/+0
| | | | | Use Rubocop's Include instead of manually checking the matcher in controllers specs.
* Add support of not_to/to_not to BeSuccessMatcherVitali Tatarintev2019-08-281-2/+2
| | | | | | | | | | | | | | BeSuccessMatcher now supports following examples: ``` expect(response).to be_success expect(response).to_not be_success expect(response).not_to be_success is_expected.to be_success is_expected.to_not be_success is_expected.not_to be_success ```
* Replace double quotes with single quotesVitali Tatarintev2019-08-281-2/+2
|
* Enable frozen string literalVitali Tatarintev2019-08-281-0/+2
|
* Autocorrect `be_success` to `be_successful`Vitali Tatarintev2019-08-281-0/+6
|
* Add Rubocop check to avoid using `be_success`Vitali Tatarintev2019-08-281-0/+50
| | | | | | | | | | | Prevent using `be_success` call in controller specs to avoid getting following deprecation warning: ``` DEPRECATION WARNING: The success? predicate is deprecated and will be removed in Rails 6.0. Please use successful? as provided by Rack::Response::Helpers. ```
* Utilize RuboCop's Include/Exclude configPeter Leitzen2019-08-262-8/+2
| | | | Stop checking the file location programmatically.
* Add RSpec/TopLevelDescribePath copSean McGivern2019-08-011-0/+35
| | | | | | | | The RSpec/FilePath cop checks that a spec file's path is correct, but only if the file describes a constant. We want to check, for any file with a top-level `describe`, whether the file path ends in `_spec.rb`. We don't care what comes before that; just that it will be executed by RSpec at all.
* Introduce a new FactoriesInMigrationSpecs copRémy Coutable2018-04-061-0/+40
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Use gitlab-stylesRémy Coutable2017-12-223-115/+2
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Add a new RSpec::EnvAssignment cop to prevent assigning to ENV in specs18765-stub_env_in_specsRémy Coutable2017-10-181-0/+58
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Replaces `tag: true` into `:tag` in the specsJacopo2017-10-071-0/+74
| | | | | | 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.
* Require rubocop-rspec in the correct locationrs-fix-codeclimate-buildRobert Speicher2017-06-141-1/+3
| | | | Resolves the `codeclimate` CI failure
* Add a custom RSpec/SingleLineHook copRobert Speicher2017-06-141-0/+36
This cop adds an offense when `before`, `after`, or `around` are used as single-line blocks.