# CHANGES

Path: | CHANGES
Last Update: | Sat Jun 02 18:36:09 CDT 2007

## Version 1.0.4

The getting ready for JRuby release.

- Fixed [11181] behaviour_type scoping of config.before(:each) is not working
- added mock argument constraint matchers (anything(), boolean(), an_instance_of(Type)) which work with rspec or mocha
- added mock argument constraint matchers (any_args(), no_args()) which only work with rspec
- deprecated rspec‘s symbol mock argument constraint matchers (:any_args, :no_args, :anything, :boolean, :numeric, :string)
- Added tarball of rspec_on_rails to the release build to support folks working behind a firewall that blocks svn access.
- Fixed [11137] rspec incorrectly handles flash after resetting the session
- Fixed [11143] Views code for ActionController::Base#render broke between 1.0.0 and 1.0.3 on Rails Edge r6731
- Added raise_controller_errors for controller examples in Spec::Rails

## Version 1.0.3

Bug fixes.

- Fixed [11104] Website uses old specify notation
- Applied [11101] StringHelpers.starts_with?(prefix) assumes a string parameter for prefix
- Removed ‘rescue nil’ which was hiding errors in controller examples.
- Fixed [11075] controller specs fail when using mocha without integrated_views
- Fixed problem with redirect_to failing incorrectly against edge rails.
- Fixed [11082] RspecResourceGenerator should be RspecScaffoldGenerator
- Fixed [10959] Focused Examples do not work for Behaviour defined with constant with modules

## Version 1.0.2

This is just to align the version numbers in rspec and rspec_on_rails.

## Version 1.0.1

This is a maintenance release with mostly cleaning up, and one minor enhancement - Modules are automatically included when described directly.

- Renamed Spec::Rails’ rspec_resource generator to rspec_scaffold.
- Removed Spec::Rails’ be_feed matcher since it‘s based on assert_select_feed which is not part of Rails (despite that docs for assert_select_encoded says it is).
- describe(SomeModule) will include that module in the examples. Like for Spec::Rails helpers, but now also in core.
- Header in HTML report will be yellow instead of red if there is one failed example
- Applied [10951] Odd instance variable name in rspec_model template (patch from Kyle Hargraves)
- Improved integration with autotest (Patches from Ryan Davis and David Goodland)
- Some small fixes to make all specs run on JRuby.

## Version 1.0.0

The stake in the ground release. This represents a commitment to the API as it is. No significant backwards compatibility changes in the API are expected after this release.

- Fixed [10923] have_text matcher does not support should_not
- Fixed [10673] should > and should >= broken
- Applied [10921] Allow verify_rcov to accept greater than threshold coverage %’s via configuration
- Applied [10920] Added support for not implemented examples (Patch from Chad Humphries and Ken Barker)
- Patch to allow not implemented examples. This works by not providing a block to the example. (Patch from Chad Humphries, Ken Barker)
- Yanked support for Rails 1.1.6 in Spec::Rails
- RSpec.tmbundle uses CMD-SHIFT-R to run focused examples now.
- Spec::Rails now bundles a spec:rcov task by default (suggestion from Kurt Schrader)
- Fixed [10814] Runner loads shared code, test cases require them again
- Fixed [10753] Global before and after
- Fixed [10774] Allow before and after to be specified in config II
- Refactored Spec::Ui examples to use new global before and after blocks.
- Added instructions about how to get Selenium working with Spec::Ui (spec_ui/examples/selenium/README.txt)
- Fixed [10805] selenium.rb missing from gem?
- Added rdocs explaining how to deal with errors in Rails’ controller actions
- Applied [10770] Finer grained includes.
- Fixed [10747] Helper methods defined in shared specs are not visible when shared spec is used
- Fixed [10748] Shared descriptions in separate files causes ‘already exists’ error
- Applied [10698] Running with —drb executes specs twice (patch from Ruy Asan)
- Fixed [10871] 0.9.4 - Focussed spec runner fails to run specs in descriptions with type and string when there is no leading space in the string

## Version 0.9.4

