Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.65	18 sie 2021, 03:49

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	379	6	53	0	0	438	39	6	45	36m 20s 987ms	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" 095ms

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

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

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

When Login as "piast-admin" 1s 406ms

Then Go to "INVITATIONS_TAB" 191ms

And Go to invitation details 065ms

Then Reject invitation by button as user 119ms

When If user is login then logout 289ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 1s 399ms

And Go to "INVITATIONS_TAB" 178ms

And Go to "REJECTED_TAB" invitation status tab 092ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 022ms

After Hooks.cleanUserDetailsAfterTest() 172ms

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

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

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 975ms

And Go to "INVITATIONS_TAB" 180ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 038ms

Hooks

After Hooks.deleteInvitationAfterTest() 037ms

After Hooks.cleanUserDetailsAfterTest() 221ms

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

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

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

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

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.getJSON(JsonApiUtil.java:145)
	at Utils.JsonApiUtil.getFormJson(JsonApiUtil.java:121)
	at CucumberTests.GetInputsStep.getInputsFromJSONFile(GetInputsStep.java:43)
	at CucumberTests.GetInputsStep.setInputsFromJSONFile(GetInputsStep.java:37)
	at ✽.Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama"(file:Features/Atom/Mail/AdviceMail.feature:8)

And Show all transport types 000ms

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

And Set advice window in schedule 000ms

And Fill advice form 000ms

And Click advice save button and wait for advice form to disappear 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.cleanUserDetailsAfterTest() 171ms

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

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

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 625ms

And Fill advice form 10s 582ms

And Click advice save button and wait for advice form to disappear 30s 733ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

After Hooks.cleanUserDetailsAfterTest() 163ms

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

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

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 477ms

And Fill advice form 15s 401ms

And Click advice save button and wait for advice form to disappear 30s 718ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 215ms

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

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

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

And Show all transport types 1s 038ms

And Create advice by JSON file "ADVICE_CONTAINER" as "super-admin-adama" 001ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.getJSON(JsonApiUtil.java:145)
	at Utils.JsonApiUtil.getTransportApiJson(JsonApiUtil.java:131)
	at CucumberTests.Transport.AdviceTransport.prepareAdviceJSON(AdviceTransport.java:371)
	at CucumberTests.Transport.AdviceTransport.createAdviceByJSONFile(AdviceTransport.java:343)
	at ✽.Create advice by JSON file "ADVICE_CONTAINER" as "super-admin-adama"(file:Features/Atom/Mail/AdviceMail.feature:28)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "CONTAINER" 000ms

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

When Go to transport details "CONTAINER" 000ms

And Fill transport form 000ms

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

And Expand advice panel 000ms

And Edit advice in transport details 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

After Hooks.cleanUserDetailsAfterTest() 181ms

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

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

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

And Show all transport types 1s 043ms

And Create advice by JSON file "ADVICE_DELIVERY" as "super-admin-piast" 000ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.getJSON(JsonApiUtil.java:145)
	at Utils.JsonApiUtil.getTransportApiJson(JsonApiUtil.java:131)
	at CucumberTests.Transport.AdviceTransport.prepareAdviceJSON(AdviceTransport.java:371)
	at CucumberTests.Transport.AdviceTransport.createAdviceByJSONFile(AdviceTransport.java:343)
	at ✽.Create advice by JSON file "ADVICE_DELIVERY" as "super-admin-piast"(file:Features/Atom/Mail/AdviceMail.feature:28)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

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

When Go to transport details "DELIVERY" 000ms

And Fill transport form 000ms

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

And Expand advice panel 000ms

And Edit advice in transport details 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

After Hooks.cleanUserDetailsAfterTest() 147ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 465ms

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

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

And Show all transport types 1s 046ms

