Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.136	28 sie 2021, 05:52

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	427	2	12	0	0	441	43	2	45	51m 59s 522ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 658ms

And Go to invitation details 138ms

Then Reject invitation by button as user 352ms

When If user is login then logout 629ms

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

And Go to "INVITATIONS_TAB" 459ms

And Go to "REJECTED_TAB" invitation status tab 293ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 175ms

After Hooks.cleanUserDetailsAfterTest() 1s 289ms

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" 229ms

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

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

And Go to "INVITATIONS_TAB" 476ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 120ms

Hooks

After Hooks.deleteInvitationAfterTest() 191ms

After Hooks.cleanUserDetailsAfterTest() 1s 280ms

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

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

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

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

And Show all transport types 1s 152ms

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

And Set advice window in schedule 3s 304ms

And Fill advice form 17s 232ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 316ms

After Hooks.deleteTransportAfterTest() 780ms

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

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

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

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

And Show all transport types 1s 200ms

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

And Set advice window in schedule 3s 401ms

And Fill advice form 13s 122ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 078ms

After Hooks.deleteTransportAfterTest() 792ms

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

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

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

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

And Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 242ms

And Fill advice form 18s 773ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 503ms

After Hooks.deleteTransportAfterTest() 718ms

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" 5s 004ms

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

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

And Show all transport types 1s 149ms

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

And Go to "TRANSPORT_TABLE" 316ms

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

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

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

And Fill transport form 5s 167ms

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

And Expand advice panel 264ms

And Edit advice in transport details 17s 600ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 269ms

After Hooks.deleteTransportAfterTest() 745ms

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 "piast-admin" and set token of apiUsername "super-admin-piast" 5s 441ms

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

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

And Show all transport types 1s 145ms

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

And Go to "TRANSPORT_TABLE" 359ms

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

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

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

And Fill transport form 1m 8s 730ms

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

And Expand advice panel 264ms

And Edit advice in transport details 8s 126ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 181ms

After Hooks.deleteTransportAfterTest() 891ms

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

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

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

And Show all transport types 1s 179ms

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

And Go to "TRANSPORT_TABLE" 400ms

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

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

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

And Fill transport form 28s 637ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 713ms

After Hooks.deleteTransportAfterTest() 777ms

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" 227ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 079ms

After Hooks.deleteTransportAfterTest() 781ms

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" 223ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 674ms

After Hooks.deleteTransportAfterTest() 757ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 430ms

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" 4s 817ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 068ms

After Hooks.deleteTransportAfterTest() 703ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 070ms

After Hooks.deleteTransportAfterTest() 598ms

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

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

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

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

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

And Wait till auction end 1m 56s 018ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 455ms

After Hooks.deleteTransportAfterTest() 697ms

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 450ms

After Hooks.deleteTransportAfterTest() 625ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 155ms

After Hooks.deleteTransportAfterTest() 586ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 306ms

After Hooks.deleteTransportAfterTest() 554ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 089ms

After Hooks.deleteTransportAfterTest() 592ms

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

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

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

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 2s 444ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 084ms

After Hooks.deleteTransportAfterTest() 734ms

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

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

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

And Go to "TRANSPORT_TABLE" 423ms

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

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

And Fill transport form 1s 292ms

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/temp/buildTmp/.com.google.Chrome.Pk7BjE}, 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: 68d6d501b2436a36dd1c7b14acb175a3
	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 067ms

After Hooks.deleteTransportAfterTest() 838ms

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" 267ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 578ms

After Hooks.deleteModeOfTransportationAfterTest() 392ms

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" 239ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 604ms

After Hooks.deleteModeOfTransportationAfterTest() 319ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 330ms

And Select warehouse "Serownia" 1s 545ms

And Set week view 1s 222ms

And Show yesterday 1s 140ms

And Move window into the past 446ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 2s 569ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 691ms

After Hooks.deleteTransportAfterTest() 794ms

After Hooks.rollbackAddedAuthorities() 195ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 153ms

After Hooks.deleteTransportAfterTest() 617ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 207ms

After Hooks.deleteTransportAfterTest() 583ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 058ms

After Hooks.deleteTransportAfterTest() 772ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 122ms

After Hooks.deleteTransportAfterTest() 583ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then If user is login then logout 252ms

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

And Go to auction details 2s 315ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 735ms

