Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.66	03 lip 2021, 06:35

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	3m 30s 777ms	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" 262ms

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

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

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

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

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

Given Click remind password button 184ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 1s 158ms

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 015ms

After Hooks.unlockUsers() 142ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 019ms

After Hooks.unlockUsers() 148ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 027ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 034ms

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 30s 777ms	Passed

Tag Report