Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.93	24 lip 2021, 05:47

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	4m 22s 208ms	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" 14s 231ms

Then User is successfully logged 031ms

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

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

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

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

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

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

Given Click remind password button 183ms

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

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

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

And Extract password from mailgun mail 4s 223ms

And Reset password from link 1s 309ms

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 014ms

After Hooks.unlockUsers() 150ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 045ms

Hooks

After Hooks.rollbackParameters() 011ms

After Hooks.unlockUsers() 166ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 023ms

Hooks

After Hooks.rollbackParameters() 028ms

After Hooks.unlockUsers() 141ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 028ms

After Hooks.unlockUsers() 125ms

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

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

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

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

And Close second browser 158ms

And Refresh page 2s 175ms

Then Verify user is logged out 096ms

Hooks

After Hooks.rollbackRemovedAuthorities() 151ms

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

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

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

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

And Close second browser 147ms

And Refresh page 2s 185ms

Then Verify user is logged out 115ms

Hooks

After Hooks.rollbackRemovedAuthorities() 153ms

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

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

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

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

And Close second browser 156ms

And Refresh page 2s 206ms

Then Verify user is logged out 105ms

Hooks

After Hooks.rollbackRemovedAuthorities() 259ms

	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 22s 208ms	Passed

Feature Report