Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.154	11 wrz 2021, 06:36

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	3m 48s 394ms	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 367ms

Then User is successfully logged 031ms

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

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

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

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

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

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

Given Click remind password button 260ms

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

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

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

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

And Reset password from link 1s 408ms

Then Login as "swiss-krono-delivery-admin-2" with new password 4s 835ms

And User is successfully logged 030ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 002ms

After Hooks.clearUserPasswordDataAfterTest() 473ms

After Hooks.rollbackParameters() 110ms

After Hooks.unlockUsers() 145ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 102ms

After Hooks.unlockUsers() 082ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 7s 079ms

And User is successfully logged 031ms

Hooks

After Hooks.rollbackParameters() 193ms

After Hooks.unlockUsers() 089ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 198ms

After Hooks.unlockUsers() 092ms

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

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

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

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

And Close second browser 157ms

And Refresh page 2s 222ms

Then Verify user is logged out 098ms

Hooks

After Hooks.rollbackRemovedAuthorities() 213ms

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

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

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

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

And Close second browser 143ms

And Refresh page 2s 211ms

Then Verify user is logged out 114ms

Hooks

After Hooks.rollbackRemovedAuthorities() 156ms

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

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

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

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

And Close second browser 150ms

And Refresh page 2s 261ms

Then Verify user is logged out 108ms

Hooks

After Hooks.rollbackRemovedAuthorities() 151ms

	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 48s 394ms	Passed

Feature Report