Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.12	25 Jul 2021, 06:02

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	2m 59s 809ms	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 445ms

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

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

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

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

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

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

Given Click remind password button 059ms

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

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

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

And Extract password from mailgun mail 4s 111ms

And Reset password from link 714ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 092ms

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

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

Given Failed login as "neuca-admin" 426ms

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

Given Failed login as "neuca-admin" 443ms

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

Then Login as "neuca-admin" 825ms

Given Failed login as "neuca-admin" 470ms

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

Then Login as "neuca-admin" 802ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 085ms

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

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

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

When Failed login as "sempertrans-admin" 443ms

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

And Failed login as "sempertrans-admin" 458ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 006ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 094ms

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

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

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

And Failed login as "adama-admin" 431ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 077ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 2s 021ms

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

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

And Close second browser 100ms

And Refresh page 2s 123ms

Then Verify user is logged out 029ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 972ms

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

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

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

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

And Close second browser 072ms

And Refresh page 2s 113ms

Then Verify user is logged out 022ms

Hooks

After Hooks.rollbackRemovedAuthorities() 1s 951ms

@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-alrec" 107ms

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

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

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

And Close second browser 072ms

And Refresh page 2s 120ms

Then Verify user is logged out 020ms

Hooks

After Hooks.rollbackRemovedAuthorities() 2s 009ms

	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	2m 59s 809ms	Passed

Feature Report