Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.89	21 lip 2021, 06:06

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 21s 704ms	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 178ms

Then User is successfully logged 028ms

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

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

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

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

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

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

Given Click remind password button 152ms

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

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

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

And Extract password from mailgun mail 4s 214ms

And Reset password from link 1s 279ms

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 014ms

After Hooks.unlockUsers() 161ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 011ms

After Hooks.unlockUsers() 127ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 120ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 030ms

After Hooks.unlockUsers() 143ms

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

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

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

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

And Close second browser 150ms

And Refresh page 2s 170ms

Then Verify user is logged out 107ms

Hooks

After Hooks.rollbackRemovedAuthorities() 143ms

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

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

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

And Close second browser 149ms

And Refresh page 2s 199ms

Then Verify user is logged out 079ms

Hooks

After Hooks.rollbackRemovedAuthorities() 137ms

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

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

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

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

And Close second browser 148ms

And Refresh page 2s 192ms

Then Verify user is logged out 109ms

Hooks

After Hooks.rollbackRemovedAuthorities() 173ms

	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 21s 704ms	Passed

Feature Report