Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	develop.461	16 cze 2021, 06:57

	Steps	Scenarios	Features
@unlockUsers	45	0	0	0	0	45	4	0	4	2m 35s 528ms	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" 122ms

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

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

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

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

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

Given Click remind password button 068ms

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

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

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

And Extract password from mail 000ms

And Reset password from link 593ms

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

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 113ms

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

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

Given Failed login as "neuca-admin" 556ms

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

Given Failed login as "neuca-admin" 909ms

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

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

Given Failed login as "neuca-admin" 586ms

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

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 010ms

After Hooks.unlockUsers() 159ms

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

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 "sempertrans-admin" 504ms

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

And Failed login as "sempertrans-admin" 664ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 100ms

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

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

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

And Failed login as "adama-admin" 745ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 113ms

	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	2m 35s 528ms	Passed

Tag Report