Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.139	31 sie 2021, 05:52

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	427	2	12	0	0	441	43	2	45	53m 3s 341ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-piast" 219ms

And Delete invitations with email "automaty31415@test.pl" 098ms

Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 411ms

And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 378ms

When Login as "piast-admin" 5s 176ms

Then Go to "INVITATIONS_TAB" 729ms

And Go to invitation details 144ms

Then Reject invitation by button as user 311ms

When If user is login then logout 5s 681ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 970ms

And Go to "INVITATIONS_TAB" 450ms

And Go to "REJECTED_TAB" invitation status tab 340ms

Then Invitation is displayed on list "automaty31415@test.pl" 453ms

Hooks

After Hooks.deleteInvitationAfterTest() 165ms

After Hooks.cleanUserDetailsAfterTest() 1s 257ms

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to invite existing user in order to associate him with principal company [A-7315]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 230ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 685ms

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 458ms

And Go to "INVITATIONS_TAB" 483ms

And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 3s 037ms

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 117ms

Hooks

After Hooks.deleteInvitationAfterTest() 184ms

After Hooks.cleanUserDetailsAfterTest() 1s 308ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 304ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 080ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 221ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 001ms

And Show all transport types 1s 144ms

And Click button advice in transport table "CONTAINER" 248ms

And Set advice window in schedule 3s 263ms

And Fill advice form 17s 308ms

And Click advice save button and wait for advice form to disappear 33s 936ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 532ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 355ms

After Hooks.deleteTransportAfterTest() 764ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 636ms

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 080ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 994ms

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

And Show all transport types 1s 153ms

And Click button advice in transport table "DELIVERY" 220ms

And Set advice window in schedule 3s 453ms

And Fill advice form 13s 032ms

And Click advice save button and wait for advice form to disappear 33s 302ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 541ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 069ms

After Hooks.deleteTransportAfterTest() 809ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 711ms

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 728ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 022ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Show all transport types 1s 143ms

And Click button advice in transport table "LOAD" 226ms

And Set advice window in schedule 3s 282ms

And Fill advice form 18s 809ms

And Click advice save button and wait for advice form to disappear 33s 385ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 910ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 515ms

After Hooks.deleteTransportAfterTest() 726ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 957ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 407ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 903ms

And Show all transport types 1s 174ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 410ms

And Go to "TRANSPORT_TABLE" 432ms

And Go to transport details "CONTAINER" 3s 018ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms

When Go to transport details "CONTAINER" 3s 600ms

And Fill transport form 5s 209ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms

And Expand advice panel 247ms

And Edit advice in transport details 17s 540ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 190ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 31s 618ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 287ms

After Hooks.deleteTransportAfterTest() 770ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 416ms

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 154ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 005ms

And Show all transport types 1s 137ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 3s 515ms

And Go to "TRANSPORT_TABLE" 366ms

And Go to transport details "DELIVERY" 3s 061ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 003ms

When Go to transport details "DELIVERY" 3s 846ms

And Fill transport form 1m 8s 822ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 000ms

And Expand advice panel 246ms

And Edit advice in transport details 8s 152ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 240ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 574ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 098ms

After Hooks.deleteTransportAfterTest() 925ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 995ms

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 710ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 928ms

And Show all transport types 1s 167ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 563ms

And Go to "TRANSPORT_TABLE" 403ms

And Go to transport details "LOAD" 2s 965ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms

When Go to transport details "LOAD" 3s 600ms

And Fill transport form 28s 605ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms

And Expand advice panel 282ms

And Edit advice in transport details 23s 532ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 202ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 46s 786ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 681ms

After Hooks.deleteTransportAfterTest() 767ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after status confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 815ms

And Confirm status "REPORTING" by Public API "v1" 551ms

And Confirm status "ARRIVAL" by Public API "v1" 1s 231ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 10s 679ms

Then Check if user got a mail 000ms

And Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION" 1s 076ms

And Assign Place to classification resource: "super-admin-skd" "trociny" "Rozładunek" "UNLOAD" 1s 080ms

