Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.82	16 lip 2021, 06:58

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	3m 32s 161ms	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" 258ms

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

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

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

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

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

Given Click remind password button 171ms

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

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

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

And Extract password from mail 002ms

And Reset password from link 1s 166ms

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 018ms

After Hooks.unlockUsers() 138ms

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

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

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

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

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

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

Then Login as "neuca-admin" 1s 915ms

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

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

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 021ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 032ms

After Hooks.unlockUsers() 133ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 026ms

After Hooks.unlockUsers() 106ms

	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 32s 161ms	Passed

Tag Report