Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.90	22 lip 2021, 06:11

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 17s 551ms	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" 15s 462ms

Then User is successfully logged 028ms

@rollbackParameters @unlockUsers

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

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

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

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

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

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

Given Click remind password button 163ms

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

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

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

And Extract password from mailgun mail 4s 195ms

And Reset password from link 1s 427ms

Then Login as "swiss-krono-delivery-admin" 5s 484ms

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 015ms

After Hooks.unlockUsers() 132ms

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

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

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

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

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

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

Then Login as "neuca-admin" 1s 944ms

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

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

Then Login as "neuca-admin" 1s 924ms

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 019ms

After Hooks.unlockUsers() 158ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 7s 448ms

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 121ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 142ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 180ms

And Login as "bausch-admin" 7s 967ms

And Login as "bausch-admin" on another browser 3s 660ms

And Close second browser 144ms

And Refresh page 2s 189ms

Then Verify user is logged out 092ms

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

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

And Login as "farmacol-admin" 6s 269ms

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

And Close second browser 151ms

And Refresh page 2s 209ms

Then Verify user is logged out 096ms

Hooks

After Hooks.rollbackRemovedAuthorities() 156ms

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

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

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

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

And Close second browser 157ms

And Refresh page 2s 192ms

Then Verify user is logged out 101ms

Hooks

After Hooks.rollbackRemovedAuthorities() 255ms

	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 17s 551ms	Passed

Feature Report