I have specs that ran fine in Rails 2.02/RSpec 1.13 that are failing on
Rails 2.1/RSpec 1.14.
There is one problem and one issue:
problem: sometimes (but not always) I get a NoMethodError referencing a
has_many association
issue: in helper specs, instance variables don't get set unless the
Helpe
I havne't take a look yet, but a couple of points:
- I was mistaken in my OP; I'm running REXML 3.1.7.3
- I saw a different post on a related topic that seemed to blame REXML
I'd been meaning to go back to an earlier version of REXML and see if that
fixed it since I had rcov working on this proje
On Sat, May 10, 2008 at 11:03 AM, Wayne Molina <[EMAIL PROTECTED]> wrote:
> Okay the issue seems to have been that it wasn't set to RSpec but Ruby
> on Rails. Changing it to RSpec seems to fix it... silly me, I guess :)
>
Same problem (and solution) for me, but ...
when I'm in a spec file and s
I have a case where I'm loading fixtures and a row added to a table in a
spec is around at the start of all subsequent specs.
When I set config.use_transactional_fixtures = false the fixtures load/clear
as expected.
Any ideas?
___
rspec-users mailing li
I assume you are running with '-f s' switch? Maybe its in your spec.opts
file ... maybe as --format progress?
If you change that to '-f p' you only see progress as a single '.' for each
passing test with errors at the end of the output.
Or maybe I'm not understanding the question.
On Wed, May 7
>
> Just because too objects have the same to_s representation don't mean
> they are equal:
The important equality in this case is what matters to the tester.
>
> This is a similar issue to Floats where there's more precision than
> the exernal representation shows.
>
Is there more precision t
I sent an inquiry to Prag Bookshelf but didn't hear anything -- saw
something online that led me to believe they were the publisher.
PeepCode has several RSpec screencasts.
On Sat, May 3, 2008 at 10:06 AM, Michael Schuerig <[EMAIL PROTECTED]>
wrote:
>
> I admit it, when it comes to rSpec, I'm la
I've seen that one too. Maybe has to do with how equality is defined in the
Time or DateTime class.
I get around it by comparing the string-ified versions:
foo.time.to_s.should == expected_time.to_s
On Sat, May 3, 2008 at 9:17 AM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> I occasionally get
Trying to run the 'spec:rcov' task and failing with error below.
I saw a post from last year with a different REXML error but it was a FixNum
issue.
Any help appreciated.
S
OS X
Ruby 1.8.6
Rails 2.02
RSpec-1.1.3 (build 20080131122909)
REXML 3.1.6
=
876 examples, 0 failures, 87 pending
/opt