rubygems
/
hashie
1
0
Fork 0
Code Packages Releases Activity
hashie/spec/spec_helper.rb

25 lines
523 B
Ruby
Raw Normal View History

Code coverage reporting
2014-11-27 06:09:36 +00:00
if ENV['CI']
Update to CodeClimate 1.0.x CodeClimate > 1.0 uses SimpleCov and requires the test reporter to be called explicitly: https://github.com/codeclimate/ruby-test-reporter/blob/master/CHANGELOG. md#v100-2016-11-03
2016-12-01 22:09:27 +00:00
require 'simplecov'
SimpleCov.start
Code coverage reporting
2014-11-27 06:09:36 +00:00
end
Add pry and pry-stack_explorer for debugging
2014-08-24 16:59:51 +00:00
require 'pry'
Adds a fix for json generation
2010-06-15 06:16:25 +00:00
Update to RSpec 2.0
2011-01-27 14:20:39 +00:00
require 'rspec'
Add simple RSpec.configure block for expect syntax Without the configure block, [mutant][mutant] was raising an error. I'm interested in mutation testing our test suite, so thought this would be the simplest thing to add to get that working. It also enforces the expect syntax, which is a nice side benefit. [mutant]: https://github.com/mbj/mutant
2014-09-06 21:21:05 +00:00
require 'hashie'
require json at spec_helper to fix #532
2020-10-05 13:00:18 +00:00
require 'json'
@dblock - a one liner with no complexity for pending specs by Ruby Engine / Version - removes all complexity from Hashie
2015-10-22 09:07:21 +00:00
require 'rspec/pending_for'
Fix support for Array#dig
2016-05-31 22:53:33 +00:00
require './spec/support/ruby_version_check'
Allow Mash subclasses to disable warnings Since we are transitively used as a dependency in many projects, we should have given the ability to toggle this behavior off. The logging feature is more of a "help people get started with Mash" feature. If you're using Hashie in a library, it's likely that you already know the tradeoffs of attempting to override methods on the object. To use this feature, you only have to subclass Mash and then call the class method: ```ruby class KeyStore < Hashie::Mash disable_warnings end ```
2017-02-01 14:03:45 +00:00
require './spec/support/logger'
Don't warn when setting most affixed keys (#500) Due to how we have implemented the bang/underbang/query behavior within Mash, setting keys that have those affixes in them actually allow overwriting the behavior of those affixes. As such, we shouldn't warn when setting a key that matches those patterns. When it comes to setter-like keys, I believe we still _do_ want to warn for two reasons: 1. Trying to access the key via method access is a syntax error. Ruby expects any method ending in `=` to be a 2+-arity method due to the infix notation of setter methods. This is unexpected behavior unless you're very familiar with Ruby parsing. 2. You can still retrieve the key via the normal `Hash#[]` reader, but it prevents setting a similar key without the equal sign. You can see this in the test about setters. I'd say that is unexpected and surprising behavior. Because of these two gotchas, I think we should still warn in cases where you try to set a key that looks like a setter.
2020-01-15 19:17:27 +00:00
require './spec/support/matchers'
Add simple RSpec.configure block for expect syntax Without the configure block, [mutant][mutant] was raising an error. I'm interested in mutation testing our test suite, so thought this would be the simplest thing to add to get that working. It also enforces the expect syntax, which is a nice side benefit. [mutant]: https://github.com/mbj/mutant
2014-09-06 21:21:05 +00:00
Fix inconsistencies with Dash defaults The normal behavior of Dash with respect to property defaults differed from the behavior of a Dash/Trash with IgnoreUndeclared mixed in. This is because some situations called the defaults and some did not. This change normalizes the behavior so that all situations where the defaults should be used to override unset values behave consistently, as well as all situations where the default should not override a `nil` value.
2020-10-24 02:57:10 +00:00
Dir[File.expand_path(File.join(__dir__, 'support', '**', '*'))].sort.each { |file| require file }
Add simple RSpec.configure block for expect syntax Without the configure block, [mutant][mutant] was raising an error. I'm interested in mutation testing our test suite, so thought this would be the simplest thing to add to get that working. It also enforces the expect syntax, which is a nice side benefit. [mutant]: https://github.com/mbj/mutant
2014-09-06 21:21:05 +00:00
RSpec.configure do |config|
Fix support for Array#dig
2016-05-31 22:53:33 +00:00
config.extend RubyVersionCheck
Add simple RSpec.configure block for expect syntax Without the configure block, [mutant][mutant] was raising an error. I'm interested in mutation testing our test suite, so thought this would be the simplest thing to add to get that working. It also enforces the expect syntax, which is a nice side benefit. [mutant]: https://github.com/mbj/mutant
2014-09-06 21:21:05 +00:00
config.expect_with :rspec do |expect|
expect.syntax = :expect
end
Fix "@disable_warnings" spec warning (#416) When running rspec specs on the ruby-grape project with warnings enabled this warning is printed hundreds of times. This change fixes the warning. Also, turn on warnings when running rspec to see when this happens.
2017-03-01 12:13:50 +00:00
config.warnings = true
Add simple RSpec.configure block for expect syntax Without the configure block, [mutant][mutant] was raising an error. I'm interested in mutation testing our test suite, so thought this would be the simplest thing to add to get that working. It also enforces the expect syntax, which is a nice side benefit. [mutant]: https://github.com/mbj/mutant
2014-09-06 21:21:05 +00:00
end