Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.158	15 wrz 2021, 06:58

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 14s 739ms	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 323ms

Then User is successfully logged 029ms

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

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

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

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

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

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

Given Click remind password button 217ms

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

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

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

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

And Reset password from link 1s 343ms

Then Login as "swiss-krono-delivery-admin-2" with new password 5s 183ms

And User is successfully logged 030ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 965ms

After Hooks.clearUserPasswordDataAfterTest() 470ms

After Hooks.rollbackParameters() 091ms

After Hooks.unlockUsers() 142ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 092ms

After Hooks.unlockUsers() 089ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 185ms

After Hooks.unlockUsers() 085ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 193ms

After Hooks.unlockUsers() 096ms

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

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

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

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

And Close second browser 166ms

And Refresh page 2s 246ms

Then Verify user is logged out 100ms

Hooks

After Hooks.rollbackRemovedAuthorities() 254ms

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

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

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

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

And Close second browser 155ms

And Refresh page 2s 203ms

Then Verify user is logged out 108ms

Hooks

After Hooks.rollbackRemovedAuthorities() 175ms

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

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

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

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

And Close second browser 161ms

And Refresh page 2s 205ms

Then Verify user is logged out 104ms

Hooks

After Hooks.rollbackRemovedAuthorities() 171ms

	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 14s 739ms	Passed

Feature Report