Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	develop.379	14 kwi 2021, 05:23

	Steps	Scenarios	Features
Login feature	47	0	0	0	0	47	5	0	5	2m 38s 834ms	Passed

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

Steps

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

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

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

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

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

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

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

Given Click remind password button 078ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 413ms

Then Login as "swiss-krono-delivery-admin" 2s 511ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 078ms

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

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

Given Failed login as "neuca-admin" 465ms

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

Given Failed login as "neuca-admin" 656ms

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

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

Given Failed login as "neuca-admin" 495ms

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

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

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 088ms

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

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

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

And Failed login as "sempertrans-admin" 641ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 079ms

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

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

And Failed login as "adama-admin" 634ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 004ms

After Hooks.unlockUsers() 074ms

	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 38s 834ms	Passed

Feature Report