Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.124	19 sie 2021, 06:07

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	424	2	12	0	0	438	43	2	45	52m 59s 272ms	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" 229ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 692ms

And Go to invitation details 139ms

Then Reject invitation by button as user 306ms

When If user is login then logout 680ms

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

And Go to "INVITATIONS_TAB" 467ms

And Go to "REJECTED_TAB" invitation status tab 336ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 193ms

After Hooks.cleanUserDetailsAfterTest() 1s 324ms

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

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

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

And Go to "INVITATIONS_TAB" 434ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 106ms

Hooks

After Hooks.deleteInvitationAfterTest() 191ms

After Hooks.cleanUserDetailsAfterTest() 1s 325ms

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

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

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

And Get inputs from database "ADVICE_CONTAINER" "super-admin-adama" 020ms

And Show all transport types 1s 144ms

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

And Set advice window in schedule 3s 382ms

And Fill advice form 17s 249ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 279ms

After Hooks.deleteTransportAfterTest() 747ms

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

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

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

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 019ms

And Show all transport types 1s 167ms

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

And Set advice window in schedule 3s 421ms

And Fill advice form 12s 987ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 055ms

After Hooks.deleteTransportAfterTest() 769ms

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

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

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

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 020ms

And Show all transport types 1s 159ms

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

And Set advice window in schedule 3s 265ms

And Fill advice form 18s 724ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 715ms

After Hooks.deleteTransportAfterTest() 723ms

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

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

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

And Show all transport types 1s 165ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 53s 748ms

And Go to "TRANSPORT_TABLE" 448ms

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

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 019ms

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

And Fill transport form 5s 140ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 023ms

And Expand advice panel 268ms

And Edit advice in transport details 17s 522ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 403ms

After Hooks.deleteTransportAfterTest() 771ms

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

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

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

And Show all transport types 1s 167ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 49s 965ms

And Go to "TRANSPORT_TABLE" 462ms

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 023ms

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

And Fill transport form 1m 8s 829ms

And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 021ms

And Expand advice panel 264ms

And Edit advice in transport details 8s 190ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 129ms

After Hooks.deleteTransportAfterTest() 963ms

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

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

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

And Show all transport types 1s 147ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 55s 430ms

And Go to "TRANSPORT_TABLE" 447ms

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

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 019ms

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

And Fill transport form 28s 776ms

And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 023ms

And Expand advice panel 272ms

And Edit advice in transport details 23s 753ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 693ms

After Hooks.deleteTransportAfterTest() 713ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 983ms

After Hooks.deleteTransportAfterTest() 771ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 673ms

After Hooks.deleteTransportAfterTest() 748ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 422ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 078ms

After Hooks.deleteTransportAfterTest() 711ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 141ms

After Hooks.deleteTransportAfterTest() 599ms

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

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

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

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

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

And Wait till auction end 1m 57s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 492ms

After Hooks.deleteTransportAfterTest() 632ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 394ms

After Hooks.deleteTransportAfterTest() 604ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 115ms

After Hooks.deleteTransportAfterTest() 618ms

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" 3s 812ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 303ms

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

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

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" 3s 001ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 085ms

After Hooks.deleteTransportAfterTest() 589ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 36s 903ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 066ms

After Hooks.deleteTransportAfterTest() 660ms

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

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

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

And Go to "TRANSPORT_TABLE" 400ms

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 019ms

And Fill transport form 1s 344ms

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.K4IZfJ}, 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: 4ec7d232f7c159b2a5822920825b61b3
	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 127ms

After Hooks.deleteTransportAfterTest() 889ms

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) 000ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 609ms

After Hooks.deleteModeOfTransportationAfterTest() 417ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 555ms

After Hooks.deleteModeOfTransportationAfterTest() 293ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 285ms

And Select warehouse "Serownia" 1s 564ms

And Set week view 1s 228ms

And Show yesterday 1s 157ms

And Move window into the past 406ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 366ms

After Hooks.deleteTransportAfterTest() 813ms

After Hooks.rollbackAddedAuthorities() 136ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 152ms

After Hooks.deleteTransportAfterTest() 574ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 383ms

After Hooks.deleteTransportAfterTest() 584ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 181ms

After Hooks.deleteTransportAfterTest() 806ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 125ms

After Hooks.deleteTransportAfterTest() 563ms

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

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

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

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

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

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

