Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	master.419	11 maj 2021, 22:24

	Steps	Scenarios	Features
Login feature	47	0	0	0	0	47	5	0	5	2m 56s 011ms	Passed

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

Steps

Given Login as "hochland-admin" 1s 213ms

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

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

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

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

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

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

Given Click remind password button 072ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 463ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 004ms

After Hooks.unlockUsers() 089ms

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

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

Given Failed login as "neuca-admin" 479ms

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

Given Failed login as "neuca-admin" 611ms

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

Then Login as "neuca-admin" 991ms

Given Failed login as "neuca-admin" 461ms

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

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 093ms

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

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

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

And Failed login as "sempertrans-admin" 603ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 076ms

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

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

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

And Failed login as "adama-admin" 591ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 076ms

	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	2m 56s 011ms	Passed

Feature Report