No opinions on this anymore?
Jarmo
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Apr 19, 4:08 pm, David Chelimsky wrote:
> OK - I think I understand this better from this example. The idea here is
> that the matcher should keep asking if div.text == "after" until it returns
> true or 2 seconds have passed, whichever comes first, after which it fails.
> Correct? If so, th
On Apr 19, 2011, at 3:00 AM, Jarmo Pertman wrote:
> On Apr 18, 5:59 pm, David Chelimsky wrote:
>> What do you think of within(n).seconds { ... }?
>
> I'm not sure i understand it fully taking into account the examples
> above. Let me try to write them below:
> expect {
>link.click
> }.to cha
On Apr 18, 5:59 pm, David Chelimsky wrote:
> What do you think of within(n).seconds { ... }?
I'm not sure i understand it fully taking into account the examples
above. Let me try to write them below:
expect {
link.click
}.to change {div.text}.from("before").to("after").within(2).seconds
link
On Apr 18, 2011, at 9:39 AM, Jarmo Pertman wrote:
> On Apr 18, 4:21 pm, David Chelimsky wrote:
>>> but it doesn't
>>> conflict with matcher's #in anyway.
>>
>> It conflicts with the name :) It's a problem when we have one name that
>> means completely different things in different contexts.
>
On Apr 18, 4:21 pm, David Chelimsky wrote:
> > but it doesn't
> > conflict with matcher's #in anyway.
>
> It conflicts with the name :) It's a problem when we have one name that means
> completely different things in different contexts.
It depends :) That's the point of OOP that the methods wit
On Apr 18, 2011, at 7:49 AM, Jarmo Pertman wrote:
> On Apr 17, 6:58 pm, Justin Ko wrote:
>> On Sun, Apr 17, 2011 at 10:01 AM, David Chelimsky
>> wrote:
>>> On Apr 16, 2011, at 4:56 PM, Jarmo Pertman wrote:
>>
Hello!
>>
I've just added a new cool matcher #in into my framework WatirSpl
On 18 Apr 2011, at 13:49, Jarmo Pertman wrote:
> What does the "matcher extension" mean? E.g. some separate gem, which
> adds that method?
>
> Didn't know that ActiveSupport adds #in? to Object, but it doesn't
> conflict with matcher's #in anyway.
I think the point is that it clashes conceptual
What does the "matcher extension" mean? E.g. some separate gem, which
adds that method?
Didn't know that ActiveSupport adds #in? to Object, but it doesn't
conflict with matcher's #in anyway.
Jarmo
On Apr 17, 6:58 pm, Justin Ko wrote:
> On Sun, Apr 17, 2011 at 10:01 AM, David Chelimsky wrote:
>
On Sun, Apr 17, 2011 at 10:01 AM, David Chelimsky wrote:
> On Apr 16, 2011, at 4:56 PM, Jarmo Pertman wrote:
>
> > Hello!
> >
> > I've just added a new cool matcher #in into my framework WatirSplash
> > and thought that this could be integrated into RSpec directly actually
> > if there's any inter
On Apr 16, 2011, at 4:56 PM, Jarmo Pertman wrote:
> Hello!
>
> I've just added a new cool matcher #in into my framework WatirSplash
> and thought that this could be integrated into RSpec directly actually
> if there's any interest.
>
> WatirSplash uses Watir (or Watir-like) frameworks for testin
11 matches
Mail list logo
