On Dec 16, 2011, at 8:46 AM, LeeQ wrote:
> I am using Capybara in combination with rspec for integration testing
> of rails apps.
Even though you are using Capybara, they are still just specs. No reason why
"puts" won't work.
>
> I would like any errors (routing errors, errors in a controller
On Dec 7, 2011, at 10:03 AM, Bradley wrote:
> I'm trying to get a new spec task defined that is 'fast': that is, it skips
> all :type => :integration tests and any tests that have :slow => true set.
>
> We're using spec/integration instead of spec/requests, but I thought I read
> somewhere tha
Is there a proper naming scheme for custom formatters?
Thanks
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
I'm trying to get a new spec task defined that is 'fast': that is, it
skips all :type => :integration tests and any tests that have :slow => true
set.
We're using spec/integration instead of spec/requests, but I thought I read
somewhere that they're equivalent, ie that they would both be autom
All,
I've been having issues with my namespaced controllers and specs. I
receive the following errors only on my create and update actions
(with invalid parameters) and only on my namespaced controllers. My
non-namespaced controllers have similar specs and work well. The
application works as ex
Hello everyone,
I'm currently using rspec2 wit capybara to do some selenium tests. I
want to put this on a CI server and run the tests regularly. capybara
already has a functionality to save a screenshot. I'd like to save a
screenshot whenever a test does not pass.
So my question is:
How do i cu
I have a project that collects various application configurations across a
couple thousand servers and wants to validate settings are following
recommended values. For example, all weblogic servers should have a minimum
memory heap size of 512M. Any violators should be reported.
Being very imp
I am using Capybara in combination with rspec for integration testing
of rails apps.
I would like any errors (routing errors, errors in a controller,
anything) generated during a test to be printed the same as "puts"
statements in rspec's output. Is this possible? Additionally, is this
a reasonab