Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.83	17 lip 2021, 03:37

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

Then User is successfully logged 029ms

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

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

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

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

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

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

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

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

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

And Extract password from mailgun mail 4s 047ms

And Reset password from link 1s 320ms

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 015ms

After Hooks.unlockUsers() 144ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 011ms

After Hooks.unlockUsers() 143ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 028ms

Hooks

After Hooks.rollbackParameters() 028ms

After Hooks.unlockUsers() 131ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 030ms

After Hooks.unlockUsers() 121ms

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

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

And Login as "bausch-admin" 8s 117ms

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

And Close second browser 151ms

And Refresh page 2s 185ms

Then Verify user is logged out 118ms

Hooks

After Hooks.rollbackRemovedAuthorities() 162ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 220ms

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

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

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

And Close second browser 150ms

And Refresh page 2s 199ms

Then Verify user is logged out 118ms

Hooks

After Hooks.rollbackRemovedAuthorities() 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-alrec" 227ms

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

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

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

And Close second browser 151ms

And Refresh page 2s 179ms

Then Verify user is logged out 116ms

Hooks

After Hooks.rollbackRemovedAuthorities() 246ms

	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 4s 044ms	Passed

Feature Report