Hi all,
Hoping you can help. I have a project using rspec 1.1.3 and rails
2.0.2. I've run into a small problem. Said project has a method in
application_helper.rb named "description". Whenever a spec test
fails, I see a message like so:
*snip*/vendor/plugins/rspec/lib/spec/runner/repo
Oi Helder,
On May 13, 2008, at 9:14 PM, Helder Ribeiro wrote:
On Tue, May 13, 2008 at 9:20 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
I wonder why OP doesn't create two records, call #most_recent, and
verify that the record returned is the one with the larger timestamp.
I'm sorry about the
On Tue, May 13, 2008 at 9:20 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
>
>
> I wonder why OP doesn't create two records, call #most_recent, and
> verify that the record returned is the one with the larger timestamp.
I'm sorry about the confusion here. Your idea sounds indeed better
(I'll explain
Wow, ok...I have had other trouble with REXML 3.1.7.3 being too
finicky...a few weeks back I found it enforcing declaration of XML
namespaces even though it doesn't seem to be actually doing anything
with namespaces except refusing to parse if they weren't properly
declared.
So, I did suspect
On 5/13/08, Jonathan Linowes <[EMAIL PROTECTED]> wrote:
>
> On May 13, 2008, at 6:39 PM, Helder Ribeiro wrote:
>
> > I'm not actually trying to test its behavior,
>
>
> quick! Duck! INCOMING...!
> ___
> rspec-users mailing list
> rspec-users@rubyforge
On 5/13/08, Pat Maddox <[EMAIL PROTECTED]> wrote:
> On 5/13/08, Jonathan Linowes <[EMAIL PROTECTED]> wrote:
> >
> > On May 13, 2008, at 6:39 PM, Helder Ribeiro wrote:
> >
> > > I'm not actually trying to test its behavior,
> >
> >
> > quick! Duck! INCOMING...!
> > __
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
Hi all,
We've recently been kicking around different ideas for simulating user
behaviour for the purposes of load testing our backend. We hit on the
idea of having user stories do double duty for both verifying behaviour
and (if selected stories were driven en-masse by a distributed network
o
Steve,
Did you have any luck with this? I ran into this problem today, with
Rcov 0.8.1.2.0, RSpec 1.1.3, and REXML 3.1.7.3.
-Alf
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/ma
On May 13, 2008, at 6:39 PM, Helder Ribeiro wrote:
I'm not actually trying to test its behavior,
quick! Duck! INCOMING...!
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Hi guys,
I'm just beginning to use RSpec and I ran into the issue of testing a
named_scope. I'm not actually trying to test its behavior, as it's not
my code, but I wanted to test at least that it's defined. I tried
doing this:
describe Post, ".most_recent" do
it "should be defined" do
Post
Hi,
I have just been having the same problem on windows using autotest and/or
rspec_autotest
I have successfully moved to rspec and rspec on rails 1.1.3 ZenTest 3.9.2
So if you were on windows the fix in case you still may need it is here
http://rspec.lighthouseapp.com/projects/5645/tickets/80-15
12 matches
Mail list logo