This release introduces massive improvements to Spec::Ui - the user interface functional testing extension to RSpec. There are also some minor bug fixes to the RSpec core.

- Massive improvements to Spec::Ui. Complete support for all Watir‘s ie.xxx(how, what) methods. Inline screenshots and HTML.
- Reactivated —timeout, which had mysteriously been deactivated in a recent release.
- Fixed [10669] Kernel#describe override does not cover Kernel#context
- Applied [10636] Added spec for OptionParser in Runner (Patch from Scott Taylor)
- Added [10516] should_include should be able to accept multiple items
- Applied [10631] redirect_to matcher doesn‘t respect request.host (Patch from Tim Lucas)
- Each formatter now flushes their own IO. This is to avoid buffering of output.
- Fixed [10670] IVarProxy#delete raises exception when instance variable does not exist

## Version 0.9.3

This is a bugfix release.

- Fixed [10594] Failing Custom Matcher show NAME NOT GENERATED description
- describe(SomeType, "message") will not add a space: "SomeType#message" (likewise for ’.’)
- describe(SomeType, "message") will have a decription with a space: "SomeType message"
- Applied [10566] prepend_before and prepend_after callbacks
- Applied [10567] Call setup and teardown using before and after callbacks

## Version 0.9.2

This is a quick maintenance release.

- Added some website love
- Fixed [10542] reverse predicate matcher syntax
- Added a spec:translate Rake task to make 0.9 translation easier with Spec:Rails
- Better translation of should_redirect_to
- Fixed —colour support for Windows. This is a regression that was introduced in 0.9.1
- Applied [10460] Make SpecRunner easier to instantiate without using commandline args

## Version 0.9.1

This release introduces describe and it (aliased as context and specify for backwards compatibility). This allows you to express specs like this:

      describe SomeClass do # Creates a Behaviour
        it "should do something" do # Creates an Example
        end
      end

The command line features four new options that give you more control over what specs are being run and in what order. This can be used to verify that your specs are independent (by running in opposite order with —reverse). It can also be used to cut down feedback time by running the most recently modified specs first (—loadby mtime —reverse).

Further, —example replaces the old —spec option, and it can now take a file name of spec names as an alternative to just a spec name. The —format failing_examples:file.txt option allows you to output an —example compatible file, which makes it possible to only rerun the specs that failed in the last run. Spec::Rails uses all of these four options by default to optimise your RSpec experience.

There is now a simple configuration model. For Spec::Rails, you do something like this:

      Spec::Runner.configure do |config|
        config.use_transactional_fixtures = true
        config.use_instantiated_fixtures  = false
        config.fixture_path = RAILS_ROOT + '/spec/fixtures'
      end

You can now use mocha or flexmock with RSpec if you prefer either to RSpec‘s own mock framework. Just put this:

      Spec::Runner.configure do |config|
        config.mock_with :mocha
      end

or this:

      Spec::Runner.configure do |config|
        config.mock_with :flexmock
      end

in a file that is loaded before your specs. You can also configure included modules and predicate_matchers:

      Spec::Runner.configure do |config|
        config.include SomeModule
        config.predicate_matchers[:does_something?] = :do_something
      end

See Spec::DSL::Behaviour for more on predicate_matchers

