Cucumber-JVM Reports - Tag: @rollbackParameters

Project	Number	Date
ApolloFullRunnerReport	develop-kapibary.401	28 kwi 2021, 19:06

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

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

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

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

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

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

Given Click remind password button 072ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 461ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 079ms

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

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

Given Failed login as "neuca-admin" 580ms

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

Given Failed login as "neuca-admin" 620ms

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

Then Login as "neuca-admin" 930ms

Given Failed login as "neuca-admin" 472ms

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

Then Login as "neuca-admin" 976ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 090ms

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

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

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

And Failed login as "sempertrans-admin" 635ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 093ms

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

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

When Failed login as "adama-admin" 498ms

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

And Failed login as "adama-admin" 606ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 078ms

	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 3s 041ms	Passed

Tag Report