Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.72	09 lip 2021, 07:01

	Steps	Scenarios	Features
@rollbackParameters	45	0	0	0	0	45	4	0	4	3m 47s 175ms	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" 342ms

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

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

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

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

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

Given Click remind password button 152ms

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

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

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

And Extract password from mail 000ms

And Reset password from link 1s 141ms

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 021ms

After Hooks.unlockUsers() 234ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 047ms

Hooks

After Hooks.rollbackParameters() 023ms

After Hooks.unlockUsers() 151ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 6s 963ms

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 032ms

After Hooks.unlockUsers() 182ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 024ms

After Hooks.unlockUsers() 140ms

	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	3m 47s 175ms	Passed

Tag Report