Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.124	19 sie 2021, 06:07

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 102ms

After Hooks.unlockUsers() 137ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 032ms

Hooks

After Hooks.rollbackParameters() 202ms

After Hooks.unlockUsers() 092ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 031ms

Hooks

After Hooks.rollbackParameters() 194ms

After Hooks.unlockUsers() 095ms

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

Tag Report