similar to: [Proposal] deprecate context() at the top level

I posted a ticket to lighthouse: http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/595-deprecate-integrate_views Please put your comments and thoughts there, as that is the best place for that discussion. I wanted to make it more "visible" so it could get wide community participation in case there are folks who absolutely feel integrate_views is necessary (considering that we

Hey all, Anybody use the --dry-run command line option? I''m planning to deprecate it if nobody has a compelling reason to keep it. Please post your comments in the ticket: https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/781-deprecate-dry-run Thanks, David

On Thu, Jul 9, 2009 at 5:40 AM, Daniel Tenner<daniel.rspec at tenner.org> wrote: > Hi all, > Like everyone (?), I use nested contexts to keep my specs well organised and > tidy. > However, I have a problem. I have various sets of specs that needs to > perform very time-expensive operations to set up the fixtures that will be > examined in the tests. Two specific examples:

Seems like the recently updated (and wonderful) textmate bundle does not take into account running individual tests that are in nested specs. Anybody else notice this? Any ideas? Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20080113/15d5cc2f/attachment.html

Hi everyone, We''ve moved ticket tracking for the rspec project to http://rspec.lighthouseapp.com! Thanks to a valiant effort from Chad Humphries, the move was done in an evening. For those of you on the rspec-devel list, apologies for the wealth of noise in this process. I set the trackers to stop sending email and they apparently didn''t listen. For those of you who submitted

Hi everybody. Per http://rubyforge.org/pipermail/rspec-users/2007-November/004572.html, we''re going to be moving ticket tracking over to lighthouse. We''d like to get this rolling sooner than later, but we''re fairly well occupied getting ready for the 1.1 release and writing rspec books :) We''ve got the lighthouse account set up. The thing we need to do to

How to run RSpec tests with JRuby in a Java project? I tried to run it with JRuby 1.7.0.preview1, rspec (2.10.0) rspec-core (2.10.1) rspec-expectations (2.10.0) rspec-mocks (2.10.1) rspec-rails (2.10.1) as follows: jruby -S rspec and got the error: javix at ubuntu:~/Development/rspec_jruby$ jruby -S rspec spec NameError: cannot load Java class com.models.Calculator for_name at

Hi all, Where can we add tickets for Cucumber? While trying to migrate a current project I ran into a snag.. specially that cucumber does not support multi-line steps like the edge rspec story runner (which makes sense since this was such a new feature to the story runner.) Anyways, I don''t have enough time at the moment to dig into it myself so I''d like to at least log it.

I get the following error when trying to run a spec command on a model test. The command is :- C:\Rspec Test\spec\models>spec bank_account_spec.rb The error is :- c:/jruby-1.5.0/lib/ruby/gems/1.8/gems/rspec-rails-1.3.0/lib/spec/rails/ matchers/ ar_be_valid.rb:2: uninitialized constant Spec::Rails (NameError) from c:/jruby-1.5.0/lib/ruby/gems/1.8/gems/rspec- rails-1.3.0/lib/spec/ra

The RSpec Development Team is pleased to announce the release of RSpec-1.0.3. == Changes This is the compatibility release! * Compatible with autotest!!!! (As of ZenTest 3.6.0 - see below) * Compatible with edge rails (as of r6825). * Compatible with jruby (since release 1.0.1) See http://rspec.rubyforge.org/changes.html for more detail. == About RSpec RSpec is a framework which provides

Hi, I download the last jruby version and install the rspec gem using jgem to install. After it, I export RUBYOPTS=rubygems to guarantee that the spec can be found. Trying to run the spec by normal mode I got: jonatas at branco:~/jruby-1.6.1$ jruby -S spec LoadError: no such file to load -- spec/autorun require at org/jruby/RubyKernel.java:1038 (root) at /usr/bin/spec:2 Trying to execute

Hey all, Rails just got tagged 2.0.0, and then 2.0.1. Unfortunately, it includes a changeset from yesterday that breaks rspec''s pre_commit task. I do not have cycles to address this until tonight, and I suspect that everyone is going to be grabbing the 2.0.1 release and become sad when RSpec won''t work with it. If any of you (especially Josh Knowles, who added the feature to

Hello RSpec''ers :-) In reply to this message: http://rubyforge.org/pipermail/rspec-users/2008-January/005477.html I provided a patch against CURRENT for fixing the latest issue introduced in 1.1.2 regarding colour and Windows. http://rspec.lighthouseapp.com/projects/5645/tickets/244-no-coloured-output-on-windows-due-missing-rubyopt just-warn-about-windows-no-colour.patch The patch

Hi all, I just submitted a patch to 2-3-stable on lighthouse and wanted to bring it to folks general attention. https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/896-be-a-little-more-discerning-about-which-exceptions-to-handle My explanation is a bit long-winded, but here''s the motivation for the patch, as explained in the lighthouse ticket: Perhaps I should open

Hi, We just spent half an afternoon figuring out why "jruby -S rake spec" didn''t generate any output at all (no warnings) on an edge rails app. We were seeing different behaviour on different boxes, and after a while figured out that it was related to a missing diff-lcs gem on one box. HTH, Stefan -- Bekk Open Source http://boss.bekk.no -------------- next part

I''m using RSpec on Rails and would like to clean up the backtraces, so I went looking for an RSpec equivalent to ThoughtBot''s Quiet Backtrace gem<http://thoughtbot.com/projects/quietbacktrace>. I found Spec::Runner::QuietBacktraceTweaker in the RDOCS, but I can''t figure out how to use it. Can I add something to spec_helper.rb that will utilize

Hi all, Running on OSX 10.5.3, Latest Rspec trunk, Rspec rails trunk, latest autotest gem and rails 2.1 I''ve lost my colour output in autotest. rake spec gives colour output, but autotest gives me black and white. It was working a little bit before, I think I upgraded to the latest versions of everything to get all the textmate snippets talking and being friendly to one another again

Hello everyone: I am currently assigned to test a big project which uses JRuby to build a web application. The reason of using JRuby is the web application is communicating with Java Service. I am writing test cases using Rspec and looking for a code coverage tool. Rcov is no doubt a nice code coverage tool. However, it is said that Rcov is not compatible with JRuby so far. Sigh....I can not

hello, when running rake spec, I''m getting a stack trace similar to the one mentioned in this ticket, which has been resolved: http://rspec.lighthouseapp.com/projects/5645/tickets/237 but from what I understood, if the project is using rspec 1.1.3 (as is the case with mine), this shouldn''t be happening? here''s the stack-trace: rake aborted! Command ruby

Hi folks. I''m very interested in the status of a port of any_instance from Mocha to RSpec. In particular I have a spec suite that I wrote using RSpec but with Mocha that depends heavily on any_instance. This is because it stubs out one or two methods from an underlying API. In attempting to convert the suite to RSpec mocks (because that''s what we''re using for the rest