Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.159	16 wrz 2021, 07:01

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 12s 783ms	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" 15s 054ms

Then User is successfully logged 029ms

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

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

Given Failed login as "swiss-krono-delivery-admin-2" 1s 596ms

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

Given Try login as "swiss-krono-delivery-admin-2" 1s 514ms

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

Given Click remind password button 265ms

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

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

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

And Extract password reset link from mailgun mail 4s 535ms

And Reset password from link 1s 343ms

Then Login as "swiss-krono-delivery-admin-2" with new password 5s 044ms

And User is successfully logged 029ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 946ms

After Hooks.clearUserPasswordDataAfterTest() 477ms

After Hooks.rollbackParameters() 092ms

After Hooks.unlockUsers() 143ms

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

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

Given Failed login as "neuca-admin" 1s 319ms

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

Given Failed login as "neuca-admin" 1s 167ms

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

Then Login as "neuca-admin" 2s 153ms

Given Failed login as "neuca-admin" 1s 256ms

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

Then Login as "neuca-admin" 2s 055ms

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 115ms

After Hooks.unlockUsers() 088ms

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

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

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

When Failed login as "sempertrans-admin" 1s 345ms

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

And Failed login as "sempertrans-admin" 1s 237ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 6s 915ms

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 197ms

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

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

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

When Failed login as "adama-admin" 1s 286ms

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

And Failed login as "adama-admin" 1s 234ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 6s 040ms

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 187ms

After Hooks.unlockUsers() 090ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "dayco-admin" 255ms

And Login as "dayco-admin" 5s 750ms

And Login as "dayco-admin" on another browser 3s 502ms

And Close second browser 156ms

And Refresh page 2s 255ms

Then Verify user is logged out 100ms

Hooks

After Hooks.rollbackRemovedAuthorities() 219ms

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

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

And Login as "farmacol-admin" 5s 600ms

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

And Close second browser 144ms

And Refresh page 2s 220ms

Then Verify user is logged out 117ms

Hooks

After Hooks.rollbackRemovedAuthorities() 191ms

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

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

And Login as "alrec-admin" 5s 615ms

And Login as "alrec-admin" on another browser 3s 445ms

And Close second browser 148ms

And Refresh page 2s 200ms

Then Verify user is logged out 107ms

Hooks

After Hooks.rollbackRemovedAuthorities() 167ms

	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	4m 12s 783ms	Passed

Feature Report