Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.24	29 lip 2021, 03:52

	Steps	Scenarios	Features
Login feature	68	0	0	0	0	68	8	0	8	3m 13s 336ms	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" 2s 903ms

Then User is successfully logged 002ms

@rollbackParameters @unlockUsers

Scenario Outline Verify that password reset cancel login blockade [A-7286]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-skd" 091ms

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

Given Failed login as "swiss-krono-delivery-admin" 472ms

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

Given Try login as "swiss-krono-delivery-admin" 512ms

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

Given Click remind password button 068ms

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

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

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

And Extract password from mailgun mail 3s 753ms

And Reset password from link 940ms

Then Login as "swiss-krono-delivery-admin" 1s 359ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 087ms

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

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

Given Failed login as "neuca-admin" 459ms

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

Given Failed login as "neuca-admin" 412ms

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

Then Login as "neuca-admin" 805ms

Given Failed login as "neuca-admin" 455ms

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

Then Login as "neuca-admin" 809ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 001ms

After Hooks.unlockUsers() 091ms

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

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

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

When Failed login as "sempertrans-admin" 460ms

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

And Failed login as "sempertrans-admin" 467ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 1s 830ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 074ms

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

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

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

When Failed login as "adama-admin" 454ms

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

And Failed login as "adama-admin" 457ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 1s 701ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 079ms

@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-bausch" 091ms

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

And Login as "bausch-admin" 1s 763ms

And Login as "bausch-admin" on another browser 1s 809ms

And Close second browser 076ms

And Refresh page 2s 126ms

Then Verify user is logged out 037ms

Hooks

After Hooks.rollbackRemovedAuthorities() 075ms

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

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

And Login as "farmacol-admin" 1s 338ms

And Login as "farmacol-admin" on another browser 1s 729ms

And Close second browser 072ms

And Refresh page 2s 120ms

Then Verify user is logged out 030ms

Hooks

After Hooks.rollbackRemovedAuthorities() 032ms

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

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

And Login as "alrec-admin" 1s 450ms

And Login as "alrec-admin" on another browser 1s 729ms

And Close second browser 076ms

And Refresh page 2s 108ms

Then Verify user is logged out 029ms

Hooks

After Hooks.rollbackRemovedAuthorities() 023ms

	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	3m 13s 336ms	Passed

Feature Report