And Confirm status "DEPARTURE" by Public API "v1" 1s 101ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 5s 338ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 938ms

After Hooks.deleteTransportAfterTest() 775ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Set token of apiUsername "super-admin-hochland" 245ms

And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 200ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 114ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 8s 971ms

And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 16s 979ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 43s 802ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 753ms

After Hooks.deleteTransportAfterTest() 724ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 451ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 096ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 239ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 225ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 624ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 247ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 081ms

After Hooks.deleteTransportAfterTest() 792ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 573ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 322ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 200ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 024ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 412ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 982ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 420ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 285ms

After Hooks.deleteTransportAfterTest() 676ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 379ms

And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 591ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 174ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 879ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 984ms

And Wait till auction end 1m 57s 015ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 48s 478ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 477ms

After Hooks.deleteTransportAfterTest() 626ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 626ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 562ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 122ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 136ms

And Wait till auction end 1m 57s 016ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 575ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 380ms

After Hooks.deleteTransportAfterTest() 598ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 075ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 355ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 096ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 001ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 067ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 854ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 36s 657ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 060ms

After Hooks.deleteTransportAfterTest() 637ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 687ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 323ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 050ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 056ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 986ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 29s 026ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 290ms

After Hooks.deleteTransportAfterTest() 581ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 568ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 405ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 096ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 013ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 765ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 232ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 952ms

After Hooks.deleteTransportAfterTest() 577ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 5s 374ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 780ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 033ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 3s 122ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 1m 3s 920ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 070ms

After Hooks.deleteTransportAfterTest() 659ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after discrepancy report generation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 164ms

And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 4s 385ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 199ms

And Go to "TRANSPORT_TABLE" 393ms

And Go to transport details "DELIVERY" 2s 938ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 1s 302ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
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=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.ueekpG}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a4d1adc2887afc648ec033dbe20815b9
	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.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:83)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:227)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:216)
	at CucumberTests.Transport.Transport.fillFields(Transport.java:172)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:150)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:184)
	at ✽.Fill transport form(file:Features/Atom/Mail/DiscrepancyReportMail.feature:11)

And Open section: "discrepancy-report-panel" 000ms

And Fill discrepancy report section 000ms

And Go to transport details "DELIVERY" 000ms

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 000ms

And Generate discrepancy report 000ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 064ms

After Hooks.deleteTransportAfterTest() 1s 011ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after updating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 233ms

And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 052ms

When Create default mode of transportation by API with "pba1-carrier" 695ms

Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 361ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 689ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 462ms

After Hooks.deleteModeOfTransportationAfterTest() 371ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after creating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 232ms

And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 868ms

When Create default mode of transportation by API with "pba1-carrier" 565ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 180ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 524ms

After Hooks.deleteModeOfTransportationAfterTest() 318ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 183ms

And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 164ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 290ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 159ms

And Go to "WAREHOUSE_TAB" 1s 301ms

And Select warehouse "Serownia" 1s 569ms

And Set week view 1s 241ms

And Show yesterday 1s 170ms

And Move window into the past 455ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 57s 357ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 578ms

After Hooks.deleteTransportAfterTest() 774ms

After Hooks.rollbackAddedAuthorities() 198ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 612ms

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 419ms

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 244ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 39s 439ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 179ms

After Hooks.deleteTransportAfterTest() 579ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 696ms

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 713ms

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 228ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 41s 925ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 199ms

After Hooks.deleteTransportAfterTest() 600ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to carrier after transport transfer

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 499ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 600ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 124ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 798ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 605ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 066ms

After Hooks.deleteTransportAfterTest() 768ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 513ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 438ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 068ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 988ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 881ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 061ms

After Hooks.deleteTransportAfterTest() 615ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 638ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 247ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 261ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 064ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 040ms

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" 1s 122ms

Then If user is login then logout 264ms

And Login as "swisskrono-admin" 2s 794ms

And Go to auction details 1s 901ms

And Pass transport to carrier from auction details 1s 598ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 31s 488ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 726ms

After Hooks.deleteTransportAfterTest() 843ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 896ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 149ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 288ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 045ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 203ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 692ms

After Hooks.deleteTransportAfterTest() 649ms

View Feature Remind password

@cleanUserDetailsAfterTest

