Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.128	22 sie 2021, 05:16

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 043ms

Hooks

After Hooks.rollbackParameters() 092ms

After Hooks.unlockUsers() 149ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 194ms

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

Steps

Given Set token of apiUsername "super-admin-adama" 227ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 031ms

Hooks

After Hooks.rollbackParameters() 191ms

After Hooks.unlockUsers() 092ms

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

Tag Report