Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.5	20 Jul 2021, 02:53

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	2m 48s 329ms	Passed

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" 2s 387ms

Then User is successfully logged 004ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Given Click remind password button 059ms

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

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

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

And Extract password from mailgun mail 4s 053ms

And Reset password from link 614ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 092ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

Given Failed login as "neuca-admin" 438ms

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

Given Failed login as "neuca-admin" 460ms

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

Then Login as "neuca-admin" 813ms

Given Failed login as "neuca-admin" 451ms

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

Then Login as "neuca-admin" 809ms

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 095ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Failed login as "sempertrans-admin" 473ms

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

And Failed login as "sempertrans-admin" 483ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 1s 385ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 076ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

When Failed login as "adama-admin" 515ms

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

And Failed login as "adama-admin" 474ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 1s 035ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 074ms

@rollbackRemovedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 589ms

And Login as "bausch-admin" 1s 663ms

And Login as "bausch-admin" on another browser 1s 858ms

And Close second browser 076ms

And Refresh page 2s 126ms

Then Verify user is logged out 038ms

Hooks

After Hooks.rollbackRemovedAuthorities() 567ms

@rollbackRemovedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 089ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "farmacol-admin" 561ms

And Login as "farmacol-admin" 1s 464ms

And Login as "farmacol-admin" on another browser 1s 778ms

And Close second browser 072ms

And Refresh page 2s 129ms

Then Verify user is logged out 032ms

Hooks

After Hooks.rollbackRemovedAuthorities() 579ms

@rollbackRemovedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 096ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "alrec-admin" 508ms

And Login as "alrec-admin" 1s 208ms

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

And Close second browser 076ms

And Refresh page 2s 113ms

Then Verify user is logged out 032ms

Hooks

After Hooks.rollbackRemovedAuthorities() 566ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Login feature	68	0	0	0	0	68	8	0	8	2m 48s 329ms	Passed

Feature Report