- Sugar FREE!
- Added [10434 ] Please Make -s synonymous with -e for autotest compat. This is temporary until autotest uses -e instead of -s.
- Fixed [10133] custom predicate matchers
- Applied [10473] Add should exist (new matcher) - Patch from Bret Pettichord
- Added another formatter: failing_behaviours. Writes the names of the failing behaviours for use with —example.
- Applied [10315] Patch to fix pre_commit bug 10313 - pre_commit_rails: doesn‘t always build correctly (Patch from Antii Tarvainen)
- Applied [10245] Patch to HTML escape the behavior name when using HTML Formatter (Patch from Josh Knowles)
- Applied [10410] redirect_to does not behave consistently with regards to query string parameter ordering (Patch from Nicholas Evans)
- Applied [9605] Patch for ER 9472, shared behaviour (Patch by Bob Cotton)
- The ’—format rdoc’ option no longer causes a dry-run by default. —dry-run must be used explicitly.
- It‘s possible to specify the output file in the —format option (See explanation in —help)
- Several —format options may be specified to output several formats in one run.
- The —out option is gone. Use —format html:path/to/my.html instead (or similar).
- Spec::Runner::Formatter::BaseTextFormatter#initialize only takes one argument - an IO. dry_run and color are setters.
- Made Spec::Ui much easier to install. It will be released separately. Check out trunk/spec_ui/examples
- HTML reports now include a syntax highlighted snippet of the source code where the spec failed (needs the syntax gem)
- Added [10262] Better Helper testing of Erb evaluation block helpers
- Added [9735] support flexmock (thanks to Jim Weirich for his modifications to flexmock to support this)
- Spec::Rails controller specs will no longer let mock exception ripple through to the response.
- Fixed [9260] IvarProxy does not act like a hash.
- Applied [9458] The rspec_scaffold generator does not take into account class nesting (Patch from Steve Tendon)
- Applied [9132] Rakefile spec:doc can fail without preparing database (Patch from Steve Ross)
- Applied [9678] Custom runner command line switch, and multi-threaded runner (Patch from Bob Cotton)
- Applied [9926] Rakefile - RSPEC_DEPS constant as an Array of Hashes instead of an Array of Arrays (Patch from Scott Taylor)
- Applied [9925] Changed ".rhtml" to "template" in REST spec generator (Patch from Scott Taylor)
- Applied [9852] Patch for RSpec‘s Website using Webgen 0.4.2 (Patch from Scott Taylor)
- Fixed [6523] Run rspec on rails without a db
- Fixed [9295] rake spec should run anything in the spec directory (not just rspec‘s standard dirs)
- Added [9786] infer controller and helper names from the described type
- Fixed [7795] form_tag renders action=’/view_spec’ in view specs
- Fixed [9767] rspec_on_rails should not define rescue_action on controllers
- Fixed [9421] —line doesn‘t work with behaviours that use class names
- Fixed [9760] rspec generators incompatible with changes to edge rails
- Added [9786] infer controller and helper names from the described type
- Applied a simplified version of [9282] Change to allow running specs from textmate with rspec installed as a rails plugin (and no rspec gem installed)
- Applied [9700] Make Spec::DSL::Example#name public / Add a —timeout switch. A great way to prevent specs from getting slow.
- In Rails, script/generate rspec will generate a spec.opts file that optimises faster/more efficient running of specs.
- Added [9522] support using rspec‘s expectations with test/unit
- Moved rspec_on_rails up to the project root, simplifying the download url
- Fixed [8103] RSpec not installing spec script correctly.
- The —spec option is replaced by the —example option.
- The —loadby option no longer supports a file argument. Use —example file_name instead.
- The —example option can now take a file name as an argument. The file should contain example names.
- Internal classes are named Behaviour/Example (rather than Context/Specification).
- You can now use mocha by saying config.mock_with :mocha in a spec_helper
- before_context_eval is replaced by before_eval.
- Applied [9509] allow spaced options in spec.opts
- Applied [9510] Added File for Ruby 1.8.6
- Applied [9511] Clarification to README file in spec/
- Moved all of the Spec::Rails specs down to the plugins directory - now you can run the specs after you install.
- Updated RSpec.tmbundle to the 0.9 syntax and replaced context/specify with describe/it.
- Applied [9232] ActionController::Base#render is sometimes protected (patch from Dan Manges)
- Added —reverse option, allowing contexts/specs to be run in reverse order.
- Added —loadby option, allowing better control over load order for spec files. mtime and file.txt supported.
- Implemented [8696] —order option (see —reverse and —loadby)
- Added describe/it as aliases for context/specify - suggestion from Dan North.
- Applied [7637] [PATCH] add skip-migration option to rspec_scaffold generator
- Added [9167] string.should have_tag
- Changed script/rails_spec_server to script/spec_server and added script/spec (w/ path to vendor/plugins/rspec)
- Fixed [8897] Error when mixing controller spec with/without integrated views and using template system other than rhtml
- Updated sample app specs to 0.9 syntax
- Updated generated specs to 0.9 syntax
- Applied [8994] trunk: generated names for be_ specs (Multiple patches from Yurii Rashkovskii)
- Applied [9983]: Allow before and after to be called in BehaviourEval. This is useful for shared examples.