And Create advice by JSON file "ADVICE_LOAD" as "super-admin-keeeper" 001ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.getJSON(JsonApiUtil.java:145)
	at Utils.JsonApiUtil.getTransportApiJson(JsonApiUtil.java:131)
	at CucumberTests.Transport.AdviceTransport.prepareAdviceJSON(AdviceTransport.java:371)
	at CucumberTests.Transport.AdviceTransport.createAdviceByJSONFile(AdviceTransport.java:343)
	at ✽.Create advice by JSON file "ADVICE_LOAD" as "super-admin-keeeper"(file:Features/Atom/Mail/AdviceMail.feature:28)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "LOAD" 000ms

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

When Go to transport details "LOAD" 000ms

And Fill transport form 000ms

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

And Expand advice panel 000ms

And Edit advice in transport details 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.cleanUserDetailsAfterTest() 205ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 255ms

And Confirm status "ARRIVAL" by Public API "v1" 285ms

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

Then Check if user got a mail 000ms

And Confirm status "DEPARTURE" by Public API "v1" 232ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

After Hooks.cleanUserDetailsAfterTest() 165ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.cleanUserDetailsAfterTest() 247ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 137ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 229ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 275ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 236ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.cleanUserDetailsAfterTest() 284ms

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

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 251ms

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

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

And Wait till auction end 1m 58s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

After Hooks.cleanUserDetailsAfterTest() 337ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 246ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 219ms

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

And Wait till auction end 1m 58s 018ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.cleanUserDetailsAfterTest() 199ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 519ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 250ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 273ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 242ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 2m 13s 121ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.cleanUserDetailsAfterTest() 248ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 222ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 268ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 238ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 286ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 431ms

And Go to "TRANSPORT_TABLE" 126ms

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

And Set "advice" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.getJSON(JsonApiUtil.java:145)
	at Utils.JsonApiUtil.getFormJson(JsonApiUtil.java:121)
	at CucumberTests.GetInputsStep.getInputsFromJSONFile(GetInputsStep.java:43)
	at CucumberTests.GetInputsStep.setInputsFromJSONFile(GetInputsStep.java:37)
	at ✽.Set "advice" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland"(file:Features/Atom/Mail/DiscrepancyReportMail.feature:10)

And Fill transport form 000ms

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.deleteTransportAfterTest() 096ms

After Hooks.cleanUserDetailsAfterTest() 406ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 307ms

After Hooks.deleteModeOfTransportationAfterTest() 103ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 304ms

After Hooks.deleteModeOfTransportationAfterTest() 063ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 320ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 382ms

And Go to "WAREHOUSE_TAB" 833ms

And Select warehouse "Serownia" 1s 384ms

And Set week view 1s 101ms

And Show yesterday 1s 068ms

And Move window into the past 308ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 318ms

After Hooks.rollbackAddedAuthorities() 023ms

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

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

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 258ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 301ms

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

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

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 308ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.cleanUserDetailsAfterTest() 287ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 248ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.cleanUserDetailsAfterTest() 273ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 223ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

After Hooks.cleanUserDetailsAfterTest() 258ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 240ms

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

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

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

Then If user is login then logout 5s 338ms

And Login as "swisskrono-admin" 1s 050ms

And Go to auction details 1s 220ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.cleanUserDetailsAfterTest() 360ms

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

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 248ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 377ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 165ms

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

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

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

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

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

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

And Set advice window in schedule 2s 527ms

And Fill advice form 16s 851ms

And Click advice save button and wait for advice form to disappear 30s 691ms

And Go to "TRANSPORT_TABLE" 164ms

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

Then Check are advice values equals 4s 363ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.cleanUserDetailsAfterTest() 314ms

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

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

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

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

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 3s 363ms

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

And Set advice window in schedule 2s 565ms

And Fill advice form 16s 822ms

And Click advice save button and wait for advice form to disappear 30s 710ms

And Go to "TRANSPORT_TABLE" 184ms

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

Then Check are advice values equals 4s 344ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 313ms

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

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

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

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

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 5s 888ms

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

And Set advice window in schedule 2s 596ms

And Fill advice form 16s 853ms

