Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.135	27 sie 2021, 06:00

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 099ms

After Hooks.unlockUsers() 134ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 194ms

After Hooks.unlockUsers() 088ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 186ms

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

Tag Report