Scenario Outline Check if remind password http status is ok

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 564ms

Then Send password remind email "automaty10@o2.pl" and check if status is ok 219ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 339ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 548ms

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 403ms

And Add transport by SKApi in "MGW" assigned to "" 025ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "CONTAINER" created in transport table and set transport id 3s 893ms

When Click button advice in transport table "CONTAINER" 222ms

And Set advice window in schedule 3s 326ms

And Fill advice form 20s 369ms

And Click advice save button and wait for advice form to disappear 33s 828ms

And Go to "TRANSPORT_TABLE" 455ms

And Go to transport details "CONTAINER" 2s 936ms

Then Check are advice values equals 4s 975ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 302ms

After Hooks.deleteTransportAfterTest() 762ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 684ms

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 387ms

And Add transport by SKApi in "MGW" assigned to "" 024ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 190ms

When Click button advice in transport table "OWN_COLLECTION" 225ms

And Set advice window in schedule 3s 362ms

And Fill advice form 20s 414ms

And Click advice save button and wait for advice form to disappear 33s 342ms

And Go to "TRANSPORT_TABLE" 468ms

And Go to transport details "OWN_COLLECTION" 2s 839ms

Then Check are advice values equals 4s 993ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 121ms

After Hooks.deleteTransportAfterTest() 816ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 431ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 378ms

And Add transport by SKApi in "MGW" assigned to "" 021ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 414ms

When Click button advice in transport table "TRANSPORT_ORDER" 218ms

And Set advice window in schedule 3s 326ms

And Fill advice form 20s 420ms

And Click advice save button and wait for advice form to disappear 33s 286ms

And Go to "TRANSPORT_TABLE" 479ms

And Go to transport details "TRANSPORT_ORDER" 2s 903ms

Then Check are advice values equals 4s 978ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 259ms

After Hooks.deleteTransportAfterTest() 820ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 673ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 437ms

And Add transport by SKApi in "MGW" assigned to "" 022ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 734ms

When Click button advice in transport table "TRANSPORT_ORDER" 208ms

And Set advice window in schedule 3s 340ms

And Fill advice form 20s 441ms

And Click advice save button and wait for advice form to disappear 33s 386ms

And Go to "TRANSPORT_TABLE" 529ms

And Go to transport details "TRANSPORT_ORDER" 2s 916ms

Then Check are advice values equals 5s 013ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 711ms

After Hooks.deleteTransportAfterTest() 845ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 543ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 743ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 024ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 563ms

When Click button advice in transport table "TRANSPORT_ORDER" 211ms

And Set advice window in schedule 30s 128ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
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-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=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.ueekpG}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a4d1adc2887afc648ec033dbe20815b9
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	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.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:82)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 748ms

After Hooks.deleteTransportAfterTest() 547ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 701ms

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 000ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 478ms

And Add transport by SKApi in "MGW" assigned to "" 018ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 131ms

When Click button advice in transport table "OWN_COLLECTION" 231ms

And Set advice window in schedule 3s 341ms

And Fill advice form 20s 372ms

And Click advice save button and wait for advice form to disappear 33s 292ms

And Go to "TRANSPORT_TABLE" 493ms

Then Check advice data in SK API database "OWN_COLLECTION" 450ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 181ms

After Hooks.deleteTransportAfterTest() 814ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 644ms

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 379ms

And Add transport by SKApi in "MGW" assigned to "" 019ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "CONTAINER" created in transport table and set transport id 6s 956ms

When Click button advice in transport table "CONTAINER" 232ms

And Set advice window in schedule 3s 396ms

And Fill advice form 20s 448ms

And Click advice save button and wait for advice form to disappear 33s 288ms

And Go to "TRANSPORT_TABLE" 445ms

Then Check advice data in SK API database "CONTAINER" 234ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 237ms

After Hooks.deleteTransportAfterTest() 924ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 605ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 460ms

And Add transport by SKApi in "MGW" assigned to "" 018ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 234ms

When Click button advice in transport table "TRANSPORT_ORDER" 228ms

