Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.95	26 lip 2021, 05:36

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 17s 869ms	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 249ms

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

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

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

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

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

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

Given Click remind password button 173ms

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

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!" 31s 775ms

And Extract password from mailgun mail 4s 463ms

And Reset password from link 1s 351ms

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 016ms

After Hooks.unlockUsers() 153ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 030ms

After Hooks.unlockUsers() 146ms

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 138ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-adama" 331ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 024ms

After Hooks.unlockUsers() 135ms

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

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

And Login as "bausch-admin" 7s 956ms

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

And Close second browser 150ms

And Refresh page 2s 190ms

Then Verify user is logged out 119ms

Hooks

After Hooks.rollbackRemovedAuthorities() 203ms

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

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

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

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

And Close second browser 150ms

And Refresh page 2s 195ms

Then Verify user is logged out 085ms

Hooks

After Hooks.rollbackRemovedAuthorities() 160ms

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

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

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

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

And Close second browser 144ms

And Refresh page 2s 227ms

Then Verify user is logged out 110ms

Hooks

After Hooks.rollbackRemovedAuthorities() 250ms

	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 17s 869ms	Passed

Feature Report