Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.64	17 sie 2021, 05:48

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	1m 51s 332ms	Passed

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

When Edit user by my account 605ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 473ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 482ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 455ms

And Wait "2" seconds 2s

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

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

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

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

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

When Go to "USERS_TAB" 969ms

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

Then Success alert is displayed 035ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 219ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-lantmannen" and set token of apiUsername "super-admin-lantmannen" 1s 515ms

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

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

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

When Go to "USERS_TAB" 946ms

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

Then Success alert is displayed 038ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 133ms

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

When Go to my account details 117ms

Then Verify that user has disabled notification 15s 053ms

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

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

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

When Go to "USERS_TAB" 940ms

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

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

And Save user details 371ms

And Click edit button in user details page 065ms

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

Hooks

After Hooks.deleteUserAfterTest() 080ms

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

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

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

When Go to "USERS_TAB" 744ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 083ms

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

And Go to my account details 106ms

And Open change password form 217ms

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

And Click save user details 165ms

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

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

And Prepare login page 228ms

And Click remind password button 087ms

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

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

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

And Extract password from mailgun mail 4s 349ms

And Reset password from link 727ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 139ms

	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	1m 51s 332ms	Passed

Feature Report