Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.116	13 sie 2021, 02:44

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 102ms

After Hooks.unlockUsers() 089ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 197ms

After Hooks.unlockUsers() 103ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 183ms

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

Tag Report