Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.59	14 sie 2021, 05:45

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	2m 18s 391ms	Passed

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 "swisskrono-admin" 1s 401ms

When Edit user by my account 641ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 494ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 465ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 477ms

And Wait "2" seconds 2s

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

@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 207ms

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

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

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

When Go to "USERS_TAB" 980ms

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

Then Success alert is displayed 034ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 180ms

@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 527ms

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

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

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

When Go to "USERS_TAB" 954ms

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

Then Success alert is displayed 037ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 129ms

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 598ms

When Go to my account details 123ms

Then Verify that user has disabled notification 15s 034ms

@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 122ms

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

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

When Go to "USERS_TAB" 926ms

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

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

And Save user details 376ms

And Click edit button in user details page 069ms

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

Hooks

After Hooks.deleteUserAfterTest() 087ms

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

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

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

When Go to "USERS_TAB" 689ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 090ms

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

And Go to my account details 116ms

And Open change password form 205ms

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

And Click save user details 174ms

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

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

And Prepare login page 198ms

And Click remind password button 089ms

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

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

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

And Extract password from mailgun mail 4s 123ms

And Reset password from link 688ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 170ms

	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 18s 391ms	Passed

Feature Report