Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.85	19 lip 2021, 03:57

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 1s 533ms	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 724ms

Then User is successfully logged 027ms

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

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

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

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

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

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

Given Click remind password button 177ms

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

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

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

And Extract password from mailgun mail 4s 006ms

And Reset password from link 1s 357ms

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 017ms

After Hooks.unlockUsers() 151ms

@rollbackParameters @unlockUsers

Scenario Outline Checking if setting for blocking the user after X failed attempts works correctly [A-7287]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 249ms

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

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

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

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

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

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

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

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

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 022ms

After Hooks.unlockUsers() 147ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 135ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 026ms

After Hooks.unlockUsers() 143ms

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

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

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

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

And Close second browser 149ms

And Refresh page 2s 176ms

Then Verify user is logged out 115ms

Hooks

After Hooks.rollbackRemovedAuthorities() 141ms

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

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

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

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

And Close second browser 149ms

And Refresh page 2s 205ms

Then Verify user is logged out 090ms

Hooks

After Hooks.rollbackRemovedAuthorities() 159ms

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

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

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

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

And Close second browser 150ms

And Refresh page 2s 180ms

Then Verify user is logged out 102ms

Hooks

After Hooks.rollbackRemovedAuthorities() 163ms

	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 1s 533ms	Passed

Feature Report