Hey Andre,
Thanks for your link .. I have seen it before but I did not have the
same issue, but I am thinking that it might well be worth my effort to
explore using sessions instead of cookies.
Thanks again.
On Jan 23, 2:48 am, and...@benjamin.dk wrote:
That seems like it :)
also about your
That seems like it :)
also about your cookie problem, is there anything that might look like
this:
http://stackoverflow.com/questions/9960732/rspec-vs-cookies-the-test-fails-even-if-the-applications-works-simulating-lo
all the best,
Andre
On Tuesday, 22 January 2013 15:00:21 UTC+1, fuzzy
So basically I think you are near the solution:
request tests, allow you to test requests(like put and others):
https://www.relishapp.com/rspec/rspec-rails/docs/request-specs/request-spec
when you doing integration testing at a feature level you dont make
requests(you would have instantiate the
Hi Andre,
Thanks for your reply.
I did see a 'put_via_redirect'.
So I would have to rewrite the test and use this command and it would
be testing the redirect which is a way to test the put?
I will give that a try.
Thanks again.
On Jan 22, 2:57 am, and...@benjamin.dk wrote:
So basically I
Hey fuzzy,
I think the first thing that is maybe wrong with your spec is that you are
trying to do a request inside of a describe.
it should be something like:
describe #update do
before { put employee_path(employee) }
it returns something or does something do
specify { response.should
Hi,
`specify` is actually just the same as `it`. It's just there because
sometimes it reads better. See here:
https://github.com/rspec/rspec-core/blob/master/lib/rspec/core/example_group.rb#L82
- Mirri
On Fri, Jan 18, 2013 at 5:22 PM, and...@benjamin.dk wrote:
Hey fuzzy,
I think the first
Hi Andre,
Thanks for your reply ... following is the
authentication_pages_spec.rb file which now resides in the spec/
features folder ... all of the tests pass except three.
require 'spec_helper'
describe Authentication do
subject { page }
describe signin do
Thanks Mirri for you post ... I had a look at the link ... are they
saying that 'specify' has now been superceded by 'it'?
On Jan 18, 10:17 am, Mirri Kim mirri@gmail.com wrote:
Hi,
`specify` is actually just the same as `it`. It's just there because
sometimes it reads better. See
Nope, just an alias.
On Sat, Jan 19, 2013 at 12:48 AM, fuzzy hlog...@gmail.com wrote:
Thanks Mirri for you post ... I had a look at the link ... are they
saying that 'specify' has now been superceded by 'it'?
On Jan 18, 10:17 am, Mirri Kim mirri@gmail.com wrote:
Hi,
`specify` is
I just read that Capybara does not do integration testing ... this I
found right at the bottom of the Capybara documentation page. So since
all Capybara tests reside in the spec/features folder, I moved the
submitting a PUT request to the Employees#update
test into the
10 matches
Mail list logo
