Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.119	15 sie 2021, 05:58

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	3m 50s 732ms	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" 2s 764ms

When Edit user by my account 1s 700ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 366ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 421ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 373ms

And Wait "2" seconds 2s

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

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

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

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

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

When Go to "USERS_TAB" 2s 989ms

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

Then Success alert is displayed 078ms

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

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

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

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

When Go to "USERS_TAB" 2s 870ms

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

Then Success alert is displayed 084ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 455ms

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

When Go to my account details 392ms

Then Verify that user has disabled notification 15s 031ms

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

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

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

When Go to "USERS_TAB" 2s 895ms

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

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

And Save user details 1s 546ms

And Click edit button in user details page 210ms

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

Hooks

After Hooks.deleteUserAfterTest() 401ms

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

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

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

When Go to "USERS_TAB" 1s 499ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 422ms

@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" 10s 278ms

And Go to my account details 342ms

And Open change password form 498ms

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

And Click save user details 366ms

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

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

And Prepare login page 385ms

And Click remind password button 251ms

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

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

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

And Extract password from mailgun mail 3s 947ms

And Reset password from link 1s 556ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 946ms

	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 50s 732ms	Passed

Feature Report