Hello everyone,
I can't seem to figure out what I'm doing wrong on this test. I'm trying
to delete one of my models, criterion. All code can be found here,
please let me know if you need anything else! The rspec message is also
in there.
http://pastie.org/private/uaoexi6tmmsplsr3oj1a8w
Thank you
On Nov 29, 2010, at 8:05 PM, Jim Morris wrote:
> Hi David,
>
> I am using the current versions of everything rspec
> rspec (2.2.0,)
> rspec-core (2.2.1)
> rspec-expectations (2.2.0)
> rspec-mocks (2.2.0,)
> rspec-rails (2.2.0)
> webrat (0.7.2)
> rails(3.0.3)
>
> webrat is in Gemfile...
>
> gro
One more thing: If instead of "test 'something'" I write "def
test_something", like so:
require 'test_helper'
class FirstTest < ActiveSupport::TestCase
def test_something
assert_equal 42, 84
end
end
class SecondTest < ActiveSupport::TestCase
def test_something
assert_equal 42, 84
Hey everyone,
(I'm a newbie, so if I'm doing something wrong, please let me know! ^^)
I'm getting weird errors when I mix RSpec and Test::Unit tests. Here is
how to reproduce it with Rails 3:
Run "rails new railsapp". Add "gem 'rspec'" to the Gemfile, and create
test/unit/demo_test.rb with the
On Nov 30, 2010, at 10:28 AM, Jo Liss wrote:
> One more thing: If instead of "test 'something'" I write "def
> test_something", like so:
>
> require 'test_helper'
> class FirstTest < ActiveSupport::TestCase
> def test_something
>assert_equal 42, 84
> end
> end
> class SecondTest < ActiveS
On Tue, Nov 30, 2010 at 7:21 PM, David Chelimsky wrote:
> Or is there a problem you're trying to solve by intermingling them?
>
> I'd recommend keeping specs under the spec directory and run them separately
> from Test::Unit tests.
Ah, I see -- thanks for the quick reply!
So, I'm really trying
On Nov 30, 2010, at 2:11 PM, Jo Liss wrote:
> On Tue, Nov 30, 2010 at 7:21 PM, David Chelimsky wrote:
>> Or is there a problem you're trying to solve by intermingling them?
>>
>> I'd recommend keeping specs under the spec directory and run them separately
>> from Test::Unit tests.
>
> Ah, I se
On Tue, Nov 30, 2010 at 9:39 PM, David Chelimsky wrote:
> Yes, it does, which is why I like to use rspec for the whole thing :)
I see... In that case I think I'll go ahead and try migrating all my
tests to RSpec. And this ...
> https://github.com/glv/rspec-unit
... will definitely help on the
cool that did fix it. thanks
On Nov 30, 6:34 am, David Chelimsky wrote:
> On Nov 29, 2010, at 8:05 PM, Jim Morris wrote:
>
>
>
> > Hi David,
>
> > I am using the current versions of everything rspec
> > rspec (2.2.0,)
> > rspec-core (2.2.1)
> > rspec-expectations (2.2.0)
> > rspec-mocks (2.2.0,)
Just installed Rspec2 and noticed an immediate improvement in speed:
it broke all 899 passing tests on an important project in a matter of
seconds.
Sadly, I don't have the time to work my way through the multitude
upgrade errors (it's not just one error repeated), so I tried to
remove rspec2 and t
maybe just being stupid here but surely your using git or some sort of scm?
stash your progress with rspec 2 in another branch then reset your
current branch..
$ git reset --hard
On 1 December 2010 00:13, itsterry wrote:
> Just installed Rspec2 and noticed an immediate improvement in speed:
>
Jo,
You may look at shoulda if you want to continue to use test unit but want some
of the feel of rspec.
Good luck
Jed
Sent from my iPad
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
12 matches
Mail list logo
