Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.1	17 Jul 2021, 02:42

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	3m 12s 458ms	Passed

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" 2s 205ms

Then User is successfully logged 003ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Given Click remind password button 069ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 33s 139ms

And Extract password from mailgun mail 3s 902ms

And Reset password from link 632ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 087ms

@rollbackParameters @unlockUsers

Scenario Outline Checking if setting for blocking the user after X failed attempts works correctly [A-7287]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 094ms

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

Given Failed login as "neuca-admin" 477ms

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

Given Failed login as "neuca-admin" 469ms

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

Then Login as "neuca-admin" 804ms

Given Failed login as "neuca-admin" 443ms

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

Then Login as "neuca-admin" 798ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 091ms

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 094ms

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

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

And Failed login as "sempertrans-admin" 482ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 077ms

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 105ms

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

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

And Failed login as "adama-admin" 450ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 993ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 074ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-bausch" 098ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 029ms

And Login as "bausch-admin" 1s 587ms

And Login as "bausch-admin" on another browser 1s 817ms

And Close second browser 077ms

And Refresh page 2s 123ms

Then Verify user is logged out 035ms

Hooks

After Hooks.rollbackRemovedAuthorities() 029ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 094ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "farmacol-admin" 028ms

And Login as "farmacol-admin" 1s 382ms

And Login as "farmacol-admin" on another browser 1s 751ms

And Close second browser 072ms

And Refresh page 2s 122ms

Then Verify user is logged out 031ms

Hooks

After Hooks.rollbackRemovedAuthorities() 028ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 097ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "alrec-admin" 028ms

And Login as "alrec-admin" 1s 173ms

And Login as "alrec-admin" on another browser 1s 762ms

And Close second browser 073ms

And Refresh page 2s 125ms

Then Verify user is logged out 030ms

Hooks

After Hooks.rollbackRemovedAuthorities() 030ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Login feature	68	0	0	0	0	68	8	0	8	3m 12s 458ms	Passed

Feature Report