After Hooks.deleteTransportAfterTest() 831ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 805ms

After Hooks.deleteTransportAfterTest() 749ms

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" 230ms

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 337ms

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" 2s 651ms

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

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

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

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

And Set advice window in schedule 3s 453ms

And Fill advice form 20s 296ms

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

And Go to "TRANSPORT_TABLE" 464ms

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

Then Check are advice values equals 5s 025ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 299ms

After Hooks.deleteTransportAfterTest() 823ms

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" 7s 795ms

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

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

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

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

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

And Set advice window in schedule 3s 342ms

And Fill advice form 20s 352ms

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

And Go to "TRANSPORT_TABLE" 446ms

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

Then Check are advice values equals 4s 980ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 122ms

After Hooks.deleteTransportAfterTest() 799ms

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

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

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

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 4s 328ms

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

And Set advice window in schedule 3s 331ms

And Fill advice form 20s 458ms

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

And Go to "TRANSPORT_TABLE" 490ms

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

Then Check are advice values equals 4s 915ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 374ms

After Hooks.deleteTransportAfterTest() 790ms

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

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

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

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

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

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

And Set advice window in schedule 3s 400ms

And Fill advice form 20s 397ms

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

And Go to "TRANSPORT_TABLE" 499ms

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

Then Check are advice values equals 5s 022ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 728ms

After Hooks.deleteTransportAfterTest() 798ms

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

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

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

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

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

And Set advice window in schedule 30s 112ms

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/temp/buildTmp/.com.google.Chrome.Pk7BjE}, 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: 68d6d501b2436a36dd1c7b14acb175a3
*** 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 829ms

After Hooks.deleteTransportAfterTest() 559ms

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

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

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

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

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

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

And Set advice window in schedule 3s 368ms

And Fill advice form 20s 438ms

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

And Go to "TRANSPORT_TABLE" 447ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 120ms

After Hooks.deleteTransportAfterTest() 781ms

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

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

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

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 "CONTAINER" created in transport table and set transport id 3s 903ms

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

And Set advice window in schedule 3s 401ms

And Fill advice form 20s 455ms

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

And Go to "TRANSPORT_TABLE" 452ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 196ms

After Hooks.deleteTransportAfterTest() 733ms

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

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

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

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

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

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

And Set advice window in schedule 3s 390ms

And Fill advice form 20s 482ms

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

And Go to "TRANSPORT_TABLE" 530ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 145ms

After Hooks.deleteTransportAfterTest() 809ms

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

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

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 "TRANSPORT_ORDER" created in transport table and set transport id 3s 786ms

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

And Set advice window in schedule 3s 380ms

And Fill advice form 20s 429ms

And Click advice save button and wait for advice form to disappear 18s 329ms

And Go to "TRANSPORT_TABLE" 469ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 046ms

After Hooks.deleteTransportAfterTest() 866ms

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

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

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

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 559ms

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

And Set advice window in schedule 3s 460ms

And Fill advice form 20s 456ms

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

And Go to "TRANSPORT_TABLE" 443ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 684ms

After Hooks.deleteTransportAfterTest() 824ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 223ms

And Check if reject date is visible 973ms

Then If user is login then logout 285ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 259ms

After Hooks.deleteTransportAfterTest() 754ms

After Hooks.rollbackWarehousesAccess() 742ms

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" 228ms

And Prepare login page 462ms

And Click remind password button 282ms

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

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

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

And Extract password from mailgun mail 3s 910ms

And Reset password from link 1s 554ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 956ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

Then Save user details 1s 036ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 717ms

After Hooks.rollbackAddedAuthorities() 253ms

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" 242ms

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

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

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

And Expand "other" notification section 2s 493ms

And Select all notifications in "other" section 287ms

Then Save user details 1s 456ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 051ms

After Hooks.rollbackAddedAuthorities() 161ms

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" 229ms

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

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

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

And Go to "USERS_TAB" 1s 531ms

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

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

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

Then Save user details 1s 043ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 659ms

After Hooks.rollbackAddedAuthorities() 247ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 589ms

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

And Expand "GLUE_FACTORY" notification section 558ms

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

Then Save user details 1s 780ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 041ms

After Hooks.rollbackAddedAuthorities() 216ms

	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	51m 59s 522ms	Failed

Tag Report