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

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@cleanUserDetailsAfterTest 370 6 39 0 0 415 36 6 42 41m 39s 010ms Failed
View Feature Invitation
Scenario Outline Check if user has accepted invitation from principal after accepting invitation by another user from company
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Set token of apiUsername "super-admin-farmacol" 093ms
And Prepare user "dnfa1-supplier" details with all notifications and "automaty314153@test.pl" by JSON file 366ms
And Create invitation by JSON file "super-admin-farmacol" for "automaty314153@test.pl" "CREATE_SUPPLIER_INVITATION" 521ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Użytkownik o podanym adresie e-mail już istnieje. Prosimy o kontakt z naszą obsługą klienta na support@support.xd.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:64)
	at ✽.Create invitation by JSON file "super-admin-farmacol" for "automaty314153@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:86)
And Prepare user "dnfa1-supplier-2" details with all notifications and "automaty214152@test.pl" by JSON file 000ms
And Create invitation by JSON file "super-admin-farmacol" for "automaty214152@test.pl" "CREATE_SUPPLIER_INVITATION" 000ms
When Login as "dnfa1-supplier" and set token of apiUsername "super-admin-farmacol" 000ms
And Go to "INVITATIONS_TAB" 000ms
And Accept invitation 000ms
And If user is login then logout 000ms
And Login as "dnfa1-supplier-2" and set token of apiUsername "super-admin-farmacol" 000ms
And Verify if user has visible "no waiting" invitation 000ms
And Verify if user has visible "accepted" invitation 000ms
And Verify if user can see "Farmacol" on principal switch dropdown 000ms
After Hooks.cleanUserDetailsAfterTest() 188ms
View Feature Invitation
Scenario Outline Check if rejected invitation is visible in rejected tab
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Set token of apiUsername "super-admin-piast" 095ms
And Delete invitations with email "automaty31415@test.pl" 003ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 137ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 122ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Piast Cargo Transport Sp. z o.o., NIP: . Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:64)
	at ✽.Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:175)
When Login as "piast-admin" 000ms
Then Go to "INVITATIONS_TAB" 000ms
And Go to invitation details 000ms
Then Reject invitation by button as user 000ms
When If user is login then logout 000ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 000ms
And Go to "INVITATIONS_TAB" 000ms
And Go to "REJECTED_TAB" invitation status tab 000ms
Then Invitation is displayed on list "automaty31415@test.pl" 000ms
Hooks
After Hooks.deleteInvitationAfterTest() 000ms
java.lang.NullPointerException
	at CucumberTests.Hooks.deleteInvitationAfterTest(Hooks.java:260)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
