Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.156	13 wrz 2021, 06:47

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	3m 53s 599ms	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 553ms

Then User is successfully logged 034ms

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

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

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

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

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

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

Given Click remind password button 225ms

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

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

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

And Extract password reset link from mailgun mail 4s 472ms

And Reset password from link 1s 361ms

Then Login as "swiss-krono-delivery-admin-2" with new password 4s 994ms

And User is successfully logged 025ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 994ms

After Hooks.clearUserPasswordDataAfterTest() 478ms

After Hooks.rollbackParameters() 099ms

After Hooks.unlockUsers() 102ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 098ms

After Hooks.unlockUsers() 090ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 6s 763ms

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 192ms

After Hooks.unlockUsers() 084ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 5s 980ms

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 202ms

After Hooks.unlockUsers() 088ms

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

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "dayco-admin" 234ms

And Login as "dayco-admin" 5s 638ms

And Login as "dayco-admin" on another browser 3s 275ms

And Close second browser 149ms

And Refresh page 2s 193ms

Then Verify user is logged out 110ms

Hooks

After Hooks.rollbackRemovedAuthorities() 206ms

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

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

And Login as "farmacol-admin" 5s 597ms

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

And Close second browser 150ms

And Refresh page 2s 227ms

Then Verify user is logged out 090ms

Hooks

After Hooks.rollbackRemovedAuthorities() 142ms

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

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

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

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

And Close second browser 156ms

And Refresh page 2s 244ms

Then Verify user is logged out 112ms

Hooks

After Hooks.rollbackRemovedAuthorities() 146ms

	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 53s 599ms	Passed

Feature Report