On Mon, Mar 8, 2010 at 1:13 AM, Amit Kulkarni wrote:
> As per the list there are 3 versions of rspec released in Jan 2010 i.e.
> 1.3.0,1.3.1 and 1.3.2
> Also there are various versions starting from 2.
> So from all above version which one is a stable one so that i can
> install it.
Why would you
As per the list there are 3 versions of rspec released in Jan 2010 i.e.
1.3.0,1.3.1 and 1.3.2
Also there are various versions starting from 2.
So from all above version which one is a stable one so that i can
install it.
--
Posted via http://www.ruby-forum.com/.
_
On Sun, Mar 7, 2010 at 7:47 AM, Jarmo Pertman wrote:
> Thank you for your thoughts. Unfortunately it seems that after :each
> is not run if before :all fails...
>
> And after :all is ran after example_failed in formatter. Consider spec
> like this:
>
> describe "something" do
> before :all do
>
On Sun, Mar 7, 2010 at 10:11 AM, Russell Fine wrote:
> David Chelimsky wrote:
>> On Sun, Mar 7, 2010 at 9:45 AM, Russell Fine
>> wrote:
>>> Our app connects to two databases. �The main database (through
>>> ActiveRecord::Base) is automatically cleared before each test. �How do I
>>> force the cle
David Chelimsky wrote:
> On Sun, Mar 7, 2010 at 9:45 AM, Russell Fine
> wrote:
>> Our app connects to two databases. �The main database (through
>> ActiveRecord::Base) is automatically cleared before each test. �How do I
>> force the clear of the secondary database as well ?
>
> There's no impli
On Sun, Mar 7, 2010 at 9:45 AM, Russell Fine wrote:
> Our app connects to two databases. The main database (through
> ActiveRecord::Base) is automatically cleared before each test. How do I
> force the clear of the secondary database as well ?
There's no implicit support for this, so you'd have
Our app connects to two databases. The main database (through
ActiveRecord::Base) is automatically cleared before each test. How do I
force the clear of the secondary database as well ?
Thanks in advance...
Russell
--
Posted via http://www.ruby-forum.com/.
_
David Chelimsky wrote:
> So this presents an interesting problem :)
>
> My intent some time back was to deprecate :shared => true, not
> share_examples_for (which is aliased with shared_examples_for). Based
> on that, the rspec.info site is correct and Pat is incorrect. However,
> Pat didn't know
Thank you for your thoughts. Unfortunately it seems that after :each
is not run if before :all fails...
And after :all is ran after example_failed in formatter. Consider spec
like this:
describe "something" do
before :all do
p "before"
raise
end
it "does" do
p "it"
end
aft
On Sat, Mar 6, 2010 at 12:33 PM, Jarmo Pertman wrote:
> Since i'm using Watir
> then i usually open up the browser in
> before :all block like this:
> before :all do
> �...@browser = Watir::Browser.new
> end
>
> and then in the formatter I'm saving html of the browser - thus
> needing to access th
On Sat, Mar 6, 2010 at 10:21 PM, Nick Hoffman wrote:
> Pat Maddox wrote:
>> describe "something something", :shared => true do
>> ...
>> end
>>
>> describe "chunky bacon" do
>> it_should_behave_like "something something"
>> end
>
> BTW, is rspec.info supposed to be up-to-date? It still recomme
11 matches
Mail list logo
