Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	master.420	12 maj 2021, 06:42

	Steps	Scenarios	Features
@rollbackParameters	45	0	0	0	0	45	4	0	4	2m 56s 042ms	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" 120ms

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

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

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

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

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

Given Click remind password button 077ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 455ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 080ms

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

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

Given Failed login as "neuca-admin" 496ms

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

Given Failed login as "neuca-admin" 608ms

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

Then Login as "neuca-admin" 969ms

Given Failed login as "neuca-admin" 502ms

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

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

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 088ms

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

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

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

When Failed login as "sempertrans-admin" 506ms

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

And Failed login as "sempertrans-admin" 628ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 1s 157ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 076ms

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

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

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

And Failed login as "adama-admin" 633ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 1s 201ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 075ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackParameters	45	0	0	0	0	45	4	0	4	2m 56s 042ms	Passed

Tag Report