Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.137	29 sie 2021, 05:53

	Steps	Scenarios	Features
@rollbackParameters	31	0	0	0	0	31	3	0	3	2m 35s 540ms	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" 258ms

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

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

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

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

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

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

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

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

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 093ms

After Hooks.unlockUsers() 151ms

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) 000ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 222ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 204ms

After Hooks.unlockUsers() 094ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 191ms

After Hooks.unlockUsers() 088ms

	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 35s 540ms	Passed

Tag Report