Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	develop.461	16 cze 2021, 06:57

	Steps	Scenarios	Features
Login feature	62	0	0	0	0	62	8	0	8	2m 57s 930ms	Passed

Scenario Outline Verify that user is able to login using valid login and password

Steps

Given Login as "hochland-admin" 3s 336ms

Then User is successfully logged 003ms

@rollbackParameters @unlockUsers

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

Steps

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

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

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

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

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

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

Given Click remind password button 068ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Restart hasła! | Password reset!" 12s 777ms

And Extract password from mail 000ms

And Reset password from link 593ms

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

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 113ms

@rollbackParameters @unlockUsers

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

Steps

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

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

Given Failed login as "neuca-admin" 556ms

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

Given Failed login as "neuca-admin" 909ms

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

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

Given Failed login as "neuca-admin" 586ms

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

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 010ms

After Hooks.unlockUsers() 159ms

@rollbackParameters @unlockUsers

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

Steps

Given Set token of apiUsername "super-admin-sempertrans" 119ms

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

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

When Failed login as "sempertrans-admin" 504ms

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

And Failed login as "sempertrans-admin" 664ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 2s 426ms

And User is successfully logged 003ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 100ms

@rollbackParameters @unlockUsers

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

Steps

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

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

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

When Failed login as "adama-admin" 566ms

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

And Failed login as "adama-admin" 745ms

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 002ms

After Hooks.unlockUsers() 113ms

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

Steps

Given Login as "bausch-admin" 2s 268ms

And Login as "bausch-admin" on another browser 2s 562ms

And Close second browser 075ms

And Refresh page 2s 135ms

Then Verify user is logged out 046ms

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

Steps

Given Login as "farmacol-admin" 1s 322ms

And Login as "farmacol-admin" on another browser 2s 548ms

And Close second browser 128ms

And Refresh page 2s 125ms

Then Verify user is logged out 039ms

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

Steps

Given Login as "alrec-admin" 1s 799ms

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

And Close second browser 071ms

And Refresh page 2s 128ms

Then Verify user is logged out 029ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Login feature	62	0	0	0	0	62	8	0	8	2m 57s 930ms	Passed

Feature Report