similar to: Change setting to receive emails when posted?

This came up from an other issue where I needed to go check something in test::unit. Immediately when I dropped into the debugger in test::unit I saw something I have been missing: test unit by default shows a number of lines of code. Is there a way to make the rspec debugger do this? I am not sure if it is just me, but seems to me that when I moved to rspec, certain things which seemed to be

I apologize if this is a very dumb newbie issue, but I really want to experiment with the new "Story Runner" functionality in rspec and I''m having trouble using the trunk. I''ve tried in both windows and linux environments and have different problems on each. On linux, I execute svn co svn://rubyforge.org/var/svn/rspec/trunk to check out the trunk. This completes

Anyone is doing email testing with RSpec? Can you post some examples? Thank you, Laco M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070928/e6e6d5d2/attachment.html

I''m getting the following error when i either checkout or update from svn://rubyforge.org/var/svn/rspec/trunk svn: Error processing command ''mv'' in ''C:\work\rspec2\RSpec.tmbundle\Preferences'' svn: Can''t move source to dest svn: Cannot rename file ''C:\work\rspec2\RSpec.tmbundle\Preferences\.svn\tmp\text-base\Symbol List:

Hi Aslak, Thanks for the help. That bug is fixed in trunk. Here''s my path to recovery ... $ svn co svn://rubyforge.org/var/svn/rspec/trunk ~/tmp/rspec $ cd ~/tmp/rspec $ rake gem $ sudo gem install pkg/rspec-0.7.3.gem $ ./script/plugin install --force svn://rubyforge.org/var/svn/rspec/trunk/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec (required to regenerate

I''d like to write a test of a REST service wherein XML is submitted as the request entity. In Test::Unit on Rails, this seems to be possible in an integration test, but not in a functional test. RSpec uses the Rails functional test framework, as far as I can tell, so it suffers the same result; it tries to symbolize the keys of the ''parameters'' hash, except the

One more try? I just want the script to save the rspec output to an html file when the script is run. In this case, the script will be run from SciTE using F5, rather than by command line. Is there a way to specify this within the ruby script? ________________________________ From: rspec-users-bounces at rubyforge.org [mailto:rspec-users-bounces at rubyforge.org] On Behalf Of Adam Reed

I ran across a problem today in which some code ran fine in regular operation but failed in a test case. I scratched my head and thought "why would running from within the test harness change the behavior of my code?" Clearly it was the Heisenberg uncertainty principle in action! :) I discovered the root cause was that the rspec runner is setting the magical ruby global, $KCODE, to

Getting a strange error. In a story I have the following step: When "I submit a search name" do xhr :post, ''/searches'', {:search => {:given_name => "bob", :family_name => "smith"}} end I am getting: ArgumentError: wrong number of arguments (4 for 3) stories/searching_story_spec.rb:45 in "I submit a search name" But I only

I figured most of it out. The Spec::Rails stuff was something in the code which has been fixed by revision 3099. The test methods partially make sense. Since the test/unit code has been integrated, methods with test in them are automatically turned into specs. However, the test? method is in a lib file that isn''t directly loaded into the specs. It is a convenience method: def

I have a project with rspec installed as a plugin using svn:externals. Here are my externals: rspec_on_rails svn://rubyforge.org/var/svn/rspec/trunk/ rspec_on_rails rspec svn://rubyforge.org/var/svn/rspec/trunk/ rspec I just did an svn up on both and now have a version mismatch: ########################################################################

The RSpec Development Team is pleased to announce the release of RSpec-1.0.8. RSpec 1.0.6 is the "holy cow, batman, it''s been a long time since we released and there are a ton of bug fixes, patches and even new features" release. RSpec 1.0.7 and 1.0.8 deal with a regression introduced in 1.0.6 and a hiccup in releasing 1.0.7, respectively. == RSpec RSpec is a Behaviour Driven

The RSpec Development Team is pleased to announce Release Candidate 1 of RSpec 0.8.0. Since we''re doing a Release Candidate and we don''t really have a separate gem server set up, everything you need is tagged in subversion. See the install instructions below. As we noted a few weeks back, this release comprises a new approach to RSpec''s expectation syntax using

Hi, I''m new to RSpec. I have a question about how to write controller specs. Here''s a code generated by scaffolding (with Rspec). def do_get get :index end it "should be successful" do do_get response.should be_success end it "should render index template" do do_get response.should

On Thu, Apr 30, 2009 at 9:33 AM, Nicholas Van Weerdenburg <vanweerd at gmail.com> wrote: > I saw that a couple of days ago- very nice. Will that be added to RSpec? Sooner or later, yes, but it will be managed through the hash passed to the declarations: describe "something", :tags => [:a,:b] do it "does something", :tags > [:c] do etc You can already access

Thanks. I was hoping someone else who was using observers and rspec had run into this before and had a solution, as I always prefer the lazy way when possible ;). I''ll take a look at the rspec code base and see if I can figure it out well enough to submit a patch. Doug > > On 7/31/07, Doug Cole <dougcole at gmail.com> wrote: > > If I''m not mistaken those stub

The RSpec Development Team is pleased to announce the release of RSpec-0.8.0. This release introduces a new approach to handling expectations using Expression Matchers. It 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

Hi there, I''m having trouble with `rake spec:models`. It''s failing on: - 1 old rspec/rails project - all new rspec/rails projects But, it *is* working fine on my other (older) rspec/rails projects. All projects are on rspec & rails 1.0.8, Rails 1.2.3, os X ppc Here''s a fresh rspec/rails project with failing rake task $ rails test_app -d postgresql $ cd

RSpec-0.7.1 is now available. It comprises some bug fixes and a couple of new features. This is recommended for anybody who has already upgraded to 0.7.0. If you are running 0.6.x (or earlier), read this first: http://rspec.rubyforge.org/upgrade.html Install gem: gem install rspec Download: http://rubyforge.org/frs/?group_id=797 Release Notes:

The RSpec Development Team is extraordinarily pleased to announce the release of RSpec-1.0.0. == RSpec RSpec provides a Domain Specific Language for describing and verifying the behaviour of Ruby code with executable examples. Some people like to call these examples "tests". In fact, they are. But we believe that tests have equally important value as documentation and as a design aid,