Cucumber-JVM Reports - Tag: @unlockUsers

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.50	30 cze 2021, 09:31

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

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

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

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

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

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

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 265ms

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

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

And Extract password from mail 001ms

And Reset password from link 1s 059ms

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 028ms

After Hooks.unlockUsers() 144ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 015ms

After Hooks.unlockUsers() 165ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 124ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 036ms

After Hooks.unlockUsers() 166ms

	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 556ms	Passed

Tag Report