Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.134	26 sie 2021, 07:47

	Steps	Scenarios	Features
@unlockUsers	31	0	0	0	0	31	3	0	3	2m 35s 206ms	Passed

View Feature Login feature

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 104ms

After Hooks.unlockUsers() 134ms

View Feature Login feature

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 216ms

After Hooks.unlockUsers() 090ms

View Feature Login feature

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 189ms

After Hooks.unlockUsers() 088ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@unlockUsers	31	0	0	0	0	31	3	0	3	2m 35s 206ms	Passed

Tag Report