Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.61	16 sie 2021, 05:45

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	2m 17s 305ms	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" 1s 216ms

When Edit user by my account 663ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 1s 286ms

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "piast-admin" 1s 831ms

When Edit user by my account 483ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 888ms

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" 901ms

When Edit user by my account 462ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 664ms

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" 1s 047ms

When Edit user by my account 478ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 940ms

@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" 2s 149ms

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

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

And Get invited user account data "automaty@test.pl" 670ms

When Go to "USERS_TAB" 1s 035ms

When Delete user "automaty@test.pl" 3s 868ms

Then Success alert is displayed 031ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 216ms

@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" 1s 531ms

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

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

And Get invited user account data "automaty@test.pl" 477ms

When Go to "USERS_TAB" 900ms

When Delete user "automaty@test.pl" 3s 503ms

Then Success alert is displayed 035ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 150ms

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" 1s 733ms

When Go to my account details 218ms

Then Verify that user has disabled notification 15s 035ms

@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" 1s 161ms

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

And Get invited user account data "automaty@test.pl" 452ms

When Go to "USERS_TAB" 875ms

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

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

And Save user details 386ms

And Click edit button in user details page 072ms

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

Hooks

After Hooks.deleteUserAfterTest() 078ms

@deleteUserAfterTest

Scenario Outline Check if user has access to the queues

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

And Get invited user account data "automaty@test.pl" 441ms

When Go to "USERS_TAB" 713ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 075ms

@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) 002ms

Steps

Given Login as "super-admin-neuca" 1s 689ms

And Go to my account details 110ms

And Open change password form 201ms

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

And Click save user details 164ms

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

@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" 104ms

And Prepare login page 194ms

And Click remind password button 086ms

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

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

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

And Extract password from mailgun mail 4s 042ms

And Reset password from link 723ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 150ms

	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	2m 17s 305ms	Passed

Feature Report