Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.146	05 wrz 2021, 06:14

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 092ms

After Hooks.unlockUsers() 137ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 6s 943ms

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 202ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 193ms

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

Tag Report