Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.142	02 wrz 2021, 20:16

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 042ms

Hooks

After Hooks.rollbackParameters() 088ms

After Hooks.unlockUsers() 163ms

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

Steps

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 186ms

After Hooks.unlockUsers() 086ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 309ms

After Hooks.unlockUsers() 090ms

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

Tag Report