Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.64	01 lip 2021, 04:35

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

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

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

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

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

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

Given Click remind password button 167ms

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

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

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

And Extract password from mail 000ms

And Reset password from link 993ms

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 014ms

After Hooks.unlockUsers() 120ms

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

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

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

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

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

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

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

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

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

Then Login as "neuca-admin" 2s

And User is successfully logged 037ms

Hooks

After Hooks.rollbackParameters() 021ms

After Hooks.unlockUsers() 177ms

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

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 "sempertrans-admin" 1s 287ms

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 126ms

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 034ms

After Hooks.unlockUsers() 114ms

	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 37s 402ms	Passed

Tag Report