## Version 0.8.2

Replaced assert_select fork with an assert_select wrapper for have_tag. This means that "should have_rjs" no longer supports :hide or :effect, but you can still use should_have_rjs for those.

## Version 0.8.1

Quick "in house" bug-fix

## Version 0.8.0

This release introduces a new approach to handling expectations using Expression Matchers.

See Upgrade, Spec::Expectations, Spec::Matchers and RELEASE-PLAN for more info.

This release also improves the spec command line by adding DRb support and making it possible to store command line options in a file. This means a more flexible RSpec experience with Rails, Rake and editor plugins like TextMate.

It also sports myriad new features, bug fixes, patches and general goodness:

- Fixed [8928] rspec_on_rails 0.8.0-RC1 controller tests make double call to setup_with_fixtures
- Fixed [8925] Documentation bug in 0.8.0RC1 rspec website
- Applied [8132] [PATCH] RSpec breaks "rake db:sessions:create" in a rails project that has the rspec_on_rails plugin (Patch from Erik Kastner)
- Fixed [8789] —line and —spec not working when the context has parenhesis in the name
- Added [8783] auto generate spec names from last expectation
- —heckle now fails if the heckled class or module is not found.
- Fixed [8771] Spec::Mocks::BaseExpectation#with converts hash params to array of arrays with collect
- Fixed [8750] should[_not]_include backwards compatibility between 0.8.0-RC1 and 0.7.5.1 broken
- Fixed [8646] Context Runner does not report on Non standard exceptions and return a 0 return code
- RSpec on Rails’ spec_helper.rb will only force RAILS_ENV to test if it was not specified on the command line.
- Fixed [5485] proc#should_raise and proc#should_not_raise output
- Added [8484] should_receive with blocks
- Applied [8218] heckle_runner.rb doesn‘t work with heckle >= 1.2.0 (Patch from Michal Kwiatkowski)
- Fixed [8240] Cryptic error message when no controller_name
- Applied [7461] [PATCH] Contexts don‘t call Module::included when they include a module
- Removed unintended block of test/unit assertions in rspec_on_rails - they should all, in theory, now be accessible
- Added mock_model method to RSpec on Rails, which stubs common methods. Based on metaclass.org/2006/12/22/making-a-mockery-of-activerecord
- Fixed [8165] Partial Mock Errors when respond_to? is true but the method is not in the object
- Fixed [7611] Partial Mocks override Subclass methods
- Fixed [8302] Strange side effect when mocking a class method
- Applied [8316] to_param should return a stringified key in resource generator‘s controller spec (Patch from Chris Anderson)
- Applied [8216] shortcut for creating object stub
- Applied [8008] Correct generated specs for view when calling resource generator (Patch from Jonathan Tron)
- Fixed [7754] Command-R fails to run spec in TextMate (added instruction from Luke Redpath to the website)
- Fixed [7826] RSpect.tmbundle web page out of date.
- RSpec on Rails specs are now running against RoR 1.2.1 and 1.2.2
- rspec_scaffold now generates specs for views
- In a Rails app, RSpec core is only loaded when RAILS_ENV==test (init.rb)
- Added support for target.should arbitrary_expectation_handler and target.should_not arbitrary_expectation_handler
- Fixed [7533] Spec suite fails and the process exits with a code 0
- Fixed [7565] Subsequent stub! calls for method fail to override the first call to method
- Applied [7524] Incorrect Documentation for ‘pattern’ in Rake task (patch from Stephen Duncan)
- Fixed [7409] default fixtures do not appear to run.
- Fixed [7507] "render..and return" doesn‘t return
- Fixed [7509] rcov/rspec incorrectly includes boot.rb (Patch from Courtenay)
- Fixed [7506] unnecessary complex output on failure of response.should be_redirect
- Applied [6098] Make scaffold_resource generator. Based on code from Pat Maddox.
- The drbspec command is gone. Use spec —drb instead.
- The drb option is gone from the Rake task. Pass —drb to spec_opts instead.
- New -X/—drb option for running specs against a server like spec/rails’ script/rails_spec_server
- New -O/—options and -G/—generate flags for file-based options (handy for spec/rails)
- Applied [7339] Turn off caching in HTML reports
- Applied [7419] "c option for colorizing output does not work with rails_spec" (Patch from Shintaro Kakutani)
- Applied [7406] [PATCH] 0.7.5 rspec_on_rails loads fixtures into development database (Patch from Wilson Bilkovich)
- Applied [7387] Allow stubs to return consecutive values (Patch from Pat Maddox)
- Applied [7393] Fix for rake task (Patch from Pat Maddox)
- Reinstated support for response.should_render (in addition to controller.should_render)

