Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	develop.380	15 kwi 2021, 01:04

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

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

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

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

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

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

Given Click remind password button 079ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 469ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 085ms

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

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

Given Failed login as "neuca-admin" 498ms

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

Given Failed login as "neuca-admin" 625ms

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

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

Given Failed login as "neuca-admin" 480ms

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

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

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

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

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

And Failed login as "sempertrans-admin" 617ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 087ms

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

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

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

And Failed login as "adama-admin" 653ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 075ms

	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 12s 780ms	Passed

Tag Report