Why functional test does not get failure?

Rails
1

The test:

test “should get new” do
get :new, :room_id => @room.name
assert_template(:ne)
end

the template new does not exists but the test does not get failure.
Why?

2

Add render_views

https://www.relishapp.com/rspec/rspec-rails/v/2-12/docs/controller-specs/render-views

Dheeraj K.

3

On 26 November 2012 12:45, Mauro [email protected] wrote:

The test:

test “should get new” do
get :new, :room_id => @room.name
assert_template(:ne)
end

the template new does not exists but the test does not get failure.
Why?

You have assert_template(:ne), not (:new) so it is looking for the
tempate ne. If that is just a typo in the posting here then please
copy/paste the actual test. Often such problems are due to typos in
the original code and by re-typing in the post the typo is removed (or
different).

Are you sure it is running the test? What happens if you add
assert(false) after the assert_template? Also what happens if you
perform the ‘new’ action from a browser?

Colin

4

On 26 November 2012 13:49, Dheeraj K. [email protected]
wrote:

Add render_views

https://www.relishapp.com/rspec/rspec-rails/v/2-12/docs/controller-specs/render-views

Is it only for rspec?
I’m using unit testing.

5

On 26 November 2012 18:25, Mauro [email protected] wrote:

Why?

If I add assert(false) then I have the failure.
I don’t undestand.

You did not answer my other question, what happens if you get that
action in the browser?

Colin

6

On 26 November 2012 15:43, Colin L. [email protected] wrote:

You have assert_template(:ne), not (:new) so it is looking for the
tempate ne. If that is just a typo in the posting here then please
copy/paste the actual test. Often such problems are due to typos in
the original code and by re-typing in the post the typo is removed (or
different).

Are you sure it is running the test? What happens if you add
assert(false) after the assert_template? Also what happens if you
perform the ‘new’ action from a browser?

It was a typo.
The test is:

test “should get new” do
get :new, :room_id => @room.name
assert_template(:ne)
end

I’m sure template ne does not exist but I have no failures.
If I add assert(false) then I have the failure.
I don’t undestand.

7

On 26 November 2012 22:23, Colin L. [email protected] wrote:

the template new does not exists but the test does not get failure.
perform the ‘new’ action from a browser?
I’m sure template ne does not exist but I have no failures.
If I add assert(false) then I have the failure.
I don’t undestand.

You did not answer my other question, what happens if you get that
action in the browser?

I wonder if it is this bug

If you use something like assert_template “something_that
_it_should_not_be” does it fail?

Colin

Colin

8

On 26 November 2012 23:28, Colin L. [email protected] wrote:

assert(false) after the assert_template? Also what happens if you

I’m sure template ne does not exist but I have no failures.
If I add assert(false) then I have the failure.
I don’t undestand.

You did not answer my other question, what happens if you get that
action in the browser?

If I do http://localhost:3000/rooms/stanza-1/reservations/ne

Couldn’t find Reservation with id=ne

If in the test I do
assert_template ‘ne’ or assert_template “ne” nothing change, I still
have no failure.
But the strange thing is:
assert_template “nene” or assert_template :nene, then I have a failure.
Really don’t understand.

9

On 27 November 2012 07:57, Mauro [email protected] wrote:

end
Are you sure it is running the test? What happens if you add

Couldn’t find Reservation with id=ne

If in the test I do
assert_template ‘ne’ or assert_template “ne” nothing change, I still
have no failure.
But the strange thing is:
assert_template “nene” or assert_template :nene, then I have a failure.
Really don’t understand.

Did you look at the bug I suggested, it looks like that is it.

Colin