After Hooks.cleanUserDetailsAfterTest() 179ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 093ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 225ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 911ms
And Go to "INVITATIONS_TAB" 176ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 1s 093ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 065ms
After Hooks.deleteInvitationAfterTest() 004ms
After Hooks.cleanUserDetailsAfterTest() 209ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 926ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 159ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 210ms
And Get inputs from database "ADVICE_CONTAINER" "super-admin-adama" 039ms
And Show all transport types 1s 042ms
And Click button advice in transport table "CONTAINER" 101ms
And Set advice window in schedule 2s 432ms
And Fill advice form 11s 722ms
And Click advice save button and wait for advice form to disappear 30s 679ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 6s 048ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 123ms
After Hooks.cleanUserDetailsAfterTest() 162ms
View Feature Advice Mail
Scenario Outline Check if mail was sent to creator after creating advice
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 135ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 146ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 221ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 037ms
And Show all transport types 1s 048ms
And Click button advice in transport table "DELIVERY" 096ms
And Set advice window in schedule 2s 549ms
And Fill advice form 8s 262ms
And Click advice save button and wait for advice form to disappear 10s 174ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-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-2/temp/buildTmp/.com.google.Chrome.cSb5NE}, 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.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e30dd61510ae17f029911546e08e7d68
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:174)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Mail/AdviceMail.feature:13)
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 000ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 066ms
After Hooks.cleanUserDetailsAfterTest() 156ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 101ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 237ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 210ms
And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 037ms
And Show all transport types 1s 039ms
And Click button advice in transport table "LOAD" 092ms
And Set advice window in schedule 2s 426ms
And Fill advice form 13s 117ms
And Click advice save button and wait for advice form to disappear 30s 669ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 486ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 116ms
After Hooks.cleanUserDetailsAfterTest() 236ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 691ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 217ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 212ms
And Show all transport types 1s 045ms
And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 44s 913ms
And Go to "TRANSPORT_TABLE" 198ms
And Go to transport details "CONTAINER" 2s 413ms
And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 037ms
When Go to transport details "CONTAINER" 3s 185ms
And Fill transport form 4s 723ms
And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 036ms
And Expand advice panel 119ms
And Edit advice in transport details 12s 273ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 082ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 530ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 100ms
After Hooks.cleanUserDetailsAfterTest() 181ms
View Feature Advice Mail
Scenario Outline Check if mail was sent to creator after editing advice
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 670ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 173ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 215ms
And Show all transport types 1s 044ms
And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 21s 054ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-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-2/temp/buildTmp/.com.google.Chrome.cSb5NE}, 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.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e30dd61510ae17f029911546e08e7d68
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:174)
	at CucumberTests.Transport.AdviceTransport.createAdvice(AdviceTransport.java:68)
	at ✽.Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast"(file:Features/Atom/Mail/AdviceMail.feature:28)
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "DELIVERY" 000ms
And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 000ms
When Go to transport details "DELIVERY" 000ms
And Fill transport form 000ms
And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 000ms
And Expand advice panel 000ms
And Edit advice in transport details 000ms
And Click "save-transport-and-close" save button and wait for form to disappear 000ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 000ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 073ms
After Hooks.cleanUserDetailsAfterTest() 166ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 637ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 244ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 210ms
And Show all transport types 1s 043ms
And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 348ms
And Go to "TRANSPORT_TABLE" 192ms
And Go to transport details "LOAD" 2s 384ms
And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 036ms
When Go to transport details "LOAD" 3s 172ms
And Fill transport form 25s 924ms
And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 038ms
And Expand advice panel 098ms
And Edit advice in transport details 18s 470ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 098ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 488ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 105ms
After Hooks.cleanUserDetailsAfterTest() 221ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 093ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 147ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 329ms
And Confirm status "ARRIVAL" by Public API "v1" 285ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 5s 260ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 224ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 36s 521ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 143ms
After Hooks.cleanUserDetailsAfterTest() 140ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-hochland" 098ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 007ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 163ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 2s 334ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 15s 338ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 49s 345ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 123ms
After Hooks.cleanUserDetailsAfterTest() 246ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 010ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 602ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 232ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 246ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 512ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 10s 397ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 128ms
After Hooks.cleanUserDetailsAfterTest() 276ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 013ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 311ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 223ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 141ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 455ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 400ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 5s 199ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 074ms
After Hooks.cleanUserDetailsAfterTest() 260ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 2s 573ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 395ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 267ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 119ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 182ms
And Wait till auction end 1m 58s 019ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 47s 999ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 094ms
After Hooks.cleanUserDetailsAfterTest() 318ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 089ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 214ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 242ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 137ms
And Wait till auction end 1m 58s 019ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 15s 880ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 193ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 582ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 326ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 243ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 115ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 186ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 302ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 15s 678ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 101ms
After Hooks.cleanUserDetailsAfterTest() 276ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 079ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 319ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 243ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 140ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 180ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 34s 952ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 088ms
After Hooks.cleanUserDetailsAfterTest() 302ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 090ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 328ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 228ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 127ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 291ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 193ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 078ms
After Hooks.cleanUserDetailsAfterTest() 267ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 635ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 311ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 248ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 2s 170ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 20s 711ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 108ms
After Hooks.cleanUserDetailsAfterTest() 258ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 352ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 630ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 435ms
And Go to "TRANSPORT_TABLE" 128ms
And Go to transport details "DELIVERY" 2s 677ms
And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 038ms
And Fill transport form 35s 609ms
And Open section: "discrepancy-report-panel" 1s 077ms
And Fill discrepancy report section 49s 516ms
And Go to transport details "DELIVERY" 2s 456ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 280ms
And Generate discrepancy report 18s 256ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 475ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 129ms
After Hooks.cleanUserDetailsAfterTest() 413ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-bausch" 094ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 379ms
When Create default mode of transportation by API with "pba1-carrier" 141ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 074ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 5s 193ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 298ms
After Hooks.deleteModeOfTransportationAfterTest() 072ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 093ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 367ms
When Create default mode of transportation by API with "pba1-carrier" 086ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 190ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 320ms
After Hooks.deleteModeOfTransportationAfterTest() 057ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 283ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 367ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 035ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 390ms
And Go to "WAREHOUSE_TAB" 725ms
And Select warehouse "Serownia" 1s 366ms
And Set week view 1s 099ms
And Show yesterday 1s 067ms
And Move window into the past 289ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 8s 961ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 139ms
After Hooks.cleanUserDetailsAfterTest() 324ms
After Hooks.rollbackAddedAuthorities() 023ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 143ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 349ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 286ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 52s 228ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 089ms
After Hooks.cleanUserDetailsAfterTest() 297ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 852ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 324ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 282ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 52s 506ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 087ms
After Hooks.cleanUserDetailsAfterTest() 306ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 092ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 319ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 211ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 177ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 197ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 090ms
After Hooks.cleanUserDetailsAfterTest() 239ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 069ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 323ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 227ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 181ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 190ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 076ms
After Hooks.cleanUserDetailsAfterTest() 258ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 864ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 442ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 230ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 145ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 194ms
And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test" 293ms
Then If user is login then logout 251ms
And Login as "swisskrono-admin" 952ms
And Go to auction details 1s 208ms
And Pass transport to carrier from auction details 1s 253ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 2m 57s 686ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 184ms
After Hooks.cleanUserDetailsAfterTest() 353ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 238ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 460ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 231ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 117ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 10s 504ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 079ms
After Hooks.cleanUserDetailsAfterTest() 364ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 093ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 225ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 032ms
After Hooks.cleanUserDetailsAfterTest() 191ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 051ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 390ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 312ms
When Click button advice in transport table "CONTAINER" 092ms
And Set advice window in schedule 2s 527ms
And Fill advice form 14s 462ms
And Click advice save button and wait for advice form to disappear 30s 703ms
And Go to "TRANSPORT_TABLE" 186ms
And Go to transport details "CONTAINER" 2s 451ms
Then Check are advice values equals 2s 288ms
After Hooks.deleteTransportAfterTest() 107ms
After Hooks.cleanUserDetailsAfterTest() 272ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 907ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 318ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 371ms
When Click button advice in transport table "OWN_COLLECTION" 100ms
And Set advice window in schedule 2s 494ms
And Fill advice form 14s 448ms
And Click advice save button and wait for advice form to disappear 30s 741ms
And Go to "TRANSPORT_TABLE" 171ms
And Go to transport details "OWN_COLLECTION" 2s 425ms
Then Check are advice values equals 2s 288ms
After Hooks.deleteTransportAfterTest() 137ms
After Hooks.cleanUserDetailsAfterTest() 331ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 890ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 307ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 855ms
When Click button advice in transport table "TRANSPORT_ORDER" 094ms
And Set advice window in schedule 2s 526ms
And Fill advice form 14s 475ms
And Click advice save button and wait for advice form to disappear 30s 735ms
And Go to "TRANSPORT_TABLE" 233ms
And Go to transport details "TRANSPORT_ORDER" 2s 470ms
Then Check are advice values equals 2s 288ms
After Hooks.deleteTransportAfterTest() 091ms
After Hooks.cleanUserDetailsAfterTest() 280ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 973ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 480ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 822ms
When Click button advice in transport table "TRANSPORT_ORDER" 083ms
And Set advice window in schedule 2s 513ms
And Fill advice form 14s 495ms
And Click advice save button and wait for advice form to disappear 30s 718ms
And Go to "TRANSPORT_TABLE" 215ms
And Go to transport details "TRANSPORT_ORDER" 2s 424ms
Then Check are advice values equals 2s 297ms
After Hooks.deleteTransportAfterTest() 103ms
After Hooks.cleanUserDetailsAfterTest() 330ms
View Feature SK Api - Advice transport
Scenario Outline Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 773ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 253ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 035ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 921ms
When Click button advice in transport table "TRANSPORT_ORDER" 085ms
And Set advice window in schedule 30s 549ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //div[contains(@class, 'success-alert')] (tried for 30 second(s) with 500 MILLISECONDS interval)
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:177)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //div[contains(@class, 'success-alert')]
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:177)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
	at sun.reflect.GeneratedMethodAccessor239.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
