Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.148	07 wrz 2021, 06:21

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 14s 421ms	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 499ms

Then User is successfully logged 028ms

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

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

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

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

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

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

Given Click remind password button 270ms

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

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

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

And Extract password reset link from mailgun mail 3s 965ms

And Reset password from link 1s 369ms

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

And User is successfully logged 027ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 004ms

After Hooks.clearUserPasswordDataAfterTest() 690ms

After Hooks.rollbackParameters() 095ms

After Hooks.unlockUsers() 140ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 033ms

Hooks

After Hooks.rollbackParameters() 094ms

After Hooks.unlockUsers() 100ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 189ms

After Hooks.unlockUsers() 092ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 5s 912ms

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 196ms

After Hooks.unlockUsers() 085ms

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

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

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

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

And Close second browser 155ms

And Refresh page 2s 216ms

Then Verify user is logged out 104ms

Hooks

After Hooks.rollbackRemovedAuthorities() 337ms

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

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

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

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

And Close second browser 151ms

And Refresh page 2s 210ms

Then Verify user is logged out 115ms

Hooks

After Hooks.rollbackRemovedAuthorities() 146ms

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

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

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

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

And Close second browser 151ms

And Refresh page 2s 215ms

Then Verify user is logged out 114ms

Hooks

After Hooks.rollbackRemovedAuthorities() 163ms

	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 14s 421ms	Passed

Feature Report