And Click advice save button and wait for advice form to disappear 30s 727ms

And Go to "TRANSPORT_TABLE" 220ms

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

Then Check are advice values equals 4s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.cleanUserDetailsAfterTest() 286ms

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

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

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

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 5s 852ms

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

And Set advice window in schedule 2s 556ms

And Fill advice form 16s 845ms

And Click advice save button and wait for advice form to disappear 30s 729ms

And Go to "TRANSPORT_TABLE" 207ms

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

Then Check are advice values equals 4s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.cleanUserDetailsAfterTest() 371ms

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

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

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

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 3s 811ms

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

And Set advice window in schedule 30s 066ms

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', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.0n5WCa}, 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: e0fe6b375f8b6306e0f6dec2e4f8854d
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source)
	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:323)
	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.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 238ms

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

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

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

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 3s 361ms

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

And Set advice window in schedule 2s 562ms

And Fill advice form 16s 755ms

And Click advice save button and wait for advice form to disappear 30s 708ms

And Go to "TRANSPORT_TABLE" 190ms

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

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 278ms

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

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

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

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

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

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

And Set advice window in schedule 2s 568ms

And Fill advice form 16s 770ms

And Click advice save button and wait for advice form to disappear 30s 743ms

And Go to "TRANSPORT_TABLE" 193ms

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

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.cleanUserDetailsAfterTest() 274ms

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

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

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

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

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

And Set advice window in schedule 2s 582ms

And Fill advice form 16s 780ms

And Click advice save button and wait for advice form to disappear 30s 714ms

And Go to "TRANSPORT_TABLE" 244ms

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.cleanUserDetailsAfterTest() 273ms

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

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

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

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 5s 914ms

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

And Set advice window in schedule 2s 581ms

And Fill advice form 16s 882ms

And Click advice save button and wait for advice form to disappear 30s 698ms

And Go to "TRANSPORT_TABLE" 233ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 331ms

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

Steps

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

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

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

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 3s 011ms

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

And Set advice window in schedule 2s 553ms

And Fill advice form 16s 795ms

And Click advice save button and wait for advice form to disappear 30s 748ms

And Go to "TRANSPORT_TABLE" 215ms

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 217ms

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

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

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

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

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 309ms

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

When Reject status: Book of disinfection 085ms

And Check if reject date is visible 306ms

Then If user is login then logout 081ms

And Login as "lantmannen-admin" 1s 069ms

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

After Hooks.cleanUserDetailsAfterTest() 187ms

After Hooks.rollbackWarehousesAccess() 110ms

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

And Prepare login page 202ms

And Click remind password button 090ms

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

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

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

And Extract password from mailgun mail 4s 042ms

And Reset password from link 784ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 156ms

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

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

When Login as "oaa1-receiver-2@qa.qa-test" 1s 256ms

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

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

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

Then Save user details 242ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 091ms

After Hooks.rollbackAddedAuthorities() 036ms

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

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

When Login as "pskza1-carrier-2@qa.qa-test" 1s 786ms

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

And Expand "other" notification section 427ms

And Select all notifications in "other" section 104ms

Then Save user details 375ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 142ms

After Hooks.rollbackAddedAuthorities() 022ms

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

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

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

When Login as "adama-buyer@qa.qa-test" 1s 424ms

And Go to "USERS_TAB" 899ms

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

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

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

Then Save user details 235ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 098ms

After Hooks.rollbackAddedAuthorities() 038ms

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

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

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

When Login as "swisskrono-tradesman@qa.qa-test" 1s 893ms

And Go to "USERS_TAB" 780ms

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

And Expand "GLUE_FACTORY" notification section 222ms

And Select all notifications in "GLUE_FACTORY" section 527ms

Then Save user details 511ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 144ms

After Hooks.rollbackAddedAuthorities() 030ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	379	6	53	0	0	438	39	6	45	36m 20s 987ms	Failed

Tag Report