Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	master.329	22 kwi 2021, 13:55

	Steps	Scenarios	Features
Login feature	47	0	0	0	0	47	5	0	5	3m 10s 873ms	Passed

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

Steps

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

Then User is successfully logged 003ms

@rollbackParameters @unlockUsers

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

Steps

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

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

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

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

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

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

Given Click remind password button 082ms

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

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

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

And Extract password from mail 001ms

And Reset password from link 476ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 083ms

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

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

Given Failed login as "neuca-admin" 487ms

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

Given Failed login as "neuca-admin" 619ms

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

Then Login as "neuca-admin" 951ms

Given Failed login as "neuca-admin" 533ms

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

Then Login as "neuca-admin" 972ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 089ms

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

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

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

And Failed login as "sempertrans-admin" 632ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 003ms

After Hooks.unlockUsers() 074ms

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

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

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

And Failed login as "adama-admin" 601ms

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

Then Wait "62" seconds 1m 2s

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

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 10s 873ms	Passed

Feature Report