Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.91	23 lip 2021, 04:22

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 18s 487ms	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 423ms

Then User is successfully logged 024ms

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

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

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

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

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

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

Given Click remind password button 151ms

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

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!" 33s 064ms

And Extract password from mailgun mail 4s 607ms

And Reset password from link 1s 450ms

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 013ms

After Hooks.unlockUsers() 157ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 024ms

After Hooks.unlockUsers() 146ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 028ms

After Hooks.unlockUsers() 119ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 034ms

After Hooks.unlockUsers() 137ms

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

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

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

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

And Close second browser 141ms

And Refresh page 2s 191ms

Then Verify user is logged out 100ms

Hooks

After Hooks.rollbackRemovedAuthorities() 145ms

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

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

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

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

And Close second browser 161ms

And Refresh page 2s 203ms

Then Verify user is logged out 111ms

Hooks

After Hooks.rollbackRemovedAuthorities() 140ms

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

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

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

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

And Close second browser 149ms

And Refresh page 2s 195ms

Then Verify user is logged out 100ms

Hooks

After Hooks.rollbackRemovedAuthorities() 237ms

	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 18s 487ms	Passed

Feature Report