Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.52	07 sie 2021, 05:34

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

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

Given Failed login as "neuca-admin" 486ms

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

Given Failed login as "neuca-admin" 487ms

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

Then Login as "neuca-admin" 849ms

Given Failed login as "neuca-admin" 507ms

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

Then Login as "neuca-admin" 843ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 017ms

After Hooks.unlockUsers() 022ms

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) 000ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 095ms

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

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

When Failed login as "sempertrans-admin" 484ms

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

And Failed login as "sempertrans-admin" 498ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 006ms

Hooks

After Hooks.rollbackParameters() 033ms

After Hooks.unlockUsers() 013ms

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) 000ms

Steps

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

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

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

When Failed login as "adama-admin" 475ms

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

And Failed login as "adama-admin" 488ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 034ms

After Hooks.unlockUsers() 016ms

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

Tag Report