Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.139	31 sie 2021, 05:52

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 044ms

Hooks

After Hooks.rollbackParameters() 086ms

After Hooks.unlockUsers() 163ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 203ms

After Hooks.unlockUsers() 091ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 189ms

After Hooks.unlockUsers() 090ms

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

Tag Report