And Fill advice form 000ms
And Click advice save button and wait for advice form to disappear 000ms
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "TRANSPORT_ORDER" 000ms
Then Check are advice values equals 000ms
After Hooks.deleteTransportAfterTest() 076ms
After Hooks.cleanUserDetailsAfterTest() 251ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 777ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 353ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 381ms
When Click button advice in transport table "OWN_COLLECTION" 089ms
And Set advice window in schedule 2s 533ms
And Fill advice form 14s 465ms
And Click advice save button and wait for advice form to disappear 30s 706ms
And Go to "TRANSPORT_TABLE" 183ms
Then Check advice data in SK API database "OWN_COLLECTION" 161ms
After Hooks.deleteTransportAfterTest() 118ms
After Hooks.cleanUserDetailsAfterTest() 285ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 991ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 306ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 313ms
When Click button advice in transport table "CONTAINER" 089ms
And Set advice window in schedule 2s 535ms
And Fill advice form 14s 429ms
And Click advice save button and wait for advice form to disappear 30s 691ms
And Go to "TRANSPORT_TABLE" 184ms
Then Check advice data in SK API database "CONTAINER" 086ms
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 272ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 774ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 349ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 001ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 815ms
When Click button advice in transport table "TRANSPORT_ORDER" 080ms
And Set advice window in schedule 2s 534ms
And Fill advice form 14s 443ms
And Click advice save button and wait for advice form to disappear 30s 750ms
And Go to "TRANSPORT_TABLE" 209ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 031ms
After Hooks.deleteTransportAfterTest() 112ms
After Hooks.cleanUserDetailsAfterTest() 309ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 758ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 476ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 846ms
When Click button advice in transport table "TRANSPORT_ORDER" 088ms
And Set advice window in schedule 2s 536ms
And Fill advice form 14s 436ms
And Click advice save button and wait for advice form to disappear 30s 764ms
And Go to "TRANSPORT_TABLE" 226ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 038ms
After Hooks.deleteTransportAfterTest() 121ms
After Hooks.cleanUserDetailsAfterTest() 352ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 047ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 253ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 815ms
When Click button advice in transport table "TRANSPORT_ORDER" 087ms
And Set advice window in schedule 2s 511ms
And Fill advice form 14s 484ms
And Click advice save button and wait for advice form to disappear 30s 737ms
And Go to "TRANSPORT_TABLE" 172ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 085ms
After Hooks.deleteTransportAfterTest() 128ms
After Hooks.cleanUserDetailsAfterTest() 235ms
View Feature Status rejection
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 484ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 210ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 183ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 125ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 216ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 276ms
And Check if reject date is not visible 15s 052ms
When Reject status: Book of disinfection 082ms
And Check if reject date is visible 315ms
Then If user is login then logout 086ms
And Login as "lantmannen-admin" 1s 019ms
And Check if note was added to transport after status rejection 1s 253ms
And Check if history note was added to transport after status rejection - "LOAD" 3s 539ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 9s 299ms
And Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 093ms
After Hooks.cleanUserDetailsAfterTest() 174ms
After Hooks.rollbackWarehousesAccess() 118ms
View Feature UserAuthority
Scenario Outline Permission - Edit user main data [A-7965]
Before Hooks.showScenarioName(Scenario) 000ms
Steps
Given Set token of apiUsername "super-admin-adama" 091ms
And Set basic authorities "ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 049ms
When Login as "oaa1-receiver-2@qa.qa-test" 1s 137ms
And Go to user "oaa1-receiver@qa.qa-test" details edition 110ms
And Change user details "email" to "newEmailAddress@newEmail.com" 15s 021ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to be clickable: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementClickable(BasePage.java:223)
	at CucumberTests.User.EditUserTest.changeUserEmailAddressByAccountDetails(EditUserTest.java:189)
	at ✽.Change user details "email" to "newEmailAddress@newEmail.com"(file:Features/Atom/Users/UserAuthority.feature:9)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //button[@data-button-name='save']
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.ExpectedConditions$22.apply(ExpectedConditions.java:643)
	at org.openqa.selenium.support.ui.ExpectedConditions$22.apply(ExpectedConditions.java:640)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.waitUntilElementClickable(BasePage.java:223)
	at CucumberTests.User.EditUserTest.changeUserEmailAddressByAccountDetails(EditUserTest.java:189)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
And Change user details "phone" to "123456789" 000ms
Then Save user details 000ms
Hooks
After Hooks.cleanUserDetailsAfterTest() 000ms
java.lang.NullPointerException
	at Utils.JsonApiUtil.editJsonTextNode(JsonApiUtil.java:158)
	at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:332)
	at sun.reflect.GeneratedMethodAccessor261.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
After Hooks.rollbackAddedAuthorities() 054ms