Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.94	25 lip 2021, 04:52

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 24s 697ms	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 479ms

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

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

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

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

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

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

Given Click remind password button 181ms

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

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

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

And Extract password from mailgun mail 3s 882ms

And Reset password from link 1s 430ms

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

And User is successfully logged 024ms

Hooks

After Hooks.rollbackParameters() 014ms

After Hooks.unlockUsers() 149ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 021ms

After Hooks.unlockUsers() 182ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 026ms

After Hooks.unlockUsers() 107ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 046ms

Hooks

After Hooks.rollbackParameters() 030ms

After Hooks.unlockUsers() 122ms

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

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

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

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

And Close second browser 148ms

And Refresh page 2s 185ms

Then Verify user is logged out 110ms

Hooks

After Hooks.rollbackRemovedAuthorities() 208ms

@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-farmacol" 225ms

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

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

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

And Close second browser 152ms

And Refresh page 2s 227ms

Then Verify user is logged out 093ms

Hooks

After Hooks.rollbackRemovedAuthorities() 127ms

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

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

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

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

And Close second browser 149ms

And Refresh page 2s 183ms

Then Verify user is logged out 108ms

Hooks

After Hooks.rollbackRemovedAuthorities() 167ms

	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 24s 697ms	Passed

Feature Report