Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.66	19 sie 2021, 05:10

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	2m 17s 934ms	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 188ms

When Edit user by my account 604ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 496ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 447ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 482ms

And Wait "2" seconds 2s

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

@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" 2s 308ms

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

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

When Go to "USERS_TAB" 1s 011ms

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

Then Success alert is displayed 039ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 207ms

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

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

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

When Go to "USERS_TAB" 883ms

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

Then Success alert is displayed 048ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 123ms

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

When Go to my account details 108ms

Then Verify that user has disabled notification 15s 056ms

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

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

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

When Go to "USERS_TAB" 897ms

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

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

And Save user details 378ms

And Click edit button in user details page 064ms

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

Hooks

After Hooks.deleteUserAfterTest() 079ms

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

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

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

When Go to "USERS_TAB" 728ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 081ms

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

And Go to my account details 115ms

And Open change password form 224ms

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

And Click save user details 180ms

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

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

And Prepare login page 202ms

And Click remind password button 088ms

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

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

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

And Extract password from mailgun mail 4s 176ms

And Reset password from link 705ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 156ms

	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 17s 934ms	Passed

Feature Report