Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.66	19 sie 2021, 05:10

	Steps	Scenarios	Features
@rollbackParameters	31	0	0	0	0	31	3	0	3	2m 14s 549ms	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) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 093ms

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

Given Failed login as "neuca-admin" 530ms

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

Given Failed login as "neuca-admin" 506ms

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

Then Login as "neuca-admin" 897ms

Given Failed login as "neuca-admin" 483ms

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

Then Login as "neuca-admin" 863ms

And User is successfully logged 006ms

Hooks

After Hooks.rollbackParameters() 012ms

After Hooks.unlockUsers() 023ms

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

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

When Failed login as "sempertrans-admin" 509ms

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

And Failed login as "sempertrans-admin" 497ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 035ms

After Hooks.unlockUsers() 014ms

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

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

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

When Failed login as "adama-admin" 511ms

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

And Failed login as "adama-admin" 527ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 013ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 013ms

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

Tag Report