Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.57	12 sie 2021, 05:48

	Steps	Scenarios	Features
@rollbackParameters	31	0	0	0	0	31	3	0	3	2m 14s 505ms	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" 094ms

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

Given Failed login as "neuca-admin" 466ms

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

Given Failed login as "neuca-admin" 513ms

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

Then Login as "neuca-admin" 886ms

Given Failed login as "neuca-admin" 489ms

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

Then Login as "neuca-admin" 866ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 013ms

After Hooks.unlockUsers() 024ms

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

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

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

When Failed login as "sempertrans-admin" 488ms

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

And Failed login as "sempertrans-admin" 518ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 1s 797ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 036ms

After Hooks.unlockUsers() 012ms

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

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

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

When Failed login as "adama-admin" 515ms

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

And Failed login as "adama-admin" 520ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 1s 702ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 012ms

	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 14s 505ms	Passed

Tag Report