Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.98	29 lip 2021, 06:08

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 19s 984ms	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 740ms

Then User is successfully logged 027ms

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

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

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

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

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

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

Given Click remind password button 142ms

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

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

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

And Extract password from mailgun mail 3s 951ms

And Reset password from link 1s 347ms

Then Login as "swiss-krono-delivery-admin" 5s 534ms

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 017ms

After Hooks.unlockUsers() 147ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 044ms

Hooks

After Hooks.rollbackParameters() 018ms

After Hooks.unlockUsers() 166ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 026ms

After Hooks.unlockUsers() 124ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 032ms

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

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

And Login as "bausch-admin" 8s 189ms

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

And Close second browser 156ms

And Refresh page 2s 173ms

Then Verify user is logged out 108ms

Hooks

After Hooks.rollbackRemovedAuthorities() 202ms

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

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

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

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

And Close second browser 153ms

And Refresh page 2s 193ms

Then Verify user is logged out 085ms

Hooks

After Hooks.rollbackRemovedAuthorities() 158ms

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

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

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

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

And Close second browser 140ms

And Refresh page 2s 206ms

Then Verify user is logged out 104ms

Hooks

After Hooks.rollbackRemovedAuthorities() 140ms

	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 19s 984ms	Passed

Feature Report