Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.130	24 sie 2021, 05:52

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 092ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 200ms

After Hooks.unlockUsers() 100ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 031ms

Hooks

After Hooks.rollbackParameters() 184ms

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

Tag Report