Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.157	14 wrz 2021, 06:50

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 9s 594ms	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" 15s 549ms

Then User is successfully logged 027ms

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

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

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

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

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

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

Given Click remind password button 207ms

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

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

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

And Extract password reset link from mailgun mail 4s 075ms

And Reset password from link 1s 339ms

Then Login as "swiss-krono-delivery-admin-2" with new password 5s 180ms

And User is successfully logged 028ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 994ms

After Hooks.clearUserPasswordDataAfterTest() 476ms

After Hooks.rollbackParameters() 097ms

After Hooks.unlockUsers() 148ms

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

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

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

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

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

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

Then Login as "neuca-admin" 2s 250ms

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

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

Then Login as "neuca-admin" 2s 114ms

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 089ms

After Hooks.unlockUsers() 089ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 6s 839ms

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 191ms

After Hooks.unlockUsers() 088ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 200ms

After Hooks.unlockUsers() 088ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "dayco-admin" 250ms

And Login as "dayco-admin" 5s 836ms

And Login as "dayco-admin" on another browser 3s 419ms

And Close second browser 162ms

And Refresh page 2s 231ms

Then Verify user is logged out 091ms

Hooks

After Hooks.rollbackRemovedAuthorities() 250ms

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

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

And Login as "farmacol-admin" 5s 681ms

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

And Close second browser 153ms

And Refresh page 2s 206ms

Then Verify user is logged out 103ms

Hooks

After Hooks.rollbackRemovedAuthorities() 177ms

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

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

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

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

And Close second browser 148ms

And Refresh page 2s 203ms

Then Verify user is logged out 120ms

Hooks

After Hooks.rollbackRemovedAuthorities() 188ms

	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 9s 594ms	Passed

Feature Report