Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.162	18 wrz 2021, 06:45

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 15s 560ms	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 533ms

Then User is successfully logged 029ms

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

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

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

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

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

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

Given Click remind password button 259ms

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

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!" 32s 416ms

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

And Reset password from link 1s 335ms

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

And User is successfully logged 029ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 006ms

After Hooks.clearUserPasswordDataAfterTest() 490ms

After Hooks.rollbackParameters() 095ms

After Hooks.unlockUsers() 104ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 089ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 195ms

After Hooks.unlockUsers() 087ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 181ms

After Hooks.unlockUsers() 094ms

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

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

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

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

And Close second browser 150ms

And Refresh page 2s 203ms

Then Verify user is logged out 105ms

Hooks

After Hooks.rollbackRemovedAuthorities() 227ms

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

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

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

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

And Close second browser 148ms

And Refresh page 2s 209ms

Then Verify user is logged out 100ms

Hooks

After Hooks.rollbackRemovedAuthorities() 187ms

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

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

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

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

And Close second browser 165ms

And Refresh page 2s 203ms

Then Verify user is logged out 113ms

Hooks

After Hooks.rollbackRemovedAuthorities() 169ms

	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 15s 560ms	Passed

Feature Report