Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.123	18 sie 2021, 06:09

	Steps	Scenarios	Features
User	65	0	0	0	0	65	11	0	11	3m 50s 091ms	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 676ms

When Edit user by my account 1s 671ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 461ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 355ms

And Wait "2" seconds 2s

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

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

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

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

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

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

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

When Go to "USERS_TAB" 3s 007ms

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

Then Success alert is displayed 087ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 590ms

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

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

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

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

When Go to "USERS_TAB" 2s 818ms

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

Then Success alert is displayed 078ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 468ms

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" 5s 102ms

When Go to my account details 391ms

Then Verify that user has disabled notification 15s 070ms

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

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

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

When Go to "USERS_TAB" 2s 900ms

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

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

And Save user details 1s 526ms

And Click edit button in user details page 168ms

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

Hooks

After Hooks.deleteUserAfterTest() 411ms

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

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

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

When Go to "USERS_TAB" 1s 557ms

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

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

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) 001ms

Steps

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

And Go to my account details 300ms

And Open change password form 477ms

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

And Click save user details 383ms

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

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

And Prepare login page 443ms

And Click remind password button 276ms

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

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

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

And Extract password from mailgun mail 3s 903ms

And Reset password from link 1s 481ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 968ms

	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 50s 091ms	Passed

Feature Report