Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.140	01 wrz 2021, 05:52

	Steps	Scenarios	Features
@unlockUsers	31	0	0	0	0	31	3	0	3	2m 35s 671ms	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" 242ms

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

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

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

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

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

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

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

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

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 096ms

After Hooks.unlockUsers() 140ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 207ms

After Hooks.unlockUsers() 098ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 212ms

After Hooks.unlockUsers() 090ms

	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 671ms	Passed

Tag Report