Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.109	07 sie 2021, 05:54

	Steps	Scenarios	Features
@rollbackParameters	31	0	0	0	0	31	3	0	3	2m 34s 472ms	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" 246ms

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

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

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

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

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

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

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

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

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 093ms

After Hooks.unlockUsers() 139ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 193ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 024ms

Hooks

After Hooks.rollbackParameters() 197ms

After Hooks.unlockUsers() 086ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackParameters	31	0	0	0	0	31	3	0	3	2m 34s 472ms	Passed

Tag Report