Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.113	11 sie 2021, 05:52

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	3m 51s 192ms	Passed

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 009ms

Steps

Given Login as "swisskrono-admin" 2s 729ms

When Edit user by my account 1s 671ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 6s 069ms

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" 7s 062ms

When Edit user by my account 1s 434ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 3s 737ms

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" 2s 253ms

When Edit user by my account 1s 438ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 2s 982ms

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" 2s 340ms

When Edit user by my account 1s 449ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 3s 918ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 9s 612ms

And Delete invitations with email "automaty@test.pl" 105ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_CARRIER_INVITATION" 5s 959ms

And Get invited user account data "automaty@test.pl" 4s 201ms

When Go to "USERS_TAB" 3s 055ms

When Delete user "automaty@test.pl" 5s 299ms

Then Success alert is displayed 093ms

And User not displayed in users list "automaty@test.pl" 16s 440ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 576ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-lantmannen" and set token of apiUsername "super-admin-lantmannen" 5s 508ms

And Delete invitations with email "automaty@test.pl" 097ms

And Create and accept invitation by JSON file as "super-admin-lantmannen" for "automaty@test.pl" "CREATE_CARRIER_INVITATION" 4s 234ms

And Get invited user account data "automaty@test.pl" 2s 415ms

When Go to "USERS_TAB" 2s 781ms

When Delete user "automaty@test.pl" 4s 689ms

Then Success alert is displayed 069ms

And User not displayed in users list "automaty@test.pl" 16s 431ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 462ms

Scenario Outline Check if the carrier has disabled the edition of the notifications

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pla1-carrier" and set token of apiUsername "super-admin-skz" 5s 088ms

When Go to my account details 410ms

Then Verify that user has disabled notification 15s 042ms

@deleteUserAfterTest

Scenario Outline Check if it possible to add queues to user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 517ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SQUARE_MANAGER_INVITATION" 3s 618ms

And Get invited user account data "automaty@test.pl" 2s 791ms

When Go to "USERS_TAB" 2s 932ms

And Find user "automaty@test.pl" 2s 756ms

And Add queues to user account "opał" 601ms

And Save user details 1s 560ms

And Click edit button in user details page 167ms

Then Verify that the user is assigned the appropriate queues "opał" 241ms

Hooks

After Hooks.deleteUserAfterTest() 389ms

@deleteUserAfterTest

Scenario Outline Check if user has access to the queues

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 589ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SORTER_INVITATION" 3s 464ms

And Get invited user account data "automaty@test.pl" 2s 698ms

When Go to "USERS_TAB" 1s 523ms

And Find user "automaty@test.pl" 2s 758ms

Then Verify that the user is assigned the appropriate queues "igla. okrągłe HDS;trociny" 418ms

Hooks

After Hooks.deleteUserAfterTest() 400ms

@TmsLink=A-8005

Scenario Outline Check if it is not possible to use the previous password when editing it - my account details [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-neuca" 9s 998ms

And Go to my account details 333ms

And Open change password form 459ms

When Fill change user password form in my account settings with "NqsB63f7Oq" 801ms

And Click save user details 370ms

Then Check if alert is displayed "Nowe hasło musi być różne od wcześniej wprowadzonego hasła." 680ms

@cleanUserDetailsAfterTest @TmsLink=A-8005.1

Scenario Outline Check if it is not possible to use the previous password when editing it - remind password [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 239ms

And Prepare login page 381ms

And Click remind password button 281ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 019ms

And Send remind password form with email "apolloautomattest@gmail.com" 574ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 32s 903ms

And Extract password from mailgun mail 4s 056ms

And Reset password from link 1s 597ms

Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 227ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 960ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
User	65	0	0	0	0	65	11	0	11	3m 51s 192ms	Passed

Feature Report