Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.112	10 sie 2021, 05:53

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

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

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

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

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

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

Then Login as "neuca-admin" 1s 994ms

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 121ms

After Hooks.unlockUsers() 112ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 226ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 190ms

After Hooks.unlockUsers() 091ms

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

Tag Report