docbrown/spec/support
Anthony Musyoki 2537670968 Refactor raise_error(specific_error) expectation (#4912)
* Refactor raise_error(specific_error) expectation

The full RSpec warining is
```
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives,
since literally any other error would cause the expectation to pass,
including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError),
meaning the code you are intending to test may not even get reached.
Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`.
```

* Refactor jsitor tests to test behaviour

As pointed out by @rhymes, the previous tests were not
testing actual behaviour. This is an attempt at improving the tests.
2019-11-26 08:46:33 -05:00
..
fixtures Refactor raise_error(specific_error) expectation (#4912) 2019-11-26 08:46:33 -05:00
initializers Remove Chrome version from Travis.yml (#4555) [ci skip] 2019-10-23 09:15:23 -04:00
api_analytics_shared_examples.rb Articles API: create and update (#2844) 2019-05-16 12:26:24 -04:00
omniauth_macros.rb Fix rubocop offenses (#1452) 2019-01-03 09:23:38 -05:00
shared_context.rb Code cleanups (#659) 2018-08-07 11:00:13 -04:00
stubs.rb Code cleanups (#659) 2018-08-07 11:00:13 -04:00
within_block_is_expected.rb Improve ArticlesController's authorization (#466) 2018-06-21 14:18:32 -04:00