Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.14	26 Jul 2021, 08:50

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	3m 20s 426ms	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" 2s 401ms

Then User is successfully logged 004ms

@rollbackParameters @unlockUsers

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

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

Given Failed login as "swiss-krono-delivery-admin" 487ms

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

Given Try login as "swiss-krono-delivery-admin" 522ms

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

Given Click remind password button 070ms

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

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

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

And Extract password from mailgun mail 4s 185ms

And Reset password from link 694ms

Then Login as "swiss-krono-delivery-admin" 1s 357ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 095ms

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

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

Given Failed login as "neuca-admin" 464ms

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

Given Failed login as "neuca-admin" 479ms

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

Then Login as "neuca-admin" 826ms

Given Failed login as "neuca-admin" 463ms

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

Then Login as "neuca-admin" 804ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

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

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

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

When Failed login as "sempertrans-admin" 496ms

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

And Failed login as "sempertrans-admin" 487ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 1s 452ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 083ms

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

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

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

When Failed login as "adama-admin" 470ms

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

And Failed login as "adama-admin" 482ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 1s 016ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 078ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 1s 854ms

And Login as "bausch-admin" 1s 630ms

And Login as "bausch-admin" on another browser 1s 844ms

And Close second browser 076ms

And Refresh page 2s 110ms

Then Verify user is logged out 035ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 858ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "farmacol-admin" 1s 829ms

And Login as "farmacol-admin" 1s 631ms

And Login as "farmacol-admin" on another browser 1s 717ms

And Close second browser 072ms

And Refresh page 2s 113ms

Then Verify user is logged out 030ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 827ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "alrec-admin" 1s 815ms

And Login as "alrec-admin" 1s 253ms

And Login as "alrec-admin" on another browser 1s 765ms

And Close second browser 074ms

And Refresh page 2s 114ms

Then Verify user is logged out 034ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 850ms

	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 20s 426ms	Passed

Feature Report