Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.96	27 lip 2021, 06:03

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 17s 959ms	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" 15s 513ms

Then User is successfully logged 027ms

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

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

Given Failed login as "swiss-krono-delivery-admin" 1s 495ms

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

Given Try login as "swiss-krono-delivery-admin" 1s 476ms

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

Given Click remind password button 190ms

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

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

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

And Extract password from mailgun mail 4s 099ms

And Reset password from link 1s 309ms

Then Login as "swiss-krono-delivery-admin" 5s 485ms

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 015ms

After Hooks.unlockUsers() 145ms

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

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

Given Failed login as "neuca-admin" 1s 229ms

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

Given Failed login as "neuca-admin" 1s 156ms

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

Then Login as "neuca-admin" 1s 977ms

Given Failed login as "neuca-admin" 1s 127ms

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

Then Login as "neuca-admin" 1s 997ms

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 017ms

After Hooks.unlockUsers() 169ms

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

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

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

When Failed login as "sempertrans-admin" 1s 310ms

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

And Failed login as "sempertrans-admin" 1s 171ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 7s 371ms

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 025ms

After Hooks.unlockUsers() 129ms

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

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

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

When Failed login as "adama-admin" 1s 244ms

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

And Failed login as "adama-admin" 1s 242ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 6s 643ms

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 032ms

After Hooks.unlockUsers() 158ms

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

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

And Login as "bausch-admin" 7s 941ms

And Login as "bausch-admin" on another browser 3s 608ms

And Close second browser 158ms

And Refresh page 2s 181ms

Then Verify user is logged out 107ms

Hooks

After Hooks.rollbackRemovedAuthorities() 191ms

@rollbackRemovedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Login as "farmacol-admin" 6s 440ms

And Login as "farmacol-admin" on another browser 3s 389ms

And Close second browser 152ms

And Refresh page 2s 234ms

Then Verify user is logged out 095ms

Hooks

After Hooks.rollbackRemovedAuthorities() 141ms

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

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

And Login as "alrec-admin" 5s 884ms

And Login as "alrec-admin" on another browser 3s 425ms

And Close second browser 148ms

And Refresh page 2s 177ms

Then Verify user is logged out 109ms

Hooks

After Hooks.rollbackRemovedAuthorities() 183ms

	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	4m 17s 959ms	Passed

Feature Report