Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.114	12 sie 2021, 06:02

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	3m 51s 144ms	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 737ms

When Edit user by my account 1s 652ms

And Wait "2" seconds 2s

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

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 "piast-admin" 7s 059ms

When Edit user by my account 1s 422ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 396ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 379ms

And Wait "2" seconds 2s

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

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

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

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

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

When Go to "USERS_TAB" 2s 987ms

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

Then Success alert is displayed 083ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 593ms

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

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

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

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

When Go to "USERS_TAB" 2s 824ms

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

Then Success alert is displayed 083ms

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

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" 4s 975ms

When Go to my account details 412ms

Then Verify that user has disabled notification 15s 044ms

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

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

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

When Go to "USERS_TAB" 2s 903ms

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

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

And Save user details 1s 472ms

And Click edit button in user details page 185ms

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

Hooks

After Hooks.deleteUserAfterTest() 405ms

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

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

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

When Go to "USERS_TAB" 1s 632ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 409ms

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

And Go to my account details 310ms

And Open change password form 466ms

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

And Click save user details 364ms

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

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

Steps

Given Set token of apiUsername "super-admin-skd" 229ms

And Prepare login page 463ms

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

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

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

And Extract password from mailgun mail 4s 259ms

And Reset password from link 1s 620ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 934ms

	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 51s 144ms	Passed

Feature Report