forked from flashingpumpkin/django-socialregistration
-
Notifications
You must be signed in to change notification settings - Fork 6
/
Test Procedures.taskpaper
212 lines (204 loc) · 9.9 KB
/
Test Procedures.taskpaper
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
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
Manual Testing:
No custom object defined:
Don't pass in a socialregistration_connect_object in the context. This will link the credentials to a user instead of another object.
setting SOCIALREGISTRATION_GENERATE_USERNAME True:
"userconnect_generate_username"
Facebook:
- Remove the site from the "allowed apps" list at Facebook, attempt to reconnect and decline. You should be sent back and get a message telling you you need to allow before it will work
- Connect a user to an existing account (through login) is not possible if socialregistration generates their username / account - no testing needed
- Create a new account
- Ensure user is not logged in
- Connect a new Facebook account
- Ensure a user was created
- Ensure that user had a password assigned
- Ensure logins are repeatable with that account
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Connect a user to an existing account (already logged in)
- Log in as the existing user via password
- Connect a new Facebook account
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
Twitter:
- Remove the site from the "allowed apps" list at Twitter, attempt to reconnect and decline. You should be sent back and get a message telling you you need to allow before it will work
- Connect a user to an existing account (through login) is not possible if socialregistration generates their username / account - no testing needed
- Create a new account
- Ensure user is not logged in
- Connect a new Twitter account
- Ensure a user was created
- Ensure that user had a password assigned
- Ensure logins are repeatable with that account
- Twitter Profile should have their twitter username stored
- If the app is configured for read/write, oauth keys should be set in the Twitter Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Connect a user to an existing account (already logged in)
- Log in as the existing user via password
- Connect a new Twitter account
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- If the app is configured for read/write, oauth keys should be set in the Twitter Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
OpenID:
- Connect a user to an existing account (through login) is not possible if socialregistration generates their username / account - no testing needed
- Create a new account
- Ensure user is not logged in
- Connect a new OpenID account
- Ensure a user was created
- Ensure that user had a password assigned
- Ensure logins are repeatable with that account
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Connect a user to an existing account (already logged in)
- Log in as the existing user via password
- Connect a new OpenID account
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
setting SOCIALREGISTRATION_GENERATE_USERNAME False:
"userconnect_manual_username"
Facebook:
- Connect a user to an existing account (through login)
- Ensure user is not logged in
- Connect a new Facebook account
- Log in as the existing user via password
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Create a new account
- Ensure user is not logged in
- Connect a new Facebook account
- Ensure a user was created
- Ensure that user had a password assigned
- Ensure logins are repeatable with that account
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Connect a user to an existing account (already logged in)
- Ensure user is logged in
- Connect a new Facebook account
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
Twitter:
- Connect a user to an existing account (through login)
- Ensure user is not logged in
- Connect a new Twitter account
- Log in as the existing user via password
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- Twitter Profile should have their twitter username stored
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Create a new account
- Ensure user is not logged in
- Connect a new Facebook account
- Ensure a user was created
- Ensure that user had a password assigned
- Ensure logins are repeatable with that account
- Twitter Profile should have their twitter username stored
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Connect a user to an existing account (already logged in)
- Ensure user is logged in
- Connect a new Facebook account
- Log in as the existing user via password
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- Twitter Profile should have their twitter username stored
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
OpenID:
- Connect a user to an existing account (through login)
- Ensure user is not logged in
- Connect a new OpenID account
- Log in as the existing user via password
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Create a new account
- Ensure user is not logged in
- Connect a new OpenID account
- Ensure a user was created
- Ensure that user had a password assigned
- Ensure logins are repeatable with that account
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
- Connect a user to an existing account (already logged in)
- Log in as the existing user via password
- Connect a new OpenID account
- Ensure the current user was used
- Ensure that user's password was not overwritten
- Ensure logins are repeatable with that account
- Does the disconnection view work properly?
- Removes profile
- Sends you somewhere useful
Custom object defined:
"objectconnect"
Pass in a socialregistration_connect_object in the context. This will link the credentials to a that object instead of a user.
Facebook:
- Connect to an object
- Connect a new Facebook account
- Ensure the correct object was connected
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Connect to another object
- Connect the same Facebook account to another object
- Ensure the correct object was connected and that the existing connection was preserved
- If the app is configured for read/write, oauth keys should be set in the Facebook Profile
- Does the disconnection view work properly?
- Removes profile (for just the object requested, leaves other alone)
- Sends you somewhere useful
- Then removes profile for the other object - still correct?
- Sends you somewhere useful
Twitter:
- Connect to an object
- Connect a new Twitter account
- Ensure the correct object was connected
- Twitter Profile should have their twitter username stored
- If the app is configured for read/write, oauth keys should be set in the Twitter Profile
- Connect to another object
- Connect the same Twitter account to another object
- Ensure the correct object was connected and that the existing connection was preserved
- Twitter Profile should have their twitter username stored
- If the app is configured for read/write, oauth keys should be set in the Twitter Profile
- Does the disconnection view work properly?
- Removes profile (for just the object requested, leaves other alone)
- Sends you somewhere useful
- Then removes profile for the other object - still correct?
- Sends you somewhere useful