Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	kapibary.44	17 cze 2021, 00:11

	Steps	Scenarios	Features
Login feature	59	1	2	0	0	62	7	1	8	4m 9s 091ms	Failed

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

Steps

Given Login as "hochland-admin" 15s 071ms

Then User is successfully logged 029ms

@rollbackParameters @unlockUsers

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

Steps

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

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

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

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

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

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

Given Click remind password button 179ms

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

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

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

And Extract password from mail 000ms

And Reset password from link 123ms

Error message

org.openqa.selenium.WebDriverException: unknown error: net::ERR_NAME_NOT_RESOLVED
  (Session info: headless chrome=91.0.4472.106)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.0P7KcA}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.106, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e1801bfd7fc29de801f7842a91e41467
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:310)
	at CucumberTests.LoginTest.resetPasswordFromLink(LoginTest.java:134)
	at ✽.Reset password from link(file:Features/Atom/Logins/Login.feature:23)

Then Login as "swiss-krono-delivery-admin" 000ms

And User is successfully logged 000ms

Hooks

After Hooks.rollbackParameters() 018ms

After Hooks.unlockUsers() 135ms

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

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

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

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

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

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

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

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

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

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

And User is successfully logged 049ms

Hooks

After Hooks.rollbackParameters() 020ms

After Hooks.unlockUsers() 213ms

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 026ms

After Hooks.unlockUsers() 125ms

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 025ms

Hooks

After Hooks.rollbackParameters() 027ms

After Hooks.unlockUsers() 116ms

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

Steps

Given Login as "bausch-admin" 7s 549ms

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

And Close second browser 151ms

And Refresh page 2s 193ms

Then Verify user is logged out 107ms

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

Steps

Given Login as "farmacol-admin" 2s 390ms

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

And Close second browser 148ms

And Refresh page 2s 177ms

Then Verify user is logged out 105ms

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

Steps

Given Login as "alrec-admin" 6s 024ms

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

And Close second browser 151ms

And Refresh page 2s 216ms

Then Verify user is logged out 076ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Login feature	59	1	2	0	0	62	7	1	8	4m 9s 091ms	Failed

Feature Report