Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	develop.388	21 kwi 2021, 05:21

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

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

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

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

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

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

Given Click remind password button 078ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 492ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 081ms

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

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

Given Failed login as "neuca-admin" 478ms

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

Given Failed login as "neuca-admin" 595ms

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

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

Given Failed login as "neuca-admin" 476ms

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

Then Login as "neuca-admin" 992ms

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 085ms

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

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

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

And Failed login as "sempertrans-admin" 578ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 079ms

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

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

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

And Failed login as "adama-admin" 608ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 088ms

	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 4s 592ms	Passed

Tag Report