Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.3	19 Jul 2021, 02:44

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	2m 51s 884ms	Passed

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

Then User is successfully logged 004ms

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

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

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

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

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

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

Given Click remind password button 063ms

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

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

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

And Extract password from mailgun mail 4s 034ms

And Reset password from link 818ms

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 093ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

Given Failed login as "neuca-admin" 467ms

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

Given Failed login as "neuca-admin" 434ms

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

Then Login as "neuca-admin" 849ms

Given Failed login as "neuca-admin" 514ms

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

Then Login as "neuca-admin" 887ms

And User is successfully logged 009ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 085ms

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

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

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

And Failed login as "sempertrans-admin" 452ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 146ms

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

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

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

And Failed login as "adama-admin" 459ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 120ms

@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-bausch" 104ms

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

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

And Login as "bausch-admin" on another browser 2s 541ms

And Close second browser 128ms

And Refresh page 2s 005ms

Then Verify user is logged out 105ms

Hooks

After Hooks.rollbackRemovedAuthorities() 625ms

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

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

And Login as "farmacol-admin" 2s 173ms

And Login as "farmacol-admin" on another browser 3s 088ms

And Close second browser 077ms

And Refresh page 2s 104ms

Then Verify user is logged out 026ms

Hooks

After Hooks.rollbackRemovedAuthorities() 474ms

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

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

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

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

And Close second browser 070ms

And Refresh page 2s 174ms

Then Verify user is logged out 023ms

Hooks

After Hooks.rollbackRemovedAuthorities() 503ms

	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	2m 51s 884ms	Passed

Feature Report