Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.88	20 lip 2021, 18:16

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 4s 301ms	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" 9s 677ms

Then User is successfully logged 026ms

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

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

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

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

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

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

Given Click remind password button 167ms

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

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

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

And Extract password from mailgun mail 4s 566ms

And Reset password from link 1s 258ms

Then Login as "swiss-krono-delivery-admin" 4s 637ms

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 019ms

After Hooks.unlockUsers() 166ms

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

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

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

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

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

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

Then Login as "neuca-admin" 1s 969ms

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 016ms

After Hooks.unlockUsers() 167ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 5s 477ms

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 026ms

After Hooks.unlockUsers() 170ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 2s 250ms

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 028ms

After Hooks.unlockUsers() 116ms

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

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

And Login as "bausch-admin" 6s 269ms

And Login as "bausch-admin" on another browser 3s 487ms

And Close second browser 156ms

And Refresh page 2s 180ms

Then Verify user is logged out 116ms

Hooks

After Hooks.rollbackRemovedAuthorities() 152ms

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

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

And Login as "farmacol-admin" 6s 478ms

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

And Close second browser 146ms

And Refresh page 2s 310ms

Then Verify user is logged out 098ms

Hooks

After Hooks.rollbackRemovedAuthorities() 386ms

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

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

And Login as "alrec-admin" 4s 217ms

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

And Close second browser 148ms

And Refresh page 2s 192ms

Then Verify user is logged out 106ms

Hooks

After Hooks.rollbackRemovedAuthorities() 246ms

	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 4s 301ms	Passed

Feature Report