Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.127	21 sie 2021, 05:25

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 108ms

After Hooks.unlockUsers() 151ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 185ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 197ms

After Hooks.unlockUsers() 097ms

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

Tag Report