## Version 0.7.5.1

Bug fix release to allow downloads of rspec gem using rubygems 0.9.1.

## Version 0.7.5

This release adds support for Heckle - Seattle‘rb‘s code mutation tool. There are also several bug fixes to the RSpec core and the RSpec on Rails plugin.

- Removed svn:externals on rails versions and plugins
- Applied [7345] Adding context_setup and context_teardown, with specs and 100% rcov
- Applied [7320] [PATCH] Allow XHR requests in controller specs to render RJS templates
- Applied [7319] Migration code uses drop_column when it should use remove_column (patch from Pat Maddox)
- Added support for Heckle
- Applied [7282] dump results even if spec is interrupted (patch from Kouhei Sutou)
- Applied [7277] model.should_have(n).errors_on(:attribute) (patch from Wilson Bilkovich)
- Applied [7270] RSpec render_partial colliding with simply_helpful (patch from David Goodlad)
- Added [7250] stubs should support throwing
- Added [7249] stubs should support yielding
- Fixed [6760] fatal error when accessing nested finders in rspec
- Fixed [7179] script/generate rspec_scaffold generates incorrect helper name
- Added preliminary support for assert_select (response.should_have)
- Fixed [6971] and_yield does not work when the arity is -1
- Fixed [6898] Can we separate rspec from the plugins?
- Added [7025] should_change should accept a block
- Applied [6989] partials with locals (patch from Micah Martin)
- Applied [7023] Typo in team.page

## Version 0.7.4

This release features a complete redesign of the reports generated with —format html. As usual there are many bug fixes - mostly related to spec/rails.

- Applied [7010] Fixes :spacer_template does not work w/ view spec (patch from Shintaro Kakutani)
- Applied [6798] ensure two ’:’ in the first backtrace line for Emacs‘s ‘next-error’ command (patch from Kouhei Sutou)
- Added Much nicer reports to generated website
- Much nicer reports with —format —html (patch from Luke Redpath)
- Applied [6959] Calls to render and redirect in controllers should return true
- Fixed [6981] helper method is not available in partial template.
- Added [6978] mock should tell you the expected and actual args when receiving the right message with the wrong args
- Added the possibility to tweak the output of the HtmlFormatter (by overriding extra_failure_content).
- Fixed [6936] View specs don‘t include ApplicationHelper by default
- Fixed [6903] Rendering a partial in a view makes the view spec blow up
- Added callback library from Brian Takita
- Added [6925] support controller.should_render :action_name
- Fixed [6884] intermittent errors related to method binding
- Fixed [6870] rspec on edge rails spec:controller fixture loading fails
- Using obj.inspect for all messages
- Improved performance by getting rid of instance_exec (instance_eval is good enough because we never need to pass it args)

## Version 0.7.3

Almost normal bug fix/new feature release.

A couple of things you need to change in your rails specs: # spec_helper.rb is a little different (see rspec.rubyforge.org/upgrade.html) # use controller.should_render before OR after the action (controller.should_have_rendered is deprecated)

