Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.155	12 wrz 2021, 06:40

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	3m 53s 958ms	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 811ms

Then User is successfully logged 024ms

Scenario Outline Verify that password reset cancel login blockade [A-7286]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-skd" 226ms

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

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

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

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

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

Given Click remind password button 220ms

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

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

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

And Extract password reset link from mailgun mail 3s 885ms

And Reset password from link 1s 370ms

Then Login as "swiss-krono-delivery-admin-2" with new password 4s 969ms

And User is successfully logged 028ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 939ms

After Hooks.clearUserPasswordDataAfterTest() 484ms

After Hooks.rollbackParameters() 096ms

After Hooks.unlockUsers() 149ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 035ms

Hooks

After Hooks.rollbackParameters() 100ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 190ms

After Hooks.unlockUsers() 109ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 204ms

After Hooks.unlockUsers() 091ms

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

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

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

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

And Close second browser 156ms

And Refresh page 2s 214ms

Then Verify user is logged out 113ms

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

Steps

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

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

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

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

And Close second browser 155ms

And Refresh page 2s 241ms

Then Verify user is logged out 100ms

Hooks

After Hooks.rollbackRemovedAuthorities() 159ms

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

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

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

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

And Close second browser 147ms

And Refresh page 2s 203ms

Then Verify user is logged out 113ms

Hooks

After Hooks.rollbackRemovedAuthorities() 139ms

	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	3m 53s 958ms	Passed

Feature Report