And Set advice window in schedule 3s 374ms

And Fill advice form 20s 396ms

And Click advice save button and wait for advice form to disappear 33s 323ms

And Go to "TRANSPORT_TABLE" 475ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 088ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 121ms

After Hooks.deleteTransportAfterTest() 819ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 6s 459ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 227ms

And Add transport by SKApi in "MGW" assigned to "" 022ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 071ms

When Click button advice in transport table "TRANSPORT_ORDER" 222ms

And Set advice window in schedule 3s 446ms

And Fill advice form 20s 474ms

And Click advice save button and wait for advice form to disappear 33s 303ms

And Go to "TRANSPORT_TABLE" 477ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 030ms

After Hooks.deleteTransportAfterTest() 826ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 936ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 910ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 023ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 532ms

When Click button advice in transport table "TRANSPORT_ORDER" 241ms

And Set advice window in schedule 3s 496ms

And Fill advice form 20s 363ms

And Click advice save button and wait for advice form to disappear 33s 936ms

And Go to "TRANSPORT_TABLE" 453ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 267ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 729ms

After Hooks.deleteTransportAfterTest() 792ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if it is possible to reject status by guard in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 751ms

And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 009ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 476ms

And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 750ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 501ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 884ms

And Check if reject date is not visible 15s 064ms

When Reject status: Book of disinfection 234ms

And Check if reject date is visible 916ms

Then If user is login then logout 260ms

And Login as "lantmannen-admin" 2s 528ms

And Check if note was added to transport after status rejection 1s 679ms

And Check if history note was added to transport after status rejection - "LOAD" 7s 299ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 41s 624ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 280ms

After Hooks.deleteTransportAfterTest() 734ms

After Hooks.rollbackWarehousesAccess() 732ms

View Feature User

@cleanUserDetailsAfterTest @TmsLink=A-8005.1

Scenario Outline Check if it is not possible to use the previous password when editing it - remind password [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare login page 435ms

And Click remind password button 277ms

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

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

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

And Extract password from mailgun mail 4s 362ms

And Reset password from link 1s 627ms

Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 214ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 949ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

Scenario Outline Permission - Edit user main data [A-7965]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 378ms

When Login as "oaa1-receiver-2@qa.qa-test" 4s 392ms

And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 127ms

And Change user details "email" to "newEmailAddress@newEmail.com" 1s 134ms

And Change user details "phone" to "123456789" 436ms

Then Save user details 1s 008ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 159ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 644ms

After Hooks.rollbackAddedAuthorities() 260ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 245ms

And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 200ms

When Login as "pskza1-carrier-2@qa.qa-test" 7s 311ms

And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 094ms

And Expand "other" notification section 2s 444ms

And Select all notifications in "other" section 269ms

Then Save user details 1s 467ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 141ms

After Hooks.rollbackAddedAuthorities() 181ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user main data from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 453ms

And Set user details json of user "oaa1-receiver@qa.qa-test" 014ms

When Login as "adama-buyer@qa.qa-test" 5s 031ms

And Go to "USERS_TAB" 1s 452ms

And Find user "oaa1-receiver@qa.qa-test" 3s 686ms

And Change user details "email" to "newEmailAddress@newEmail.com" 822ms

And Change user details "phone" to "123456789" 424ms

Then Save user details 1s 009ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 166ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 675ms

After Hooks.rollbackAddedAuthorities() 245ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-skz" 221ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 347ms

And Set user details json of user "pskza1-carrier@qa.qa-test" 011ms

When Login as "swisskrono-tradesman@qa.qa-test" 9s 661ms

And Go to "USERS_TAB" 1s 864ms

And Find user "pskza1-carrier@qa.qa-test" 3s 655ms

And Expand "GLUE_FACTORY" notification section 632ms

And Select all notifications in "GLUE_FACTORY" section 1s 405ms

Then Save user details 1s 823ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 007ms

After Hooks.rollbackAddedAuthorities() 215ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	427	2	12	0	0	441	43	2	45	53m 3s 341ms	Failed

Tag Report