Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.87	20 lip 2021, 04:12

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	3m 39s 750ms	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 627ms

Then User is successfully logged 030ms

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

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

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

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

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

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

Given Click remind password button 171ms

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

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

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

And Extract password from mailgun mail 4s 085ms

And Reset password from link 1s 267ms

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 016ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 152ms

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 031ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 030ms

After Hooks.unlockUsers() 128ms

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

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

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

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

And Close second browser 157ms

And Refresh page 2s 184ms

Then Verify user is logged out 112ms

Hooks

After Hooks.rollbackRemovedAuthorities() 153ms

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

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

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

And Close second browser 147ms

And Refresh page 2s 206ms

Then Verify user is logged out 112ms

Hooks

After Hooks.rollbackRemovedAuthorities() 157ms

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

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

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

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

And Close second browser 148ms

And Refresh page 2s 180ms

Then Verify user is logged out 110ms

Hooks

After Hooks.rollbackRemovedAuthorities() 187ms

	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	3m 39s 750ms	Passed

Feature Report