- Applied [6577] messy mock backtrace when frozen to edge rails (patch from Jay Levitt)
- Fixed [6674] rspec_on_rails fails on @session deprecation warning
- Fixed [6780] routing() was failing...fix included - works for 1.1.6 and edge (1.2)
- Fixed [6835] bad message with arbitrary predicate
- Added [6731] Partial templates rendered
- Fixed [6713] helper methods not rendered in view tests?
- Fixed [6707] cannot run controller / helper tests via rails_spec or spec only works with rake
- Applied [6417] lambda {…}.should_change(receiver, :message) (patch from Wilson Bilkovich)
- Eliminated dependency on ZenTest
- Fixed [6650] Reserved characters in the TextMate bundle break svn on Win32
- Fixed [6643] script/generate rspec_controller: invalid symbol generation for ‘controller_name’ for modularized controllers
- The script/rails_spec command has been moved to bin/drbspec in RSpec core (installed by the gem)

## Version 0.7.2

This release introduces a brand new RSpec bundle for TextMate, plus some small bugfixes.

- Packaged RSpec.tmbundle.tgz as part of the distro
- Fixed [6593] Add moving progress bar to HtmlFormatter using Javascript
- Applied [6265] should_raise should accept an Exception object
- Fixed [6616] Can‘t run Rails specs with RSpec.tmbundle
- Fixed [6411] Can‘t run Rails specs with ruby
- Added [6589] New -l —line option. This is useful for IDE/editor runners/extensions.
- Fixed [6615] controller.should_render_rjs should support :partial => ‘path/to/template‘

## Version 0.7.1

Bug fixes and a couple o’ new features.

- Fixed [6575] Parse error in aliasing the partial mock original method (patch by Brian Takita)
- Fixed [6277] debris left by stubbing (trunk) [submitted by dastels] (fixed by fix to [6575])
- Fixed [6575] Parse error in aliasing the partial mock original method
- Fixed [6555] should_have_tag does not match documentation
- Fixed [6567] SyntaxError should not stop entire run
- Fixed [6558] integrated views look for template even when redirected
- Fixed [6547] response.should be_redirect broken in 0.7.0
- Applied [6471] Easy way to spec routes
- Applied [6587] Rspec on Rails displays "Spec::Rails::ContextFactory" as context name
- Applied [6514] Document has trivial typos.
- Added [6560] controller.session should be available before the action
- Added support for should_have_rjs :visual_effect
- Different printing and colours for unmet expectations (red) and other exceptions (magenta)
- Simplified method_missing on mock_methods to make it less invasive on partial mocks.

## Version 0.7.0

This is the "Grow up and eat your own dog food release". RSpec is now used on itself and we‘re no longer using Test::Unit to test it. Although, we are still extending Test::Unit for the rails plugin (indirectly - through ZenTest)

IMPORTANT NOTE: THIS RELEASE IS NOT 100% BACKWARDS COMPATIBLE TO 0.6.x

There are a few changes that will require that you change your existing specs.

RSpec now handles equality exactly like ruby does:

# actual.should_equal(expected) will pass if actual.equal?(expected) returns true # actual.should eql(expected) will pass if actual.eql?(expected) returns true # actual.should == expected will pass if actual == expected) returns true

At the high level, eql? implies equivalence, while equal? implies object identity. For more information on how ruby deals w/ equality, you should do this:

ri equal?

or look at this:

www.ruby-doc.org/core/classes/Object.html#M001057

Also, we left in should_be as a synonym for should_equal, so the only specs that should break are the ones using should_equal (which used to use `==` instead of `.equal?`).

Lastly, should_be used to handle true and false differently from any other values. We‘ve removed this special handling, so now actual.should_be true will fail for any value other than true (it used to pass for any non-nil, non-false value), and actual.should_be false will fail for any value other than false (it used to pass for nil or false).

Here‘s what you‘ll need to do to update your specs: # search for "should_equal" and replace with "should_eql" # run specs

If any specs still fail, they are probably related to should be_true or should_be_false using non-boolean values. Those you‘ll just have to inspect manually and adjust appropriately (sorry!).

[Validate]