IT4Change/gradido
3
0
Fork 0
mirror of https://github.com/IT4Change/gradido.git synced 2025-12-13 07:45:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

use different users for e2e tests

Browse Source
This commit is contained in:
mahula 2023-03-08 14:43:44 +01:00
parent c4083bef86
commit 9a843f3e67
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
e2e-tests/cypress/e2e/User.Authentication.ResetPassword.feature
View File

@ -5,13 +5,13 @@ Feature: User Authentication - reset password
# TODO for these pre-conditions utilize seeding or API check, if user exists in test system # TODO for these pre-conditions utilize seeding or API check, if user exists in test system
# Background: # Background:
# Given the following "users" are in the database: # Given the following "users" are in the database:
# | email | password | name | # | email | password | name |
# | bibi@bloxberg.de | Aa12345_ | Bibi Bloxberg | # | raeuber@hotzenplotz.de | Aa12345_ | Räuber Hotzenplotz |
Scenario: Reset password from signin page successfully Scenario: Reset password from signin page successfully
Given the user navigates to page "/login" Given the user navigates to page "/login"
And the user navigates to the forgot password page And the user navigates to the forgot password page
When the user enters the e-mail address "bibi@bloxberg.de" When the user enters the e-mail address "raeuber@hotzenplotz.de"
And the user submits the e-mail form And the user submits the e-mail form
Then the user receives an e-mail containing the "password reset" link Then the user receives an e-mail containing the "password reset" link
When the user opens the "password reset" link in the browser When the user opens the "password reset" link in the browser
@ -19,7 +19,7 @@ Feature: User Authentication - reset password
And the user repeats the password "12345Aa_" And the user repeats the password "12345Aa_"
And the user submits the password form And the user submits the password form
And the user clicks the sign in button And the user clicks the sign in button
Then the user submits the credentials "bibi@bloxberg.de" "Aa12345_" Then the user submits the credentials "raeuber@hotzenplotz.de" "Aa12345_"
And the user cannot login And the user cannot login
But the user submits the credentials "bibi@bloxberg.de" "12345Aa_" But the user submits the credentials "raeuber@hotzenplotz.de" "12345Aa_"
And the user is logged in with username "Bibi Bloxberg" And the user is logged in with username "Räuber Hotzenplotz"

12
e2e-tests/cypress/e2e/UserProfile.ChangePassword.feature
View File

@ -5,11 +5,11 @@ Feature: User profile - change password
Background: Background:
# TODO for these pre-conditions utilize seeding or API check, if user exists in test system # TODO for these pre-conditions utilize seeding or API check, if user exists in test system
# Given the following "users" are in the database: # Given the following "users" are in the database:
# | email | password | name | # | email | password | name |
# | bibi@bloxberg.de | Aa12345_ | Bibi Bloxberg | | # | bob@baumeister.de | Aa12345_ | Bob der Baumeister |
# TODO instead of credentials use the name of an user object (see seeds in backend) # TODO instead of credentials use the name of an user object (see seeds in backend)
Given the user is logged in as "bibi@bloxberg.de" "Aa12345_" Given the user is logged in as "bob@baumeister.de" "Aa12345_"
Scenario: Change password successfully Scenario: Change password successfully
Given the user navigates to page "/settings" Given the user navigates to page "/settings"
@ -21,7 +21,7 @@ Feature: User profile - change password
And the user submits the password form And the user submits the password form
And the user is presented a "success" message And the user is presented a "success" message
And the user logs out And the user logs out
Then the user submits the credentials "bibi@bloxberg.de" "Aa12345_" Then the user submits the credentials "bob@baumeister.de" "Aa12345_"
And the user cannot login And the user cannot login
But the user submits the credentials "bibi@bloxberg.de" "12345Aa_" But the user submits the credentials "bob@baumeister.de" "12345Aa_"
And the user is logged in with username "Bibi Bloxberg" And the user is logged in with username "Bob der Baumeister"