Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	master.392	22 kwi 2021, 22:07

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

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

Steps

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

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

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

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

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

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

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

Given Click remind password button 072ms

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

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

And Extract password from mail 001ms

And Reset password from link 441ms

Then Login as "swiss-krono-delivery-admin" 3s 076ms

And User is successfully logged 006ms

Hooks

After Hooks.rollbackParameters() 018ms

After Hooks.unlockUsers() 120ms

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

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

Given Failed login as "neuca-admin" 434ms

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

Given Failed login as "neuca-admin" 556ms

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

Then Login as "neuca-admin" 991ms

Given Failed login as "neuca-admin" 432ms

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

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

And User is successfully logged 006ms

Hooks

After Hooks.rollbackParameters() 004ms

After Hooks.unlockUsers() 128ms

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

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

And Prepare parameter "BLOCKED_USER_DURATION_IN_MINUTES" with value: "1" 023ms

When Failed login as "sempertrans-admin" 843ms

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

And Failed login as "sempertrans-admin" 661ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 078ms

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

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 "adama-admin" 425ms

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

And Failed login as "adama-admin" 555ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 097ms

	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 723ms	Passed

Feature Report