Then If user is login then logout 262ms

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

And Go to auction details 1s 898ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 767ms

After Hooks.deleteTransportAfterTest() 841ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 746ms

After Hooks.deleteTransportAfterTest() 610ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 316ms

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

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

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms

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

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

And Set advice window in schedule 3s 357ms

And Fill advice form 20s 404ms

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

And Go to "TRANSPORT_TABLE" 449ms

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

Then Check are advice values equals 5s 001ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 268ms

After Hooks.deleteTransportAfterTest() 851ms

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" 8s 142ms

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

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 024ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 015ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 097ms

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

And Set advice window in schedule 3s 383ms

And Fill advice form 20s 570ms

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

And Go to "TRANSPORT_TABLE" 461ms

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

Then Check are advice values equals 4s 928ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 225ms

After Hooks.deleteTransportAfterTest() 785ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 025ms

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

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

And Set advice window in schedule 3s 364ms

And Fill advice form 20s 409ms

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

And Go to "TRANSPORT_TABLE" 490ms

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

Then Check are advice values equals 4s 965ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 293ms

After Hooks.deleteTransportAfterTest() 784ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 931ms

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

And Set advice window in schedule 3s 567ms

And Fill advice form 20s 529ms

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

And Go to "TRANSPORT_TABLE" 456ms

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

Then Check are advice values equals 5s 042ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 701ms

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) 000ms

Steps

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms

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

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

And Set advice window in schedule 30s 086ms

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.K4IZfJ}, 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: 4ec7d232f7c159b2a5822920825b61b3
*** 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:91)
	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 762ms

After Hooks.deleteTransportAfterTest() 552ms

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 Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 410ms

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 020ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms

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

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

And Set advice window in schedule 3s 404ms

And Fill advice form 20s 406ms

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

And Go to "TRANSPORT_TABLE" 385ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 217ms

After Hooks.deleteTransportAfterTest() 789ms

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

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

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 021ms

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

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

And Set advice window in schedule 3s 334ms

And Fill advice form 20s 497ms

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

And Go to "TRANSPORT_TABLE" 447ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 256ms

After Hooks.deleteTransportAfterTest() 753ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms

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

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

And Set advice window in schedule 3s 404ms

And Fill advice form 20s 286ms

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

And Go to "TRANSPORT_TABLE" 506ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 203ms

After Hooks.deleteTransportAfterTest() 835ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 015ms

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

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

And Set advice window in schedule 3s 505ms

And Fill advice form 20s 381ms

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

And Go to "TRANSPORT_TABLE" 531ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 975ms

After Hooks.deleteTransportAfterTest() 873ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms

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

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

And Set advice window in schedule 3s 387ms

And Fill advice form 20s 495ms

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

And Go to "TRANSPORT_TABLE" 489ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 838ms

After Hooks.deleteTransportAfterTest() 815ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 217ms

And Check if reject date is visible 1s 078ms

Then If user is login then logout 333ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 391ms

After Hooks.deleteTransportAfterTest() 831ms

After Hooks.rollbackWarehousesAccess() 754ms

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

And Prepare login page 386ms

And Click remind password button 270ms

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

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

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

And Extract password from mailgun mail 4s 439ms

And Reset password from link 1s 621ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 921ms

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

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

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

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

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

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

Then Save user details 1s 043ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 649ms

After Hooks.rollbackAddedAuthorities() 256ms

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

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

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

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

And Expand "other" notification section 2s 459ms

And Select all notifications in "other" section 290ms

Then Save user details 1s 467ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 884ms

After Hooks.rollbackAddedAuthorities() 154ms

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) 001ms

Steps

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

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

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

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

And Go to "USERS_TAB" 2s 916ms

And Find user "oaa1-receiver@qa.qa-test" 2s 673ms

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

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

Then Save user details 1s 054ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 653ms

After Hooks.rollbackAddedAuthorities() 244ms

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

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

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

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

And Go to "USERS_TAB" 1s 603ms

And Find user "pskza1-carrier@qa.qa-test" 2s 704ms

And Expand "GLUE_FACTORY" notification section 524ms

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

Then Save user details 1s 778ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 049ms

After Hooks.rollbackAddedAuthorities() 251ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	424	2	12	0	0	438	43	2	45	52m 59s 272ms	Failed

Tag Report