On Fri, Jun 7, 2013 at 5:02 AM, Oliver Jesus wrote:
> Hello, I am new to RSpec and I've got error something like this:
> You have a nil object when you didn't expect it!
> You might have expected an instance of Array.
> The error occurred while evaluating nil.collect
>
> In my controller:
>
> def
Hello, I am new to RSpec and I've got error something like this:
You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.collect
In my controller:
def new
@employee_mst = EmployeeMst.new
@branch_mst = Br
Hi all,
Having not done any speccing for a few weeks I just spent ages puzzling
over why the following code wasn't working
it "should require a client" do
expect{ }.should raise_error ArgumentError
end
and giving me a
expected ArgumentError, got #__
On Thu, Aug 16, 2012 at 1:06 AM, Fahim Patel wrote:
> let me explain this problem
> ---rails destroy
Please post questions about Rails to the Rails mailing list:
https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-talk
__
let me explain this problem
---rails destroythis command
destroy model,scaffold etc .
problem is that if a model or other structure is exist than ,this command
will destroy all the related file to it...good ..till now no
problem..
On Tue, Apr 10, 2012 at 5:28 PM, Ryan Macy wrote:
> /Users/ryanmacy/.rvm/gems/ruby-1.9.2-p318/gems/ffi-1.0.11/lib/ffi/
> library.rb:121:in `block in ffi_lib': Could not open library '/usr/lib/
> liblpcapi_ssl.so': dlopen(/usr/lib/liblpcapi_ssl.so, 5): image not
> found (LoadError)
> from /U
/Users/ryanmacy/.rvm/gems/ruby-1.9.2-p318/gems/ffi-1.0.11/lib/ffi/
library.rb:121:in `block in ffi_lib': Could not open library '/usr/lib/
liblpcapi_ssl.so': dlopen(/usr/lib/liblpcapi_ssl.so, 5): image not
found (LoadError)
from /Users/ryanmacy/.rvm/gems/ruby-1.9.2-p318/gems/ffi-1.0.11/lib/
On Mar 28, 2011, at 8:04 PM, Carlos Torres wrote:
> I'm new to Rails and I was planning on trying out RSpec. When I try to
> execute the rspec command on Debian v6.0.1, I get the output below:
>
> k4ru050@DebianBox:~/Desktop/rails_projects/sample_app/spec$ bundle exec rspec
> spec/controllers
I just wanted to confirm that you've verified that the exact same
codebase has its specs run correctly on a different OS (or flavour of
linux, even)?
Best,
Sidu.
http://c42.in
http://about.me/ponnappa
On 29 March 2011 06:34, Carlos Torres wrote:
> I'm new to Rails and I was planning on trying
I'm new to Rails and I was planning on trying out RSpec. When I try to
execute the rspec command on Debian v6.0.1, I get the output below:
k4ru050@DebianBox:~/Desktop/rails_projects/sample_app/spec$ bundle exec
rspec spec/controllers
/home/k4ru050/.rvm/gems/ruby-1.9.2-p180@rails3tutorial/gems/rspe
Rafael Felix wrote in post #949668:
>
> I don't know what method we use to check my views?
>
> thanks for all
> regards
if you want to test views with have_tag and rspec2 try this gem:
https://rubygems.org/gems/rspec2-rails-views-matchers
--
Posted via http://www.ruby-forum.com/.
__
On Jan 5, 2011, at 4:06 PM, Steve Hull wrote:
> David Chelimsky wrote in post #949683:
>> have_tag wrapped assert_select in a way that was very brittle. Also
>> Webrat and Capybara matchers are better :)
>
> Any tips on how we can use the Capybara matchers in our helper specs?
> Seems like a re
David Chelimsky wrote in post #949683:
> have_tag wrapped assert_select in a way that was very brittle. Also
> Webrat and Capybara matchers are better :)
Any tips on how we can use the Capybara matchers in our helper specs?
Seems like a reasonable thing to want to do, since helpers are typically
On Oct 12, 2010, at 7:57 PM, Rafael Felix wrote:
> On Oct 12, 9:37 pm, David Chelimsky wrote:
>> On Oct 12, 2010, at 7:33 PM, Rafael Felix wrote:
>>
>>> On Oct 12, 9:24 pm, David Chelimsky wrote:
On Oct 12, 2010, at 6:38 PM, Rafael Felix wrote:
>>
> Well, I'be looking for test my views
Woah, now works the test, thanks for response. Why the have_tag has
removed from RSpec 2?
regards
On Oct 12, 9:37 pm, David Chelimsky wrote:
> On Oct 12, 2010, at 7:33 PM, Rafael Felix wrote:
>
>
>
>
>
>
>
> > On Oct 12, 9:24 pm, David Chelimsky wrote:
> >> On Oct 12, 2010, at 6:38 PM, Rafael F
On Oct 12, 2010, at 7:33 PM, Rafael Felix wrote:
>
> On Oct 12, 9:24 pm, David Chelimsky wrote:
>> On Oct 12, 2010, at 6:38 PM, Rafael Felix wrote:
>>
>>
>>
>>
>>
>>> Well, I'be looking for test my views with rspec, looking the
>>> documentation athttp://rspec.info/rails/writing/views.html
Changing my test, for user assert_select, an new error is raised
it "should be have an p when no company for the tag was found" do
assigns[:name] = "Teste"
render
rendered.should assert_select('h4', "Visualizando empresas pela
Tag")
end
And the error:
Failures:
1) tags/search.htm
On Oct 12, 2010, at 6:38 PM, Rafael Felix wrote:
> Well, I'be looking for test my views with rspec, looking the
> documentation at http://rspec.info/rails/writing/views.html we see
> some examples, in RSpec 2 the response was deprecated and now I'm
> using the rendered instead, but this code
>
>
Well, I'be looking for test my views with rspec, looking the
documentation at http://rspec.info/rails/writing/views.html we see
some examples, in RSpec 2 the response was deprecated and now I'm
using the rendered instead, but this code
describe "tags/search.html.erb" do
it "should be have an p w
On Sep 4, 2010, at 12:25 PM, Paul Denlinger wrote:
> Just tried to run rspec and got this error message even though the
> rspec gem installed successfully:
>
>
> $ spec hello_spec.rb
> /Users/pdenlinger/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems.rb:
> 340:in `bin_path': can't find executa
Just tried to run rspec and got this error message even though the
rspec gem installed successfully:
$ spec hello_spec.rb
/Users/pdenlinger/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems.rb:
340:in `bin_path': can't find executable spec for rspec-2.0.0.beta.18
(Gem::Exception)
from /Us
Hi David,
I am using autospec and it by default runs using 'spec' rather than
'script/spec'. Can you give me a quick direction of how to configure it to
use the former.
Thanks,
Amiruddin Nagri,
Bangalore, 560008, KA
India
Y! IM : amir_na...@yahoo.com
GTalk : amir.na...@gmail.com
On Tue, Jun 8
On Jun 9, 2010, at 4:45 PM, Amiruddin Nagri wrote:
> Hi David,
>
> I am using autospec and it by default runs using 'spec' rather than
> 'script/spec'. Can you give me a quick direction of how to configure it to
> use the former.
Take a look at http://github.com/rspec/rspec-core/blob/master/Up
On Jun 8, 2010, at 4:05 AM, Amiruddin Nagri wrote:
> I have a bunch of rspec test that are running fine when I don't freeze them
> in the vendor folder.
>
> But when I freeze the rails gems, the spec starts failing with the stack
>
> /home/xuser/myprojects/xproject/config/../vendor/rails/railti
I have a bunch of rspec test that are running fine when I don't freeze them
in the vendor folder.
But when I freeze the rails gems, the spec starts failing with the stack
/home/xuser/myprojects/xproject/config/../vendor/rails/railties/lib/initializer.rb:271:in
`require_frameworks': can't activate
On 3 Mag, 14:14, David Chelimsky wrote:
> I see the same error (hadn't run against 1.9.2 in a while). Reported
> tohttp://github.com/rspec/rspec-rails/issues/issue/41
Thanks David.
I added this to my spec_helper.rb file
Rspec::Mocks::Mock.module_eval do
alias to_str to_s
end
and now it se
On May 3, 2010, at 6:06 AM, andrea longhi wrote:
> Hello *,
> I started today to test rspec current beta with ruby 1.9.2 and rails
> 3.0. I created a basic app with a scaffold. I am experiencing a lot of
> failures in the geneated controller spec. I am pasting the complete
> error string:
>
> ca
Hello *,
I started today to test rspec current beta with ruby 1.9.2 and rails
3.0. I created a basic app with a scaffold. I am experiencing a lot of
failures in the geneated controller spec. I am pasting the complete
error string:
can't convert Rspec::Mocks::Mock to String (Rspec::Mocks::Mock#to_
This happens when you generate tests pre-Rails 2.3 then upgrade to Rails
2.3.
go to test/test_helper.rb and change:
class Test::Unit::testCase
to:
class ActiveSupport::TestCase
http://www.datatravels.com/technotes/2009/04/21/rails-error-undefined-method-use_transactional_fix/
waseem ahmad wro
Please provide more context. There should be a stack trace that tells you at
which line the error occurs.
This problem typically occurs when you have a method that calls itself and has
no return mechanism. Sometimes that can be a sloppily implemented
method_missing.
I can't see anything obvi
hi, guys
i write follow code :
it "The default should be based on readers to recommend a book
tastes" do
@pick_book = mock_model(PickBook)
@pick_books = [...@pick_book]
@recommend_count = 1
PickBook.should_receive(:recommend_books).with(@recommend_
On Sat, Dec 12, 2009 at 11:28 AM, athem wrote:
> Hello,
>
> I've written the following simple rspec test that I'm trying to run
> (rspec 1.2.9) standalone (outside Rails) from the command line and
> getting the following error. Any idea for how to fix this? Thanks.
>
> $> spec foo_rspec.rb
>
>
Hello,
I've written the following simple rspec test that I'm trying to run
(rspec 1.2.9) standalone (outside Rails) from the command line and
getting the following error. Any idea for how to fix this? Thanks.
$> spec foo_rspec.rb
/Users/athem/.gem/ruby/1.8/gems/rspec-1.2.9/lib/spec/runner/opt
On Nov 23, 2009, at 11:12 PM, David Chelimsky wrote:
>
>
> On Mon, Nov 23, 2009 at 9:36 PM, Scott Taylor wrote:
>
> On Nov 23, 2009, at 9:35 PM, David Chelimsky wrote:
>
>> On Fri, Nov 20, 2009 at 9:06 PM, Bogdan Dumitru wrote:
>> The syntax for use_fakefs changed in version 0.2.1 and the f
On Mon, Nov 23, 2009 at 9:36 PM, Scott Taylor wrote:
>
> On Nov 23, 2009, at 9:35 PM, David Chelimsky wrote:
>
> On Fri, Nov 20, 2009 at 9:06 PM, Bogdan Dumitru wrote:
>
>> The syntax for use_fakefs changed in version 0.2.1 and the fixtures
>> for rspec are generating errors, but it can be solved
On Nov 23, 2009, at 9:35 PM, David Chelimsky wrote:
> On Fri, Nov 20, 2009 at 9:06 PM, Bogdan Dumitru wrote:
> The syntax for use_fakefs changed in version 0.2.1 and the fixtures
> for rspec are generating errors, but it can be solved easily.
> Have to change ...
> describe "smth" do
> extend
On Fri, Nov 20, 2009 at 9:06 PM, Bogdan Dumitru wrote:
> The syntax for use_fakefs changed in version 0.2.1 and the fixtures
> for rspec are generating errors, but it can be solved easily.
> Have to change ...
> describe "smth" do
> extend FakeFS::SpecHelpers
> use_fakefs
> ...
> end
> To..
The syntax for use_fakefs changed in version 0.2.1 and the fixtures
for rspec are generating errors, but it can be solved easily.
Have to change ...
describe "smth" do
extend FakeFS::SpecHelpers
use_fakefs
...
end
To...
extend FakeFS::SpecHelpers
use_fakefs describe "smth" do ... end
As i
On Sun, Nov 8, 2009 at 2:35 AM, Conrad Taylor wrote:
> David, I'm still seeing the issue. Thus, here's a transcript of my
> activity:
>
> http://pastie.org/688639
$ gem which fakefs
(checking gem bmabey-fakefs-0.1.1.1 for fakefs)
/Users/david/.rvm/gems/ruby/1.9.1/gems/bmabey-fakefs-0.1.1.1/lib
David, I'm still seeing the issue. Thus, here's a transcript of my
activity:
http://pastie.org/688639
-Conrad
On Nov 4, 2:28 pm, David Chelimsky wrote:
> On Tue, Nov 3, 2009 at 7:25 AM, Conrad Taylor wrote:
> > Hi, 'rake spec' failed to run on Ruby 1.9.1p243 and RSpec 1.2.9.
>
> Hi Conrad,
>
On Tue, Nov 3, 2009 at 7:25 AM, Conrad Taylor wrote:
> Hi, 'rake spec' failed to run on Ruby 1.9.1p243 and RSpec 1.2.9.
Hi Conrad,
If this was a problem in the gem, it is now fixed:
$ rvm 1.9.1
$ which ruby
/Users/david/.rvm/ruby-1.9.1-p243/bin/ruby
$ rake spec
...
1522 examples, 0 failures,
Hi, 'rake spec' failed to run on Ruby 1.9.1p243 and RSpec 1.2.9. I'm
getting the following error message when I run the specs:
/opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.2.9/spec/spec/runner/
option_parser_spec.rb:21:in `block (2 levels) in ':
wrong number of arguments (0 for 1) (ArgumentError)
On Tue, Jul 28, 2009 at 8:03 PM, rogerdpack wrote:
> Question.
>
> Currently with this test:
>
> instance.splatted3().should raise_error(ArgumentError)
This should be:
lambda { instance.splatted3() }.should raise_error(ArgumentError)
See http://rspec.rubyforge.org/rspec/1.2.8/classes/Spec/Mat
Question.
Currently with this test:
instance.splatted3().should raise_error(ArgumentError)
if it's broken, and returns [] instead of raising appropriately,
currently the error reported is:
expected ArgumentError, got #
shouldn't this have been reported as
expected ArgumentError, got []
?
Mu
David Chelimsky wrote:
> On Wed, May 20, 2009 at 2:47 AM, Amit Kulkarni
> wrote:
It is not the case that i will always run spec from the root project.So
>> Thank a lot.
>> But is the case that all controller specs are run from the root
>> directory.
>> I had had written spec models and it ru
On Wed, May 20, 2009 at 2:47 AM, Amit Kulkarni wrote:
> David Chelimsky wrote:
>> On Wed, May 20, 2009 at 1:47 AM, Amit Kulkarni
>> wrote:
> script/spec spec/controllers/channels_controller_spec1.rb
Hey It worked thanks a lot. :-)
Can you tell me the difference why it was
David Chelimsky wrote:
> On Wed, May 20, 2009 at 1:47 AM, Amit Kulkarni
> wrote:
script/spec spec/controllers/channels_controller_spec1.rb
>>>
>>> Hey It worked thanks a lot. :-)
>>>
>>> Can you tell me the difference why it was not running earlier and now it
>>> is running.Just for my under
On Wed, May 20, 2009 at 1:47 AM, Amit Kulkarni wrote:
> Amit Kulkarni wrote:
>> David Chelimsky wrote:
>>> On Tue, May 19, 2009 at 9:04 AM, Amit Kulkarni
>>> wrote:
but i am getting the same error which says RuntimeError in
Files/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_
David Chelimsky wrote:
> On Tue, May 19, 2009 at 9:04 AM, Amit Kulkarni
> wrote:
>> but i am getting the same error which says RuntimeError in
>> Files/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_control
>> ./channels_controller_spec1.rb:149:
> It looks like you're calling the file f
Amit Kulkarni wrote:
> David Chelimsky wrote:
>> On Tue, May 19, 2009 at 9:04 AM, Amit Kulkarni
>> wrote:
>>> but i am getting the same error which says RuntimeError in
>>> Files/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_control
>>> ./channels_controller_spec1.rb:149:
>> It looks l
On Tue, May 19, 2009 at 9:04 AM, Amit Kulkarni wrote:
> Hi,
>
> Thanks for quick response
>
> My channels_controller_spec.rb file is inside controller spec only
> i.e. PROJECT_ROOT/spec/controllers/channels_controller_spec.rb.
>
> As per your suggestion i removed the setup method and moved
> user_
Hi,
Thanks for quick response
My channels_controller_spec.rb file is inside controller spec only
i.e. PROJECT_ROOT/spec/controllers/channels_controller_spec.rb.
As per your suggestion i removed the setup method and moved
user_attributes under example groups.
but i am getting the same error whi
On Tue, May 19, 2009 at 3:30 AM, Amit Kulkarni wrote:
> Ruby version : 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]
> rspec - 1.2.4
> rails - 2.1.2
> OS - Vista Home
> I am running a single file by the command
> spec channels_controller(filename)_spec.rb
Where is this file? For rspec-rails to k
Ruby version : 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]
rspec - 1.2.4
rails - 2.1.2
OS - Vista Home
I am running a single file by the command
spec channels_controller(filename)_spec.rb
Contents of the file:
require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')
def setup
@c
On Fri, May 8, 2009 at 4:03 AM, Amit Kulkarni wrote:
> Hello,
>
> I am trying to execute controller spec but it gives me error which
> says
>
> @controller is nil: make sure you set it in your test's setup
> method.
>
> I tried to search for the solution but till now no success :(
>
> Foll
Hello,
I am trying to execute controller spec but it gives me error which
says
@controller is nil: make sure you set it in your test's setup
method.
I tried to search for the solution but till now no success :(
Following is the description of the controller spec.
describe ChannelCate
> Hi
>
> I am experiencing a problem when using Cucumber with Norwegian language. I
> have added the files and the stacktrace on gist:
> http://gist.github.com/102438
>
> The problem is that when we use Når (When) and Så (Then) in the steps file,
> it fails with a parser error. If we switch all Når
Hi
I am experiencing a problem when using Cucumber with Norwegian language. I
have added the files and the stacktrace on gist:
http://gist.github.com/102438
The problem is that when we use Når (When) and Så (Then) in the steps file,
it fails with a parser error. If we switch all Når and Så with G
On Wed, Jan 7, 2009 at 11:26 PM, waseem ahmad wrote:
> I have both the rspec 1.1.11 and rspec-rails 1.1.11 as gems. I had them
> plugged in my application too. When I removed them from my application the
> problem was solved. The version of both the gems and plugins are same.
>
> Why did this happ
I have both the rspec 1.1.11 and rspec-rails 1.1.11 as gems. I had them
plugged in my application too. When I removed them from my application the
problem was solved. The version of both the gems and plugins are same.
Why did this happen?
--
Waseem
RwrWrwRwrWrwRwrWrwRwrWrwR
B
On Wed, Jan 7, 2009 at 10:26 AM, David Chelimsky wrote:
> On Wed, Jan 7, 2009 at 12:20 PM, Mark Wilden wrote:
> > FWIW, I was getting this error yesterday. I completely uninstalled rspec
> and
> > rspec-rails (including David's code from GitHub) and reinstalled, and it
> > "went away."
>
> Which
On Wed, Jan 7, 2009 at 12:20 PM, Mark Wilden wrote:
> FWIW, I was getting this error yesterday. I completely uninstalled rspec and
> rspec-rails (including David's code from GitHub) and reinstalled, and it
> "went away."
Which version did you install after removing everything?
>
> ///ark
>
> On
FWIW, I was getting this error yesterday. I completely uninstalled rspec and
rspec-rails (including David's code from GitHub) and reinstalled, and it
"went away."
///ark
On Wed, Jan 7, 2009 at 1:49 AM, waseem ahmad wrote:
>
>
> On Wed, Jan 7, 2009 at 2:55 PM, David Chelimsky wrote:
>
>> Seems l
On Wed, Jan 7, 2009 at 2:55 PM, David Chelimsky wrote:
> Seems like it's not loading up rspec-rails' Configuration object. In
> order for that to happen implicitly, the specs need to be in any of
> spec/models, spec/controllers, spec/views, spec/helpers. Is your file
> in one of those?
>
>
Yeah th
On Wed, Jan 7, 2009 at 12:29 AM, waseem ahmad wrote:
> Hi,
>
> I get this error when I do
>
> $spec /spec/any_spec
>
> /home/waseem/app/spec/spec_helper.rb:14: undefined method
> `use_transactional_fixtures=' for #
> (NoMethodError)
> from /usr/lib/ruby/gems/1.8/gems/rspec-1.1.11/lib/spec/
this may help:
http://themomorohoax.com/2008/12/17/rails-2-3-tests
On Wed, Jan 7, 2009 at 12:29 AM, waseem ahmad wrote:
> Hi,
>
> I get this error when I do
>
> $spec /spec/any_spec
>
> /home/waseem/app/spec/spec_helper.rb:14: undefined method
> `use_transactional_fixtures=' for #
> (NoMeth
Hi,
I get this error when I do
$spec /spec/any_spec
/home/waseem/app/spec/spec_helper.rb:14: undefined method
`use_transactional_fixtures=' for #
(NoMethodError)
from /usr/lib/ruby/gems/1.8/gems/rspec-1.1.11/lib/spec/runner.rb:184:in
`configure'
from /home/waseem/app/spec/spec_helper
Josh Knowles wrote:
>There are forks out on github which have specs and have
> fixed the problem with validate_uniqueness_of.
I have test a plugin with that fixed (from negonicrac) and it still has
the same problem for me.
I see that this plugin already has specs, and want to try them.
But I don
On Mon, Dec 29, 2008 at 7:20 AM, David Chelimsky wrote:
> I don't see any specs for the rspec-on-rails-matchers library on
> github, and no activity in 9 months, so I'm guessing that it is
> incomplete/no longer being maintained.
>
> Josh Knowles, if you're reading this, can you respond?
I unfort
David Chelimsky wrote:
> I'm not really sure why this is stubbing find, or why the stub value
> is true instead of a model. Actually, I don't even see how this would
> specify validating uniqueness of the attribute without very specific
> setup:
>
> first = Centro.create(:nombre => "example")
> s
On Mon, Dec 29, 2008 at 5:04 AM, Juanma Cervera wrote:
> I am fighting with an error using rspec-on-rails-matchers.
>
> I have a model called "Centro" based in this table
>
> create_table "centros", :force => true do |t|
>t.string "nombre"
>t.string "cif"
>t.string "domicilio"
>
Well, it seems tha the error is indeed in the stubbing of the find
method in the class of the model.
def validate_uniqueness_of(attribute)
return simple_matcher("model to validate the uniqueness of
#{attribute}") do |model|
model.class.stub!(:find).and_return(true)
!model.valid? && mod
I am fighting with an error using rspec-on-rails-matchers.
I have a model called "Centro" based in this table
create_table "centros", :force => true do |t|
t.string "nombre"
t.string "cif"
t.string "domicilio"
t.string "codigo_postal"
t.string "poblacion"
t.str
On Sat, Oct 18, 2008 at 1:55 PM, Scott Burton <[EMAIL PROTECTED]> wrote:
> Hi all;
>
> I'm getting a weird error from the rspec gem when using rake to load
> fixtures in rails:
>
> % rake db:fixtures:load RAILS_ENV=test
> /path/to/Ruby/Gems/1.8/gems/rspec-1.1.8/lib/spec/runner/options.rb:229:in
> `
Hi all;
I'm getting a weird error from the rspec gem when using rake to load
fixtures in rails:
% rake db:fixtures:load RAILS_ENV=test
/path/to/Ruby/Gems/1.8/gems/rspec-1.1.8/lib/spec/runner/options.rb:
229:in `files_to_load': File or directory not found: db:fixtures:load
(RuntimeError)
f
Hi David,
On 28/08/2008, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 8:22 AM, aidy lewis <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I think the scenario based way of defining acceptance tests is akin to
> > scenarios in use-cases.
> >
> > In use-cases we can have a ha
On Thu, Aug 28, 2008 at 8:22 AM, aidy lewis <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I think the scenario based way of defining acceptance tests is akin to
> scenarios in use-cases.
>
> In use-cases we can have a happy path with extends for error conditions etc.
>
> Should I create extra scenarios for
Hi,
I think the scenario based way of defining acceptance tests is akin to
scenarios in use-cases.
In use-cases we can have a happy path with extends for error conditions etc.
Should I create extra scenarios for my error conditions (making my
tests less understandable) or should I create a new e
I have been using autotest/zentest 3.5.0 with my rails 2.0.2 and rspec. I
upgraded my gems and got 3.9.3 and had a problem. I went back to 3.5.0 and
it worked. I stayed there until moving to rails 2.1. I again updated my gems
and got 3.10. This one had the same problem. This time I need to figure
Ticket files -- #407.
& cheers for the link, man -- I'll check that now.
Doug.
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On May 23, 2008, at 5:17 AM, Doug Livesey wrote:
Hi -- I've tried to get the latest RSpec by following the instructions
at:
http://github.com/dchelimsky/rspec/wikis/home
I clone the repository just fine, but then, when I 'rake gem', I get
the
following errors:
svn: '..' is not a working
Hi -- I've tried to get the latest RSpec by following the instructions
at:
http://github.com/dchelimsky/rspec/wikis/home
I clone the repository just fine, but then, when I 'rake gem', I get the
following errors:
svn: '..' is not a working copy
svn: Can't open file '../.svn/entries': No such f
It actually turned out to an invalid syntax in my controller,
completely unrelated.
Guess thats what I get for not checking my syntax before diving in.
On Apr 7, 2:14 pm, "David Chelimsky" <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 4, 2008 at 12:46 PM, Jacob <[EMAIL PROTECTED]> wrote:
> > I am tryi
On Fri, Apr 4, 2008 at 12:46 PM, Jacob <[EMAIL PROTECTED]> wrote:
> I am trying to test my controllers with RSpec and from the examples I
> have found it is as easy as this:
>
> describe SessionsController do
>
> it "should render login template" do
> get 'new'
> response.should render_
I am trying to test my controllers with RSpec and from the examples I
have found it is as easy as this:
describe SessionsController do
it "should render login template" do
get 'new'
response.should render_template(:login)
end
end
However both get and post raise "wrong number of arg
Ooops there was a typo on the method causing the error. It should be:
It is this test that fails
it "should make the relation to the users" do
@account.should_receive(:users) # removed the .and_return
do_post
end
Is there a better way to test that the data is being loaded into the
related
I can't figure out why I am getting an error for one of the tests below:
describe AccountsController, "POST" do
before :each do
@user = mock_model(User)
@account = mock_model(Account, :id => 1, :valid => true, :save =>
true, :users => mock("users", :build => @user
Hi all,
I'm just getting started with rspec. I'm using trunk rspec with edge
rails. I get an error on migration though, here it is:
rake db:migrate RAILS_ENV="test" --trace
(in /home/pat/railsapp)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
rake abo
88 matches
Mail list logo
