Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.57	27 cze 2021, 06:33

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	4m 6s 804ms	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" 234ms

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

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

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

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

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

Given Click remind password button 180ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Restart hasła! | Password reset!" 1m 20s 390ms

And Extract password from mail 001ms

And Reset password from link 973ms

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 016ms

After Hooks.unlockUsers() 146ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 019ms

After Hooks.unlockUsers() 145ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 121ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 134ms

	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	4m 6s 804ms	Passed

Tag Report