Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.161	17 wrz 2021, 07:00

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

Then User is successfully logged 028ms

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

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

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

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

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

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

Given Click remind password button 218ms

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

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

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

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

And Reset password from link 1s 496ms

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

And User is successfully logged 082ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 009ms

After Hooks.clearUserPasswordDataAfterTest() 478ms

After Hooks.rollbackParameters() 097ms

After Hooks.unlockUsers() 101ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 044ms

Hooks

After Hooks.rollbackParameters() 104ms

After Hooks.unlockUsers() 096ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 203ms

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) 002ms

Steps

Given Set token of apiUsername "super-admin-adama" 285ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 193ms

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

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

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

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

And Close second browser 150ms

And Refresh page 2s 223ms

Then Verify user is logged out 099ms

Hooks

After Hooks.rollbackRemovedAuthorities() 266ms

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

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

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

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

And Close second browser 147ms

And Refresh page 2s 218ms

Then Verify user is logged out 111ms

Hooks

After Hooks.rollbackRemovedAuthorities() 173ms

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

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

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

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

And Close second browser 152ms

And Refresh page 2s 205ms

Then Verify user is logged out 088ms

Hooks

After Hooks.rollbackRemovedAuthorities() 158ms

	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 548ms	Passed

Feature Report