1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
require 'spec_helper'
# This spec was generated by rspec-rails when you ran the scaffold generator.
# It demonstrates how one might use RSpec to specify the controller code that
# was generated by Rails when you ran the scaffold generator.
#
# It assumes that the implementation code is generated by the rails scaffold
# generator. If you are using any extension libraries to generate different
# controller code, this generated spec may or may not pass.
#
# It only uses APIs available in rails and/or rspec-rails. There are a number
# of tools you can use to make these specs even more expressive, but we're
# sticking to rails and rspec-rails APIs to keep things simple and stable.
#
# Compared to earlier versions of this generator, there is very limited use of
# stubs and message expectations in this spec. Stubs are only used when there
# is no simpler way to get a handle on the object needed for the example.
# Message expectations are only used when there is no simpler way to specify
# that an instance is receiving a specific message.
describe MatchesController do
# This should return the minimal set of attributes required to create a valid
# Match. As you add validations to Match, be sure to
# adjust the attributes here as well.
let(:valid_attributes) { { "tournament" => "" } }
# This should return the minimal set of values that should be in the session
# in order to pass any filters (e.g. authentication) defined in
# MatchesController. Be sure to keep this updated too.
let(:valid_session) { {} }
describe "GET index" do
it "assigns all matches as @matches" do
match = Match.create! valid_attributes
get :index, {}, valid_session
assigns(:matches).should eq([match])
end
end
describe "GET show" do
it "assigns the requested match as @match" do
match = Match.create! valid_attributes
get :show, {:id => match.to_param}, valid_session
assigns(:match).should eq(match)
end
end
describe "GET new" do
it "assigns a new match as @match" do
get :new, {}, valid_session
assigns(:match).should be_a_new(Match)
end
end
describe "GET edit" do
it "assigns the requested match as @match" do
match = Match.create! valid_attributes
get :edit, {:id => match.to_param}, valid_session
assigns(:match).should eq(match)
end
end
describe "POST create" do
describe "with valid params" do
it "creates a new Match" do
expect {
post :create, {:match => valid_attributes}, valid_session
}.to change(Match, :count).by(1)
end
it "assigns a newly created match as @match" do
post :create, {:match => valid_attributes}, valid_session
assigns(:match).should be_a(Match)
assigns(:match).should be_persisted
end
it "redirects to the created match" do
post :create, {:match => valid_attributes}, valid_session
response.should redirect_to(Match.last)
end
end
describe "with invalid params" do
it "assigns a newly created but unsaved match as @match" do
# Trigger the behavior that occurs when invalid params are submitted
Match.any_instance.stub(:save).and_return(false)
post :create, {:match => { "tournament" => "invalid value" }}, valid_session
assigns(:match).should be_a_new(Match)
end
it "re-renders the 'new' template" do
# Trigger the behavior that occurs when invalid params are submitted
Match.any_instance.stub(:save).and_return(false)
post :create, {:match => { "tournament" => "invalid value" }}, valid_session
response.should render_template("new")
end
end
end
describe "PUT update" do
describe "with valid params" do
it "updates the requested match" do
match = Match.create! valid_attributes
# Assuming there are no other matches in the database, this
# specifies that the Match created on the previous line
# receives the :update_attributes message with whatever params are
# submitted in the request.
Match.any_instance.should_receive(:update).with({ "tournament" => "" })
put :update, {:id => match.to_param, :match => { "tournament" => "" }}, valid_session
end
it "assigns the requested match as @match" do
match = Match.create! valid_attributes
put :update, {:id => match.to_param, :match => valid_attributes}, valid_session
assigns(:match).should eq(match)
end
it "redirects to the match" do
match = Match.create! valid_attributes
put :update, {:id => match.to_param, :match => valid_attributes}, valid_session
response.should redirect_to(match)
end
end
describe "with invalid params" do
it "assigns the match as @match" do
match = Match.create! valid_attributes
# Trigger the behavior that occurs when invalid params are submitted
Match.any_instance.stub(:save).and_return(false)
put :update, {:id => match.to_param, :match => { "tournament" => "invalid value" }}, valid_session
assigns(:match).should eq(match)
end
it "re-renders the 'edit' template" do
match = Match.create! valid_attributes
# Trigger the behavior that occurs when invalid params are submitted
Match.any_instance.stub(:save).and_return(false)
put :update, {:id => match.to_param, :match => { "tournament" => "invalid value" }}, valid_session
response.should render_template("edit")
end
end
end
describe "DELETE destroy" do
it "destroys the requested match" do
match = Match.create! valid_attributes
expect {
delete :destroy, {:id => match.to_param}, valid_session
}.to change(Match, :count).by(-1)
end
it "redirects to the matches list" do
match = Match.create! valid_attributes
delete :destroy, {:id => match.to_param}, valid_session
response.should redirect_to(matches_url)
end
end
end
|
