Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	develop.405	01 maj 2021, 06:13

	Steps	Scenarios	Features
Login feature	47	0	0	0	0	47	5	0	5	3m 11s 982ms	Passed

Scenario Outline Verify that user is able to login using valid login and password

Steps

Given Login as "hochland-admin" 3s 268ms

Then User is successfully logged 004ms

@rollbackParameters @unlockUsers

Scenario Outline Verify that password reset cancel login blockade [A-7286]

Steps

Given Set token of apiUsername "super-admin-skd" 111ms

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

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

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

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

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

Given Click remind password button 079ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 474ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 113ms

@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" 113ms

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

Given Failed login as "neuca-admin" 489ms

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

Given Failed login as "neuca-admin" 604ms

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

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

Given Failed login as "neuca-admin" 425ms

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

Then Login as "neuca-admin" 976ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 087ms

@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" 111ms

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

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

And Failed login as "sempertrans-admin" 620ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 077ms

@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" 113ms

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

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

And Failed login as "adama-admin" 591ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 078ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Login feature	47	0	0	0	0	47	5	0	5	3m 11s 982ms	Passed

Feature Report