Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.116	13 sie 2021, 02:44

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	3m 54s 382ms	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 683ms

When Edit user by my account 1s 605ms

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

When Edit user by my account 1s 393ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 424ms

And Wait "2" seconds 2s

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

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

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 3s 937ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

When Go to "USERS_TAB" 3s 006ms

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

Then Success alert is displayed 093ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 571ms

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

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

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

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

When Go to "USERS_TAB" 2s 821ms

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

Then Success alert is displayed 088ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 452ms

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

When Go to my account details 490ms

Then Verify that user has disabled notification 15s 058ms

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

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

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

When Go to "USERS_TAB" 2s 883ms

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

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

And Save user details 1s 582ms

And Click edit button in user details page 213ms

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

Hooks

After Hooks.deleteUserAfterTest() 408ms

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

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

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

When Go to "USERS_TAB" 1s 506ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 398ms

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

Steps

Given Login as "super-admin-neuca" 10s 902ms

And Go to my account details 344ms

And Open change password form 494ms

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

And Click save user details 329ms

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

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

And Prepare login page 490ms

And Click remind password button 299ms

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

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

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

And Extract password from mailgun mail 3s 912ms

And Reset password from link 1s 619ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 973ms

	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 54s 382ms	Passed

Feature Report