Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	develop.387	20 kwi 2021, 06:09

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	3m 8s 728ms	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" 096ms

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

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

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

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

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

Given Click remind password button 073ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 482ms

Then Login as "swiss-krono-delivery-admin" 2s 349ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 124ms

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

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

Given Failed login as "neuca-admin" 485ms

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

Given Failed login as "neuca-admin" 607ms

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

Then Login as "neuca-admin" 5s 475ms

Given Failed login as "neuca-admin" 493ms

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

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

And User is successfully logged 009ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 092ms

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

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

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

When Failed login as "sempertrans-admin" 523ms

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

And Failed login as "sempertrans-admin" 663ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 075ms

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

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 "adama-admin" 498ms

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

And Failed login as "adama-admin" 632ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 020ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 078ms

	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 8s 728ms	Passed

Tag Report