Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.147	06 wrz 2021, 06:13

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 126ms

After Hooks.unlockUsers() 147ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 190ms

After Hooks.unlockUsers() 097ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 5s 993ms

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 196ms

After Hooks.unlockUsers() 083ms

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

Tag Report