Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.120	16 sie 2021, 06:00

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	3m 52s 066ms	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 762ms

When Edit user by my account 1s 631ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 454ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 420ms

And Wait "2" seconds 2s

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

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 "keeeper-admin" 2s 398ms

When Edit user by my account 1s 462ms

And Wait "2" seconds 2s

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

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

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

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

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

When Go to "USERS_TAB" 3s 041ms

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

Then Success alert is displayed 090ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 601ms

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

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

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

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

When Go to "USERS_TAB" 2s 823ms

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

Then Success alert is displayed 088ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 458ms

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" 6s 556ms

When Go to my account details 502ms

Then Verify that user has disabled notification 15s 037ms

@deleteUserAfterTest

Scenario Outline Check if it possible to add queues to user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

When Go to "USERS_TAB" 2s 861ms

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

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

And Save user details 1s 586ms

And Click edit button in user details page 204ms

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

Hooks

After Hooks.deleteUserAfterTest() 413ms

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

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

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

When Go to "USERS_TAB" 1s 464ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 452ms

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

And Go to my account details 328ms

And Open change password form 506ms

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

And Click save user details 354ms

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

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

And Prepare login page 444ms

And Click remind password button 267ms

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

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

And Extract password from mailgun mail 4s 408ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 952ms

	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 52s 066ms	Passed

Feature Report