Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	develop.347	15 cze 2021, 22:44

	Steps	Scenarios	Features
Login feature	62	0	0	0	0	62	8	0	8	3m 37s 327ms	Passed

Scenario Outline Verify that user is able to login using valid login and password

Steps

Given Login as "hochland-admin" 3s 112ms

Then User is successfully logged 004ms

@rollbackParameters @unlockUsers

Scenario Outline Verify that password reset cancel login blockade [A-7286]

Steps

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

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 002ms

Given Failed login as "swiss-krono-delivery-admin" 510ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 286ms

Given Try login as "swiss-krono-delivery-admin" 651ms

Then Verify that login error reason is "auth.accountLocked" 105ms

Given Click remind password button 068ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Restart hasła! | Password reset!" 55s 511ms

And Extract password from mail 001ms

And Reset password from link 460ms

Then Login as "swiss-krono-delivery-admin" 1s 364ms

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 086ms

@rollbackParameters @unlockUsers

Scenario Outline Checking if setting for blocking the user after X failed attempts works correctly [A-7287]

Steps

Given Set token of apiUsername "super-admin-neuca" 100ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "3" 002ms

Given Failed login as "neuca-admin" 490ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 220ms

Given Failed login as "neuca-admin" 604ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 218ms

Then Login as "neuca-admin" 954ms

Given Failed login as "neuca-admin" 462ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 217ms

Then Login as "neuca-admin" 981ms

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 093ms

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Steps

Given Set token of apiUsername "super-admin-sempertrans" 101ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 001ms

And Prepare parameter "BLOCKED_USER_DURATION_IN_MINUTES" with value: "1" 001ms

When Failed login as "sempertrans-admin" 563ms

And Verify that login error reason is "auth.invalidLoginOrPassword" 288ms

And Failed login as "sempertrans-admin" 688ms

And Verify that login error reason is "auth.accountLocked" 104ms

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 2s 407ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 157ms

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Steps

Given Set token of apiUsername "super-admin-adama" 175ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 001ms

And Prepare parameter "BLOCKED_USER_DURATION_IN_MINUTES" with value: "1" 001ms

When Failed login as "adama-admin" 482ms

And Verify that login error reason is "auth.invalidLoginOrPassword" 277ms

And Failed login as "adama-admin" 803ms

And Verify that login error reason is "auth.accountLocked" 107ms

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 2s 139ms

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 078ms

Scenario Outline Check if user is logged out when another person login on same account

Steps

Given Login as "bausch-admin" 2s 205ms

And Login as "bausch-admin" on another browser 2s 256ms

And Close second browser 075ms

And Refresh page 2s 080ms

Then Verify user is logged out 061ms

Scenario Outline Check if user is logged out when another person login on same account

Steps

Given Login as "farmacol-admin" 1s 150ms

And Login as "farmacol-admin" on another browser 2s 405ms

And Close second browser 070ms

And Refresh page 2s 117ms

Then Verify user is logged out 023ms

Scenario Outline Check if user is logged out when another person login on same account

Steps

Given Login as "alrec-admin" 1s 723ms

And Login as "alrec-admin" on another browser 1s 976ms

And Close second browser 068ms

And Refresh page 2s 144ms

Then Verify user is logged out 022ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Login feature	62	0	0	0	0	62	8	0	8	3m 37s 327ms	Passed

Feature Report