Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.69	06 lip 2021, 06:05

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	3m 36s 844ms	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" 319ms

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

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

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

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

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

Given Click remind password button 173ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 1s 043ms

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 015ms

After Hooks.unlockUsers() 129ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 013ms

After Hooks.unlockUsers() 150ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 117ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 129ms

	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 36s 844ms	Passed

Tag Report