Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	develop.400	28 kwi 2021, 05:38

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	2m 52s 637ms	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" 104ms

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

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

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

Given Try login as "swiss-krono-delivery-admin" 698ms

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

Given Click remind password button 081ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 448ms

Then Login as "swiss-krono-delivery-admin" 1s 737ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 084ms

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

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

Given Failed login as "neuca-admin" 449ms

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

Given Failed login as "neuca-admin" 566ms

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

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

Given Failed login as "neuca-admin" 473ms

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

Then Login as "neuca-admin" 978ms

And User is successfully logged 006ms

Hooks

After Hooks.rollbackParameters() 002ms

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]

Steps

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

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

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

When Failed login as "sempertrans-admin" 540ms

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

And Failed login as "sempertrans-admin" 604ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 2s 450ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 086ms

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

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

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

When Failed login as "adama-admin" 504ms

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

And Failed login as "adama-admin" 585ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 2s 425ms

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 076ms

	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	2m 52s 637ms	Passed

Tag Report