Aslak Hellesøy wrote:
> On Tue, Apr 14, 2009 at 12:08 AM, John Goodsen
> wrote:
>
>> OK, I'll reproduce in a simple example and create a ticket...
>>
>>
> Excellent - I'll get to it ASAP
I am also having the same issue with cucumber-java.
please refer - http://www.ruby-forum.com/topic/184342#n
On Fri, Apr 17, 2009 at 5:37 PM, Tom Stuart wrote:
> On 17 Apr 2009, at 15:03, Tom Stuart wrote:
>>
>> the bad commit is
>> http://github.com/dchelimsky/rspec-rails/commit/c9abdccedee97217f28e07ec824bb12cda1c9173
>
> I don't understand what's happening to rspec.rake in this commit. In
> particular
Mysql::Error: You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use near
'RELEASE SAVEPOINT active_record_1' at line 1: RELEASE SAVEPOINT
active_record_1
a rails ticket concerning this error which was marked invalid:
https:
On 17 Apr 2009, at 18:20, Aslak Hellesøy wrote:
Den 17. april. 2009 kl. 18.58 skrev Zach Dennis
:
On Fri, Apr 17, 2009 at 12:31 PM, Aslak Hellesøy
wrote:
Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
Is there currently a way to register a block to run after the
current
scenario c
On 17 Apr 2009, at 15:03, Tom Stuart wrote:
the bad commit is
http://github.com/dchelimsky/rspec-rails/commit/c9abdccedee97217f28e07ec824bb12cda1c9173
I don't understand what's happening to rspec.rake in this commit. In
particular, how is the "require 'spec/rake/spectask'" line meant to
su
Den 17. april. 2009 kl. 18.58 skrev Zach Dennis :
On Fri, Apr 17, 2009 at 12:31 PM, Aslak Hellesøy
wrote:
Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
Is there currently a way to register a block to run after the
current
scenario completes?
After.
After is used after *any* scen
On Fri, Apr 17, 2009 at 12:31 PM, Aslak Hellesøy
wrote:
>
>
> Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
>
>> Is there currently a way to register a block to run after the current
>> scenario completes?
>>
> After.
After is used after *any* scenario completes thought, right? If you
add an A
Matt Wynne wrote:
Is there currently a way to register a block to run after the current
scenario completes?
You could achieve the same thing with After and tags:
http://wiki.github.com/aslakhellesoy/cucumber/hooks
@please-clean-me
Scenario: dirty
...
After "@please-clean-me" do
#clean
On Fri, Apr 17, 2009 at 9:06 AM, Matt Wynne wrote:
>
> If you're interested, our use case is for pagination, where we explicitly
> set the length of a page to something much shorter than the default in a
> step, so that we only have to create a small number of objects to spill over
> onto another
Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
Is there currently a way to register a block to run after the
current scenario completes?
After.
If not, we've implemented one. Would anyone be interested in us
submitting it as a patch to Cucumber?
How is this different from After?
As
Is there currently a way to register a block to run after the current
scenario completes?
If not, we've implemented one. Would anyone be interested in us
submitting it as a patch to Cucumber?
Something like
Given "something that will not be rolled back after the scenario is
finished" do
I've been doing something similar. I think the benefit of having half
the steps(each can be negated) wins over the small impact it has on
step readability. Personally I started adding stuff like this(perhaps
not as DRY but simple enough):
Then /^the correspondence should (not )?have inclusi
On 17 Apr 2009, at 14:56, Tom Stuart wrote:
Can I git-bisect rspec and rspec-rails independently to try to track
down the problem, or are there going to be interdependent changes
between RSpec versions 1.2.0 and 1.2.1?
I tried this anyway; the bad commit is http://github.com/dchelimsky/rspec
On 17 Apr 2009, at 11:35, David Chelimsky wrote:
So there is something different about your environment than mine.
Hm, that's weird. Thanks for trying.
What OS? Ruby version? Versions of rspec/rspec-rails installed on
the system?
I'm trying to run everything vendored, so no RSpec (or Rails
Do you include cucumber in your gem config? When I include config.gem
'cucumber' in my config/environments/test.rb file and run "rake gems
RAILS_ENV=test", I receive the "can't activate , already activated
cucumber-0.3.0" error. The following are the gem config entries in my
test.rb file.
config
On Fri, Apr 17, 2009 at 5:45 AM, Tom Stuart wrote:
> Hi,
>
> I've been seeing the below problem since RSpec 1.2.1 on any machine that
> doesn't have the RSpec gems installed. 1.2.0 was fine. I'd hoping it would
> magically go away with later versions but it hasn't; does anyone have any
> clues?
>
Hi,
I've been seeing the below problem since RSpec 1.2.1 on any machine
that doesn't have the RSpec gems installed. 1.2.0 was fine. I'd hoping
it would magically go away with later versions but it hasn't; does
anyone have any clues?
--
$ git clone git://github.com/rails/rails testapp/ven
Hi Chuck,
Release 0.3.0 does include the fix
"""
begin
require 'spec/runner/differs/default' # RSpec >=1.2.4
rescue ::LoadError
require 'spec/expectations/differs/default' # RSpec <=1.2.3
end
"""
described in
http://github.com/aslakhellesoy/cucumber/commit/888b875bc17218fea77021edd059af7be53
18 matches
Mail list logo
