Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.84	18 lip 2021, 04:05

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 2s 434ms	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 649ms

Then User is successfully logged 028ms

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

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

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

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

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

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

Given Click remind password button 179ms

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

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

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

And Extract password from mailgun mail 4s 546ms

And Reset password from link 1s 406ms

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 015ms

After Hooks.unlockUsers() 168ms

@rollbackParameters @unlockUsers

Scenario Outline Checking if setting for blocking the user after X failed attempts works correctly [A-7287]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 334ms

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

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

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

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

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

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

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

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

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 011ms

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) 001ms

Steps

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 133ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 031ms

After Hooks.unlockUsers() 149ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-bausch" 330ms

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

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

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

And Close second browser 150ms

And Refresh page 2s 193ms

Then Verify user is logged out 122ms

Hooks

After Hooks.rollbackRemovedAuthorities() 160ms

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

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

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

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

And Close second browser 147ms

And Refresh page 2s 217ms

Then Verify user is logged out 095ms

Hooks

After Hooks.rollbackRemovedAuthorities() 144ms

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

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

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

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

And Close second browser 147ms

And Refresh page 2s 178ms

Then Verify user is logged out 112ms

Hooks

After Hooks.rollbackRemovedAuthorities() 247ms

	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 2s 434ms	Passed

Feature Report