Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.132	25 sie 2021, 05:54

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 088ms

After Hooks.unlockUsers() 132ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 182ms

After Hooks.unlockUsers() 091ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 214ms

After Hooks.unlockUsers() 089ms

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

Tag Report