Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.111	09 sie 2021, 05:45

	Steps	Scenarios	Features
@rollbackParameters	31	0	0	0	0	31	3	0	3	2m 34s 981ms	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" 110ms

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

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

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

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

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

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

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

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

And User is successfully logged 039ms

Hooks

After Hooks.rollbackParameters() 087ms

After Hooks.unlockUsers() 149ms

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) 000ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 241ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 190ms

After Hooks.unlockUsers() 075ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 190ms

After Hooks.unlockUsers() 086ms

	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 34s 981ms	Passed

Tag Report