Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	develop.393	23 kwi 2021, 05:44

	Steps	Scenarios	Features
Login feature	47	0	0	0	0	47	5	0	5	3m 20s 815ms	Passed

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

Steps

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

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

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

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

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

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

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

Given Click remind password button 082ms

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

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!" 56s 284ms

And Extract password from mail 001ms

And Reset password from link 465ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 005ms

After Hooks.unlockUsers() 095ms

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

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

Given Failed login as "neuca-admin" 477ms

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

Given Failed login as "neuca-admin" 590ms

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

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

Given Failed login as "neuca-admin" 446ms

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

Then Login as "neuca-admin" 975ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 096ms

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

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

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

And Failed login as "sempertrans-admin" 612ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 2s 336ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 102ms

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

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

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

And Failed login as "adama-admin" 610ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 2s 404ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 088ms

	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 20s 815ms	Passed

Feature Report