Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.65	02 lip 2021, 06:45

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	3m 18s 706ms	Passed

View Feature Login feature

@rollbackParameters @unlockUsers

Scenario Outline Verify that password reset cancel login blockade [A-7286]

Steps

Given Set token of apiUsername "super-admin-skd" 259ms

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

Given Failed login as "swiss-krono-delivery-admin" 1s 347ms

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

Given Try login as "swiss-krono-delivery-admin" 1s 436ms

Then Verify that login error reason is "auth.accountLocked" 312ms

Given Click remind password button 172ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 118ms

And Send remind password form with email "apolloautomattest@gmail.com" 543ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Restart hasła! | Password reset!" 32s 121ms

And Extract password from mail 001ms

And Reset password from link 1s 053ms

Then Login as "swiss-krono-delivery-admin" 5s 463ms

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 016ms

After Hooks.unlockUsers() 135ms

View Feature Login feature

@rollbackParameters @unlockUsers

Scenario Outline Checking if setting for blocking the user after X failed attempts works correctly [A-7287]

Steps

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 019ms

After Hooks.unlockUsers() 156ms

View Feature Login feature

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Steps

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 113ms

View Feature Login feature

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Steps

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 043ms

After Hooks.unlockUsers() 131ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@unlockUsers	45	0	0	0	0	45	4	0	4	3m 18s 706ms	Passed

Tag Report