Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.11	24 Jul 2021, 06:06

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	2m 52s 655ms	Passed

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

Then User is successfully logged 004ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

Given Click remind password button 071ms

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

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

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

And Extract password from mailgun mail 3s 781ms

And Reset password from link 664ms

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

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 088ms

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

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

Given Failed login as "neuca-admin" 441ms

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

Given Failed login as "neuca-admin" 479ms

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

Then Login as "neuca-admin" 843ms

Given Failed login as "neuca-admin" 464ms

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

Then Login as "neuca-admin" 814ms

And User is successfully logged 006ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 117ms

@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-sempertrans" 107ms

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 "sempertrans-admin" 468ms

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

And Failed login as "sempertrans-admin" 473ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 093ms

@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-adama" 095ms

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

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

And Failed login as "adama-admin" 446ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 079ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 1s 710ms

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

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

And Close second browser 077ms

And Refresh page 2s 133ms

Then Verify user is logged out 032ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 691ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "farmacol-admin" 1s 629ms

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

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

And Close second browser 072ms

And Refresh page 2s 126ms

Then Verify user is logged out 034ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 663ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "alrec-admin" 1s 615ms

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

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

And Close second browser 071ms

And Refresh page 2s 131ms

Then Verify user is logged out 024ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 652ms

	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 52s 655ms	Passed

Feature Report