Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.149	08 wrz 2021, 06:16

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 15s 390ms	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 827ms

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

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

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

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

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

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

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 238ms

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

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

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

And Reset password from link 1s 478ms

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

And User is successfully logged 029ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 077ms

After Hooks.clearUserPasswordDataAfterTest() 711ms

After Hooks.rollbackParameters() 097ms

After Hooks.unlockUsers() 138ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 113ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 200ms

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-adama" 220ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 183ms

After Hooks.unlockUsers() 094ms

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

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

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

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

And Close second browser 150ms

And Refresh page 2s 209ms

Then Verify user is logged out 108ms

Hooks

After Hooks.rollbackRemovedAuthorities() 191ms

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

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

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

And Close second browser 155ms

And Refresh page 2s 251ms

Then Verify user is logged out 091ms

Hooks

After Hooks.rollbackRemovedAuthorities() 152ms

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

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

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

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

And Close second browser 147ms

And Refresh page 2s 214ms

Then Verify user is logged out 108ms

Hooks

After Hooks.rollbackRemovedAuthorities() 156ms

	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 15s 390ms	Passed

Feature Report