|
39 | 39 | group: Dashboard
|
40 | 40 | description: Verify that Access Control page works properly
|
41 | 41 | steps: |
|
42 |
| - - Change permissions |
43 |
| - - Review permissions on GitHub |
| 42 | + 1. Check push to remote is not possible, if no write permissions were granted |
| 43 | + 1. Check push to remote is possible, if write permissions were granted |
44 | 44 | mustpass: true
|
45 | 45 | mintestercount: 1
|
46 | 46 | annotations: {}
|
@@ -294,13 +294,86 @@ case:
|
294 | 294 | mintestercount: 1
|
295 | 295 | annotations: {}
|
296 | 296 | - id: logout-and-login
|
| 297 | + group: Dashboard |
| 298 | + mustpass: true |
| 299 | + mintestercount: 1 |
| 300 | + annotations: {} |
| 301 | + description: "" |
297 | 302 | name: Log out and log in again
|
| 303 | + steps: | |
| 304 | + 1. On logout, you should be redirected to the empty dashboard (or whatever is configured at that time) |
| 305 | + 2. Next, on login noo ToS page should be shown (unless there was a update in the meantime) |
| 306 | +- id: login-with-second-provider |
| 307 | + group: Dashboard |
| 308 | + mustpass: true |
| 309 | + mintestercount: 1 |
| 310 | + annotations: {} |
| 311 | + description: "" |
| 312 | + name: Login with second privider |
| 313 | + steps: | |
| 314 | + 1. First of, log out. |
| 315 | + 2. Try to log in with a different provider; |
| 316 | + - If the provider was already connected, you get logged in into the account. |
| 317 | + BEFORE proceeding with the following steps, go to Access Control and disconnect that provider. |
| 318 | + - (ALTERNATIVE 1) If the primary email address is matching your existing account (and first provider,) you should be able to log in into the first account. |
| 319 | + Verify in Access Control, that you have both providers connected. |
| 320 | + - (ALTERNATIVE 2) If the primary email address is NOT matching, you are about to create a new account. |
| 321 | + Verify in Access Control, that you have connected just a single provider. |
| 322 | +- id: connect-with-second-provider |
298 | 323 | group: Dashboard
|
| 324 | + mustpass: true |
| 325 | + mintestercount: 1 |
| 326 | + annotations: {} |
299 | 327 | description: ""
|
300 |
| - steps: "" |
| 328 | + name: Connect with second provider |
| 329 | + steps: | |
| 330 | + 1. First of, ensure you are logged in, and in Access Control only one provider is connected. |
| 331 | + 2. Connect to a second provider. |
| 332 | +- id: connect-with-provider-already-connected |
| 333 | + group: Dashboard |
| 334 | + mustpass: true |
| 335 | + mintestercount: 1 |
| 336 | + annotations: {} |
| 337 | + description: "" |
| 338 | + name: Connect with a provider which is already connected |
| 339 | + steps: | |
| 340 | + 1. First of, ensure you have two accounts with distict provider connections, e.g. one with GitHub and one with GitLab. |
| 341 | + 2. Log in with user A. |
| 342 | + 3. Go to Access Controll, try to connect with second provider (which is connected to user B) |
| 343 | + 4. See the Select Account page explaining the current situation. Verify the shown information. |
| 344 | + 5. Select the `Switch Account` action, and notice that you're logged into the other account. |
| 345 | + 6. Go to Access Controll, try to connect with second provider (which is connected to user A) |
| 346 | + 7. Disconnect a provider in one account (or delete one account) to proceed with connecting in the other account. |
| 347 | +- id: disconnect-providers |
| 348 | + group: Dashboard |
301 | 349 | mustpass: true
|
302 | 350 | mintestercount: 1
|
303 | 351 | annotations: {}
|
| 352 | + description: "" |
| 353 | + name: Disconnect second provider |
| 354 | + steps: | |
| 355 | + 1. First of, ensure you are logged in, and in Access Control two providers are connected. |
| 356 | + 2. Disconnect one provider. Verify, a single provider is left connected. |
| 357 | + 3. Try to disconnect the single provider, notice the message tells you to delete account in Settings. |
| 358 | +- id: tos-update |
| 359 | + group: Dashboard |
| 360 | + mustpass: true |
| 361 | + mintestercount: 1 |
| 362 | + annotations: {} |
| 363 | + description: "" |
| 364 | + name: ToS Update |
| 365 | + steps: | |
| 366 | + 1. First of, ensure you are logged in, and terms were already accepted. |
| 367 | + 2. Start a workspace. Keep running in background. (cf. 4.) |
| 368 | + 3. Connect to DB, and run `update d_b_user_acceptance_entry set termsRevision='' where userId='YOUR_ID'` |
| 369 | + 4. Verify the running workspace was not impacted. |
| 370 | + 5. Verify, you can load the workspaces list. (/workspaces) |
| 371 | + 6. Verify, you can load Settings page. |
| 372 | + 7. Verify, you see /tos page with the update message when trying to create/start a workspace. Once accepted, workspace start should be resumed. |
| 373 | + 8. (repeat 3.) |
| 374 | + 9. Log out. |
| 375 | + 10. Verify, you see the /tos page with the update on login. |
| 376 | + 11. Verify, you get logged out if you decline. |
304 | 377 | - id: open-branch
|
305 | 378 | name: Open a GitHub branch
|
306 | 379 | group: IDE
|
|
0 commit comments