Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.147	06 wrz 2021, 06:13

	Steps	Scenarios	Features
@deleteTransportAfterTest	4255	9	6	0	0	4270	422	9	431	7h 4m 12s 144ms	Failed

View Feature Advice transport

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 6s 417ms

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

And Set "advice" inputs from JSON file "CREATE_ADVICE_CONTAINER" "super-admin-adama" 003ms

And Check is transport "CONTAINER" created in transport table and set transport id 1s 397ms

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

And Set advice window in schedule in the past 3s 245ms

And Fill advice form 22s 021ms

And Click advice save button to check error message 204ms

Then Check if possible advice alert is displayed 076ms

Hooks

After Hooks.deleteTransportAfterTest() 550ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Check is transport "DELIVERY" created in transport table and set transport id 1s 348ms

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

And Set advice window in schedule in the past 3s 391ms

And Fill advice form 12s 960ms

And Click advice save button to check error message 188ms

Then Check if possible advice alert is displayed 072ms

Hooks

After Hooks.deleteTransportAfterTest() 549ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 988ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-piast" 002ms

And Check is transport "LOAD" created in transport table and set transport id 1s 369ms

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

And Set advice window in schedule in the past 3s 455ms

And Fill advice form 13s 100ms

And Click advice save button to check error message 193ms

Then Check if possible advice alert is displayed 071ms

Hooks

After Hooks.deleteTransportAfterTest() 519ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 6s 758ms

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

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

And Check is transport "LOAD" created in transport table and set transport id 1s 347ms

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

And Set advice window in schedule in the past 3s 298ms

And Fill advice form 19s 031ms

And Click advice save button to check error message 198ms

Then Check if possible advice alert is displayed 067ms

Hooks

After Hooks.deleteTransportAfterTest() 566ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 2s 009ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 002ms

And Check is transport "CONTAINER" created in transport table and set transport id 1s 357ms

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

And Set advice window in schedule in the past 3s 284ms

And Fill advice form 18s 804ms

And Click advice save button to check error message 204ms

Then Check if possible advice alert is displayed 069ms

Hooks

After Hooks.deleteTransportAfterTest() 571ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport types 1s 174ms

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

And Go to "TRANSPORT_TABLE" 398ms

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

When Go to transport details "CONTAINER" 2s 899ms

And Fill transport form 5s 039ms

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

And Expand advice panel 238ms

And Edit advice in transport details 17s 327ms

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

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

And Expand advice panel 241ms

Then Check are advice values equals after edition 2s 880ms

Hooks

After Hooks.deleteTransportAfterTest() 745ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport types 1s 166ms

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

And Go to "TRANSPORT_TABLE" 395ms

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

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

And Fill transport form 1m 8s 922ms

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

And Expand advice panel 234ms

And Edit advice in transport details 7s 852ms

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

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

And Expand advice panel 349ms

Then Check are advice values equals after edition 295ms

Hooks

After Hooks.deleteTransportAfterTest() 993ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 028ms

And Show all transport types 1s 147ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-piast" 3s 213ms

And Go to "TRANSPORT_TABLE" 419ms

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

When Go to transport details "LOAD" 2s 998ms

And Fill transport form 1m 3s 062ms

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

And Expand advice panel 230ms

And Edit advice in transport details 8s 161ms

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

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

And Expand advice panel 395ms

Then Check are advice values equals after edition 334ms

Hooks

After Hooks.deleteTransportAfterTest() 719ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport types 1s 172ms

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

And Go to "TRANSPORT_TABLE" 385ms

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

When Go to transport details "LOAD" 2s 862ms

And Fill transport form 28s 663ms

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

And Expand advice panel 255ms

And Edit advice in transport details 23s 314ms

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

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

And Expand advice panel 267ms

Then Check are advice values equals after edition 9s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 813ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 956ms

And Show all transport types 1s 168ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-keeeper" 2s 689ms

And Go to "TRANSPORT_TABLE" 406ms

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

When Go to transport details "CONTAINER" 2s 890ms

And Fill transport form 28s 668ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-keeeper" 003ms

And Expand advice panel 262ms

And Edit advice in transport details 23s 423ms

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

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

And Expand advice panel 252ms

Then Check are advice values equals after edition 9s 008ms

Hooks

After Hooks.deleteTransportAfterTest() 597ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-skz" 3s 104ms

And Show all transport types 1s 161ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" 5s 113ms

And Go to "TRANSPORT_TABLE" 358ms

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

When Go to transport details "CONTAINER" 2s 947ms

And Fill transport form 8s 557ms

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

And Expand advice panel 280ms

And Edit advice in transport details 19s 176ms

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

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

And Expand advice panel 281ms

Then Check are advice values equals after edition 4s 741ms

Hooks

After Hooks.deleteTransportAfterTest() 842ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 140ms

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

And Set advice window in schedule 3s 195ms

And Fill advice form 18s 349ms

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

And Go to "TRANSPORT_TABLE" 451ms

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

Then Check are advice values equals 2s 947ms

Hooks

After Hooks.deleteTransportAfterTest() 777ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 14s 888ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 949ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

When Show all transport types 1s 152ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 252ms

And Set advice window in schedule 7s 526ms

And Fill advice form 18s 753ms

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

And Go to "TRANSPORT_TABLE" 472ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 3s 185ms

Then Check are advice values equals 5s 005ms

Hooks

After Hooks.deleteTransportAfterTest() 960ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 170ms

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

And Set advice window in schedule 3s 367ms

And Fill advice form 13s 005ms

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

And Go to "TRANSPORT_TABLE" 503ms

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

Then Check are advice values equals 2s 661ms

Error message

java.lang.AssertionError: Wartości w formularzu w polu phone-number-prefix są niepoprawne, wartość na stronie:  wartość poprawna: 48
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:137)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:263)
	at CucumberTests.Transport.AdviceTransport.checkAdviceValues(AdviceTransport.java:141)
	at ✽.Check are advice values equals(file:Features/Atom/Advice/AdviceTransport.feature:61)

Hooks

After Hooks.deleteTransportAfterTest() 825ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 016ms

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

When Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 382ms

And Fill advice form 13s 048ms

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

And Go to "TRANSPORT_TABLE" 480ms

And Go to transport details "LOAD" 3s 119ms

Then Check are advice values equals 2s 836ms

Hooks

After Hooks.deleteTransportAfterTest() 808ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 165ms

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

And Set advice window in schedule 3s 301ms

And Fill advice form 18s 801ms

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

And Go to "TRANSPORT_TABLE" 435ms

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

Then Check are advice values equals 4s 907ms

Hooks

After Hooks.deleteTransportAfterTest() 751ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 820ms

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

When Show all transport types 1s 137ms

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

And Set advice window in schedule 3s 240ms

And Fill advice form 18s 778ms

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

And Go to "TRANSPORT_TABLE" 423ms

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

Then Check are advice values equals 4s 962ms

Hooks

After Hooks.deleteTransportAfterTest() 765ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to change warehouse during advice creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-neuca" 001ms

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 9s

And Go to new transport "DELIVERY" 738ms

And Fill transport form 47s 977ms

And Select warehouse "Katowice" in step section "1" 1s 075ms

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

When Change warehouse in schedule to: "Ołtarzew" 1s 173ms

Then Set advice window in schedule 2s 871ms

And Check is transport created in schedule and set transport id 3s 135ms

And Go to "TRANSPORT_TABLE" 471ms

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

And Check if transport has warehouse "Ołtarzew" in step section "1" 089ms

Hooks

After Hooks.deleteTransportAfterTest() 969ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 826ms

And Set token of apiUsername "paa1-carrier@qa.qa-test" 232ms

And Accept transferred transport by Api 801ms

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

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

When Show all transport types 1s 325ms

And Click button advice in transport table "TRANSPORT" 228ms

And Set advice window in schedule 3s 178ms

And Fill advice form 17s 145ms

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

And Go to "TRANSPORT_TABLE" 487ms

And Go to transport details "TRANSPORT" 2s 932ms

Then Check are advice values equals 4s 837ms

Hooks

After Hooks.deleteTransportAfterTest() 802ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 664ms

And Set token of apiUsername "pskza1-carrier@qa.qa-test" 211ms

And Accept transferred transport by Api 763ms

And Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 095ms

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

When Show all transport types 1s 255ms

And Click button advice in transport table "SMALLS_IMPORT" 998ms

And Set advice window in schedule 3s 350ms

And Fill advice form 20s 068ms

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

And Go to "TRANSPORT_TABLE" 455ms

And Go to transport details "SMALLS_IMPORT" 2s 825ms

Then Check are advice values equals 5s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 847ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 634ms

And Set token of apiUsername "pskza1-carrier@qa.qa-test" 218ms

And Accept transferred transport by Api 702ms

And Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 799ms

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

When Show all transport types 1s 221ms

And Click button advice in transport table "SMALLS_EXPORT" 1s 008ms

And Set advice window in schedule 3s 444ms

And Fill advice form 20s 319ms

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

And Go to "TRANSPORT_TABLE" 433ms

And Go to transport details "SMALLS_EXPORT" 2s 886ms

Then Check are advice values equals 5s 011ms

Hooks

After Hooks.deleteTransportAfterTest() 849ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 646ms

And Accept transferred transport by Api 720ms

And Login as "paa1-carrier@qa.qa-test" 2s 665ms

When Show all transport types 1s 357ms

And Click button advice in transport table "TRANSPORT" 249ms

And Set week view 1s 896ms

And Show yesterday 1s 150ms

Then Check if advice restriction blockade windows are visible 040ms

Hooks

After Hooks.deleteTransportAfterTest() 686ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 15s 980ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 669ms

And Accept transferred transport by Api 752ms

And Login as "pskza1-carrier@qa.qa-test" 2s 604ms

When Show all transport types 1s 253ms

And Click button advice in transport table "SMALLS_IMPORT" 1s 146ms

And Set week view 2s 560ms

And Show yesterday 1s 183ms

Then Check if advice restriction blockade windows are visible 335ms

Hooks

After Hooks.deleteTransportAfterTest() 624ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 16s 062ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 642ms

And Accept transferred transport by Api 667ms

And Login as "pskza1-carrier@qa.qa-test" 2s 633ms

When Show all transport types 1s 195ms

And Click button advice in transport table "SMALLS_EXPORT" 1s 186ms

And Set week view 2s 413ms

And Show yesterday 1s 176ms

Then Check if advice restriction blockade windows are visible 307ms

Hooks

After Hooks.deleteTransportAfterTest() 598ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 000ms

And Click on time window date 1s 709ms

And Select view "DAYS_4" 2s 169ms

And Move advice window "3" 1s 496ms

Then Check if advice window is in new location 066ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 163ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 5s 400ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 454ms

And Show all transport "false" 000ms

And Click on time window date 16s 085ms

And Select view "DAYS_4" 2s 156ms

And Move advice window "3" 1s 718ms

Then Check if advice window is in new location 068ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 629ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 5s 225ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 681ms

And Show all transport "false" 000ms

And Click on time window date 15s 874ms

And Select view "DAYS_4" 2s 140ms

And Move advice window "3" 1s 614ms

Then Check if advice window is in new location 070ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 756ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 5s 470ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 907ms

And Show all transport "false" 000ms

And Click on time window date 1s 894ms

And Select view "DAYS_4" 2s 181ms

And Move advice window "3" 1s 592ms

Then Check if advice window is in new location 067ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 860ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 920ms

And Show all transport "false" 000ms

And Click on time window date 1s 874ms

And Select view "DAYS_4" 2s 168ms

And Move advice window "3" 1s 473ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 936ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 5s 623ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 748ms

And Show all transport "true" 164ms

And Click on time window date 1s 774ms

And Select view "DAYS_4" 2s 136ms

And Move advice window "3" 1s 518ms

Then Check if advice window is in new location 060ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 343ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add advice and move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 159ms

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

And Set advice window in schedule 3s 330ms

And Fill advice form 12s 955ms

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

And Go to "TRANSPORT_TABLE" 490ms

And Click on time window date 1s 875ms

And Select view "DAYS_4" 2s 176ms

And Move advice window "3" 1s 666ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 496ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_LATE_DELIVERY" by JSON file as "super-admin-hochland" in "0" days 2s 956ms

Then Check if transport row is "red" 3s 250ms

Hooks

After Hooks.deleteTransportAfterTest() 916ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Go to "TRANSPORT_TABLE" 418ms

And Show all transport types 1s 150ms

And Click on time window date 1s 706ms

And Scroll to time window "adviceWindow" 146ms

And Set time window height "2" "adviceWindow" 5s 589ms

Then Check height of the time window after expanding by "2" in "adviceWindow" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 929ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 383ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 845ms

And Go to "TRANSPORT_TABLE" 348ms

And Show all transport types 1s 200ms

And Click on time window date 1s 931ms

And Scroll to time window "adviceWindow" 119ms

And Set time window height "4" "adviceWindow" 5s 624ms

Then Check height of the time window after expanding by "4" in "adviceWindow" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 852ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 904ms

And Go to "TRANSPORT_TABLE" 451ms

And Show all transport types 1s 164ms

And Click on time window date 1s 723ms

And Scroll to time window "adviceWindow" 121ms

And Set time window height "3" "adviceWindow" 5s 615ms

Then Check height of the time window after expanding by "3" in "adviceWindow" 062ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 455ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 16s 996ms

And Go to "TRANSPORT_TABLE" 559ms

And Show all transport types 1s 157ms

And Click on time window date 2s 297ms

And Scroll to time window "adviceWindow" 233ms

And Set time window height "1" "adviceWindow" 5s 665ms

Then Check height of the time window after expanding by "1" in "adviceWindow" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 403ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule after add advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 439ms

And Fill advice form 13s 003ms

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

And Go to "TRANSPORT_TABLE" 481ms

And Click on time window date 1s 875ms

And Set time window height "2" "adviceWindow" 5s 675ms

Then Check height of the time window after expanding by "2" in "adviceWindow" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 618ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice after clicking back button in browser

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

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

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

And Go to "WAREHOUSE_TAB" 1s 243ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 854ms

When Go to new transport "DELIVERY" 708ms

And Fill transport form 46s 905ms

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

And Click previous page button in browser 063ms

Then Check if advice window can't be created 3s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice after modifing warehouse id in browser url

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Go to "WAREHOUSE_TAB" 1s 243ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 887ms

When Go to new transport "DELIVERY" 687ms

And Fill transport form 47s 086ms

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

And Replace warehouse id in browser url with "Twarożkarnia wyrób gotowy" id 113ms

Then Check if advice window can't be created 2s 617ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if transport without warehouse after carrier add advice has checkpoint steps

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT_WITHOUT_WAREHOUSES" by JSON file as "super-admin-adama" 2s 413ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 966ms

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

When Show all transport types 1s 154ms

And Click button advice in transport table "TRANSPORT" 238ms

And Fill advice form 16s 204ms

And Click advice save button and wait for advice form to disappear 17s 756ms

When Find transport in table with status "no-advice-undefined" 3s 745ms

And Open statuses popup 196ms

And Wait "2" seconds 2s

Then Check if transport has checkpoints from list "Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta" in "1" 163ms

Hooks

After Hooks.deleteTransportAfterTest() 655ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 881ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 952ms

And Login as "farmacol-admin" 7s 869ms

And Go to "WAREHOUSE_TAB" 1s 201ms

And Select warehouse "Katowice Przyjęcia" 1s 395ms

And Set week view 2s 728ms

And Move cursor over time window element 460ms

Then Check if "Zaawizowany" "31415" "06:00" "GDA12345" are visible on time window popup details 321ms

Hooks

After Hooks.deleteTransportAfterTest() 820ms

View Feature Advice transport

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is possible to advice transport after splitting advice data from advice window

- order: advice data => advice window [A-7478]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 4s 827ms

And Create default accepted mode of transportation by API with "pba1-carrier" 2s 034ms

And Create transport "CREATE_EXW_DELIVERY" by JSON file as "super-admin-bausch" 2s 193ms

And Set "advice" inputs from JSON file "ADVICE_EXW_DELIVERY" "super-admin-bausch" 001ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "true" confirmation 880ms

When Go to "TRANSPORT_TABLE" 401ms

And Show all transport types 1s 164ms

And Click button advice in transport table "EXW_DELIVERY" 694ms

And Fill advice form 13s 008ms

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

And Click button advice in transport table "EXW_DELIVERY" 254ms

And Set advice window in schedule 3s 198ms

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 2s 588ms

And Click advice save button and wait for advice form to disappear 34s 066ms

And Go to "TRANSPORT_TABLE" 419ms

And Show all transport types 1s 160ms

And Go to transport details "EXW_DELIVERY" 2s 905ms

Then Check are advice values equals 4s 704ms

Hooks

After Hooks.deleteTransportAfterTest() 843ms

After Hooks.deleteModeOfTransportationAfterTest() 335ms

View Feature Company Resources

@deleteTransportAfterTest

Scenario Outline Check if it possible to save resource to company from transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY_CONTRACTOR" "super-admin-neuca" 001ms

And Login as "pna1-carrier" and set token of apiUsername "super-admin-neuca" 2s 604ms

And Go to new transport "DELIVERY" 801ms

And Fill transport form 40s 930ms

And Select "save-as-resource" checkbox 380ms

When Click "save-transport" save button and wait for form to disappear 30s 264ms

And Set advice window in schedule 2s 404ms

And Check is transport created in schedule and set transport id 3s 880ms

Then Go to "OWN_COMPANY_TAB" 787ms

And Check if advice values are visible in company resources 366ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 065ms

View Feature Company Resources

@deleteTransportAfterTest

Scenario Outline Check if it possible to save resource to company from transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY_SUPPLIER" "super-admin-alrec" 001ms

And Login as "daaa1-supplier" and set token of apiUsername "super-admin-alrec" 4s 345ms

And Go to new transport "DELIVERY" 15s 464ms

And Fill transport form 21s 533ms

And Select "save-as-resource" checkbox 387ms

When Click "save-transport" save button and wait for form to disappear 30s 200ms

And Set advice window in schedule 2s 368ms

And Check is transport created in schedule and set transport id 3s 127ms

Then Go to "OWN_COMPANY_TAB" 856ms

And Check if advice values are visible in company resources 376ms

Hooks

After Hooks.deleteTransportAfterTest() 824ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7060

Scenario Outline Check if it is possible to create new custom field [A-7060]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "custom-field" inputs from JSON file "CREATE_CUSTOM_FIELD" "super-admin-skz" 001ms

And Go to "SETTINGS_TAB" 952ms

When Go to "CONTAINER" transport type settings 732ms

And Go to custom fields settings 407ms

And Click add new custom field 409ms

And Fill custom field form 6s 840ms

And Click save button 168ms

And Click back to custom field settings button 323ms

And Set custom field id 3s 272ms

And Refresh page 2s 239ms

Then Go to new transport "CONTAINER" 5s 637ms

And Verify if created custom field appeared in transport form 088ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 2s 956ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7060

Scenario Outline Check if it is possible to create new custom field [A-7060]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 7s 283ms

And Set "custom-field" inputs from JSON file "CREATE_CUSTOM_FIELD" "super-admin-piast" 001ms

And Go to "SETTINGS_TAB" 802ms

When Go to "LOAD" transport type settings 743ms

And Go to custom fields settings 430ms

And Click add new custom field 452ms

And Fill custom field form 6s 881ms

And Click save button 172ms

And Click back to custom field settings button 436ms

And Set custom field id 3s 312ms

And Refresh page 2s 235ms

Then Go to new transport "LOAD" 3s 485ms

And Verify if created custom field appeared in transport form 089ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 3s 129ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7060

Scenario Outline Check if it is possible to create new custom field [A-7060]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 15s 973ms

And Set "custom-field" inputs from JSON file "CREATE_CUSTOM_FIELD" "super-admin-hochland" 001ms

And Go to "SETTINGS_TAB" 876ms

When Go to "DELIVERY" transport type settings 620ms

And Go to custom fields settings 421ms

And Click add new custom field 433ms

And Fill custom field form 6s 891ms

And Click save button 144ms

And Click back to custom field settings button 315ms

And Set custom field id 6s 191ms

And Refresh page 2s 267ms

Then Go to new transport "DELIVERY" 7s 711ms

And Verify if created custom field appeared in transport form 092ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 5s 886ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7061

Scenario Outline Check if it is possible to edit custom field [A-7061]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create custom field with "CREATE_CONTAINER_TEXT_CFD" by "super-admin-skz" 3s 005ms

And Go to "SETTINGS_TAB" 836ms

When Go to "CONTAINER" transport type settings 703ms

And Go to custom fields settings 394ms

And Click edit button of "Testowy CFD" custom field 579ms

And Change filled value in details "definition-name" "text" "Edytowany CFD" "0" 1s 669ms

And Click save button 137ms

And Refresh page 2s 253ms

Then Go to new transport "CONTAINER" 5s 639ms

And Verify that edited "Edytowany CFD" is visible in transport form 084ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 2s 891ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7061

Scenario Outline Check if it is possible to edit custom field [A-7061]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 157ms

And Create custom field with "CREATE_LOAD_TEXT_CFD" by "super-admin-piast" 3s 386ms

And Go to "SETTINGS_TAB" 775ms

When Go to "LOAD" transport type settings 712ms

And Go to custom fields settings 438ms

And Click edit button of "Testowy CFD" custom field 497ms

And Change filled value in details "definition-name" "text" "Edytowany CFD" "0" 1s 673ms

And Click save button 142ms

And Refresh page 2s 228ms

Then Go to new transport "LOAD" 3s 525ms

And Verify that edited "Edytowany CFD" is visible in transport form 072ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 3s 038ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7061

Scenario Outline Check if it is possible to edit custom field [A-7061]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 11s 530ms

And Create custom field with "CREATE_DELIVERY_TEXT_CFD" by "super-admin-hochland" 6s 071ms

And Go to "SETTINGS_TAB" 940ms

When Go to "DELIVERY" transport type settings 591ms

And Go to custom fields settings 389ms

And Click edit button of "Testowy CFD" custom field 600ms

And Change filled value in details "definition-name" "text" "Edytowany CFD" "0" 1s 688ms

And Click save button 147ms

And Refresh page 2s 262ms

Then Go to new transport "DELIVERY" 7s 716ms

And Verify that edited "Edytowany CFD" is visible in transport form 072ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 5s 876ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 206ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 2s 281ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 9s 344ms

When Go to "TRANSPORT_TABLE" 456ms

And Sort transports by "show-mine" 1s 146ms

And Show all transport types 1s 188ms

Then Verify that created transport is "true" in transport table 1s 228ms

Hooks

After Hooks.deleteTransportAfterTest() 644ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 216ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 2s 208ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 748ms

When Go to "TRANSPORT_TABLE" 423ms

And Sort transports by "show-all" 1s 143ms

And Show all transport types 1s 197ms

Then Verify that created transport is "true" in transport table 1s 294ms

Hooks

After Hooks.deleteTransportAfterTest() 621ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 217ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 2s 179ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 690ms

When Go to "TRANSPORT_TABLE" 357ms

And Sort transports by "show-mine" 1s 141ms

And Show all transport types 1s 145ms

Then Verify that created transport is "false" in transport table 31s 738ms

Hooks

After Hooks.deleteTransportAfterTest() 600ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 240ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 2s 286ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 844ms

When Go to "TRANSPORT_TABLE" 364ms

And Sort transports by "show-all" 1s 129ms

And Show all transport types 1s 191ms

Then Verify that created transport is "true" in transport table 1s 293ms

Hooks

After Hooks.deleteTransportAfterTest() 664ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 227ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 2s 169ms

And Delete created transport by API 629ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 697ms

When Go to "ARCHIVE_TAB" 489ms

And Sort transports by "show-mine" 1s 146ms

And Show "SMALLS_IMPORT" 184ms

Then Verify that created transport is "true" in transport table 15s 146ms

Hooks

After Hooks.deleteTransportAfterTest() 584ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 216ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 16s 110ms

And Delete created transport by API 658ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 870ms

When Go to "ARCHIVE_TAB" 516ms

And Sort transports by "show-all" 1s 157ms

And Show "SMALLS_IMPORT" 169ms

Then Verify that created transport is "true" in transport table 15s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 632ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 216ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 16s 056ms

And Delete created transport by API 620ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 940ms

When Go to "ARCHIVE_TAB" 484ms

And Sort transports by "show-mine" 1s 159ms

And Show "SMALLS_IMPORT" 199ms

Then Verify that created transport is "false" in transport table 45s 722ms

Hooks

After Hooks.deleteTransportAfterTest() 596ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 227ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 16s 108ms

And Delete created transport by API 584ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 876ms

When Go to "ARCHIVE_TAB" 510ms

And Sort transports by "show-all" 1s 151ms

And Show "SMALLS_IMPORT" 152ms

Then Verify that created transport is "true" in transport table 15s 126ms

Hooks

After Hooks.deleteTransportAfterTest() 615ms

View Feature Filters

@deleteTransportAfterTest @FLAKY-A-8288

Scenario Outline Check if order is visible after filter load or unload time column in specific time range

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 2s 306ms

When Login as "alrec-admin" 2s 253ms

And Go to "TRANSPORT_TABLE" 436ms

And Show all transport "true" 171ms

And Select transportType "TRANSPORT_ORDER" 1s 329ms

Then Check if load and unload time filters work properly "LOAD_TIME_WINDOW" 37s 649ms

Hooks

After Hooks.deleteTransportAfterTest() 611ms

View Feature Filters

@deleteTransportAfterTest @FLAKY-A-8288

Scenario Outline Check if it is possible to choose what the search in the archive applies to

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 695ms

And Accept transferred transport by Api 559ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 4s 111ms

And Delete created transport by API 1s 146ms

When Go to "ARCHIVE_TAB" 682ms

And Show "CONTAINER" 210ms

Then Check if it is possible to search with different date property selects 28s 618ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[contains(@class, 'open')]//span[@aria-label='2021-08-19']"}
  (Session info: headless chrome=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.nXQC78}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 9cf8c623213683dad42f700c3a1a1e2f
*** Element info: {Using=xpath, value=//div[contains(@class, 'open')]//span[@aria-label='2021-08-19']}
	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.Filters.FiltersPage.fillDateFilters(FiltersPage.java:180)
	at Pages.Filters.FiltersPage.checkDateFilterPropertySelect(FiltersPage.java:293)
	at CucumberTests.Filters.FilterTransportTest.searchWithDifferentArchiveFilters(FilterTransportTest.java:115)
	at ✽.Check if it is possible to search with different date property selects(file:Features/Atom/Filters/Filter.feature:141)

Hooks

After Hooks.deleteTransportAfterTest() 761ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport table days limit filter displays correct transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare setting: "TRANSPORT_TABLE_DAYS_LIMIT" with value: "7d" with "super-admin-neuca" 109ms

When Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "8" days 16s 944ms

And Login as "neuca-admin" 7s 018ms

And Go to "TRANSPORT_TABLE" 508ms

Then Verify that created transport is "false" in transport table 31s 784ms

And Toggle transport table days limit filter 162ms

And Verify that created transport is "true" in transport table 1s 238ms

Hooks

After Hooks.deleteTransportAfterTest() 793ms

View Feature Grouping of carriers

@deleteTransportAfterTest @removeContractorsGroup

Scenario Outline Check if company is selected in inquiry after adding company to contractors group and selecting contractors group

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Add carrier "Przewoźnik SKZ Automat 1" to carriers group "Kraj" by Api as "super-admin-skz" 799ms

When Go to "TRANSPORT_TABLE" 386ms

And Go to auction form 1s 579ms

And Select contractors group "Kraj" 253ms

Then Verify that carrier "PSKZA1" is selected 087ms

Hooks

After Hooks.deleteTransportAfterTest() 696ms

After Hooks.removeContractorsGroup() 288ms

View Feature Grouping of carriers

@deleteTransportAfterTest

Scenario Outline Check if all contractors group are selected in inquiry after click in all contractors group checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 466ms

And Go to auction form 1s 562ms

And Select contractors group "Wybierz grupę firm transportowych" 254ms

Then Verify that all companies are selected after choose "data-group-name" 286ms

Hooks

After Hooks.deleteTransportAfterTest() 611ms

View Feature Grouping of carriers

@deleteTransportAfterTest

Scenario Outline Check if all companies are selected in inquiry after selecting all companies

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 452ms

And Go to auction form 1s 515ms

And Select contractors group "Wybierz uczestników zapytania" 232ms

Then Verify that all companies are selected after choose "data-carrier-name" 266ms

Hooks

After Hooks.deleteTransportAfterTest() 597ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to add new index to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 000ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-adama" 001ms

And Create product if needed "false" by api for principal "adama" 448ms

When Go to transport details "TRANSPORT" 2s 914ms

And Expand index panel 266ms

And Click add index button 310ms

And Fill index form 11s 755ms

And Click ok button in index form 15s 282ms

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

And Go to transport details "TRANSPORT" 2s 968ms

And Expand index panel 272ms

Then Check are transport values equals 246ms

Hooks

After Hooks.deleteProductAfterTest() 281ms

After Hooks.deleteTransportAfterTest() 653ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to add new index to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 412ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 199ms

And Show all transport "true" 164ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-alrec" 001ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 883ms

And Expand index panel 358ms

And Click add index button 265ms

And Fill index form 8s 710ms

And Click ok button in index form 15s 223ms

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

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

And Expand index panel 289ms

Then Check are transport values equals 2s 353ms

Hooks

After Hooks.deleteProductAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 549ms

View Feature Crud index

@deleteTransportAfterTest @deleteProductAfterTest

Scenario Outline Check if it possible to edit index in index form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 000ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-adama" 001ms

And Create product if needed "false" by api for principal "adama" 136ms

When Go to transport details "TRANSPORT" 2s 934ms

And Expand index panel 281ms

And Click add index button 297ms

And Fill index form 11s 752ms

And Click ok button in index form 15s 317ms

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

When Go to transport details "TRANSPORT" 2s 945ms

And Expand index panel 251ms

And Click edit index button 258ms

And Edit index quantity to "999" 307ms

And Click ok button in index form 15s 252ms

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

And Go to transport details "TRANSPORT" 2s 932ms

And Expand index panel 276ms

And Verify if index quantity equals "999" 067ms

Hooks

After Hooks.deleteProductAfterTest() 231ms

After Hooks.deleteTransportAfterTest() 574ms

View Feature Crud index

@deleteTransportAfterTest @deleteProductAfterTest

Scenario Outline Check if it possible to edit index in index form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 740ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 243ms

And Show all transport "true" 149ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-alrec" 001ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 866ms

And Expand index panel 324ms

And Click add index button 291ms

And Fill index form 8s 610ms

And Click ok button in index form 15s 247ms

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

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

And Expand index panel 281ms

And Click edit index button 264ms

And Edit index quantity to "999" 334ms

And Click ok button in index form 15s 232ms

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

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

And Expand index panel 243ms

And Verify if index quantity equals "999" 066ms

Hooks

After Hooks.deleteProductAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 496ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 000ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-adama" 001ms

And Create product if needed "false" by api for principal "adama" 166ms

When Go to transport details "TRANSPORT" 2s 915ms

And Add index to transport 27s 608ms

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

When Go to transport details "TRANSPORT" 2s 937ms

And Expand index panel 250ms

And Click delete index button 190ms

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

And Go to transport details "TRANSPORT" 2s 856ms

And Expand index panel 272ms

Then Verify that transport has no indexes 15s 085ms

Hooks

After Hooks.deleteProductAfterTest() 156ms

After Hooks.deleteTransportAfterTest() 534ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 516ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 223ms

And Show all transport "true" 167ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-alrec" 001ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 884ms

And Add index to transport 24s 560ms

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

When Go to transport details "TRANSPORT_ORDER" 2s 896ms

And Expand index panel 240ms

And Click delete index button 186ms

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

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

And Expand index panel 287ms

Then Verify that transport has no indexes 15s 088ms

Hooks

After Hooks.deleteProductAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 516ms

View Feature Index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if indexes displayed after click indexes details icon on time window

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 6s 160ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 084ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-dayco" 001ms

And Create product if needed "false" by api for principal "dayco" 117ms

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

And Add index to transport 25s 746ms

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

Then Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

And Click button advice in transport table "OWN_COLLECTION" 294ms

And Set advice window in schedule 3s 348ms

And Fill advice form 11s 642ms

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

When Click on index details icon 233ms

Then Verify that indexes display in window "product-index;quantity-of-Planned quantity;quantity-of-Quantity sent" 001ms

Hooks

After Hooks.deleteProductAfterTest() 272ms

After Hooks.deleteTransportAfterTest() 788ms

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

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

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

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

And Show all transport types 1s 169ms

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

And Set advice window in schedule 3s 356ms

And Fill advice form 17s 151ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 295ms

After Hooks.deleteTransportAfterTest() 829ms

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

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

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

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

And Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 413ms

And Fill advice form 12s 907ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 094ms

After Hooks.deleteTransportAfterTest() 846ms

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

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

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

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

And Show all transport types 1s 147ms

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

And Set advice window in schedule 3s 308ms

And Fill advice form 18s 773ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 508ms

After Hooks.deleteTransportAfterTest() 712ms

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

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

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

And Show all transport types 1s 164ms

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

And Go to "TRANSPORT_TABLE" 409ms

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

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

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

And Fill transport form 5s 182ms

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

And Expand advice panel 279ms

And Edit advice in transport details 17s 559ms

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" 37s 346ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 356ms

After Hooks.deleteTransportAfterTest() 749ms

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

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

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

And Show all transport types 1s 148ms

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

And Go to "TRANSPORT_TABLE" 347ms

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

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

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

And Fill transport form 1m 8s 782ms

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

And Expand advice panel 252ms

And Edit advice in transport details 8s 079ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 046ms

After Hooks.deleteTransportAfterTest() 838ms

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

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

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

And Show all transport types 1s 176ms

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

And Go to "TRANSPORT_TABLE" 412ms

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

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

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

And Fill transport form 28s 393ms

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

And Expand advice panel 264ms

And Edit advice in transport details 23s 449ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 749ms

After Hooks.deleteTransportAfterTest() 808ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 972ms

After Hooks.deleteTransportAfterTest() 764ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 728ms

After Hooks.deleteTransportAfterTest() 811ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 427ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 055ms

After Hooks.deleteTransportAfterTest() 766ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 042ms

After Hooks.deleteTransportAfterTest() 604ms

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

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 415ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 384ms

After Hooks.deleteTransportAfterTest() 621ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 010ms

After Hooks.deleteTransportAfterTest() 641ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 426ms

After Hooks.deleteTransportAfterTest() 574ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 053ms

After Hooks.deleteTransportAfterTest() 600ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 057ms

After Hooks.deleteTransportAfterTest() 659ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 427ms

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

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

And Fill transport form 43s 111ms

And Open section: "discrepancy-report-panel" 1s 159ms

And Fill discrepancy report section 52s 572ms

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

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 545ms

And Generate discrepancy report 21s 625ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 395ms

After Hooks.deleteTransportAfterTest() 1s 016ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 481ms

And Select warehouse "Serownia" 1s 561ms

And Set week view 1s 216ms

And Show yesterday 1s 129ms

And Move window into the past 407ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 308ms

After Hooks.deleteTransportAfterTest() 973ms

After Hooks.rollbackAddedAuthorities() 156ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 117ms

After Hooks.deleteTransportAfterTest() 572ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 186ms

After Hooks.deleteTransportAfterTest() 579ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 060ms

After Hooks.deleteTransportAfterTest() 850ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 022ms

After Hooks.deleteTransportAfterTest() 539ms

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

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

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

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

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

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

Then If user is login then logout 268ms

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

And Go to auction details 2s 228ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 820ms

After Hooks.deleteTransportAfterTest() 849ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 809ms

After Hooks.deleteTransportAfterTest() 709ms

View Feature Pallet limit

@deleteTransportAfterTest

Scenario Outline Verify that the error is visible after exceeding the pallet limit during create transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-neuca" 001ms

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 555ms

When Go to new transport "DELIVERY" 750ms

And Fill transport form 48s 188ms

And Change filled value in details "number-of-pallets-step-0" "number" "1000000" "0" 1s 637ms

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

And Set advice window in schedule 2s 384ms

Then Verify that the error is visible after exceeding the pallet limit 725ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Pallet limit

@deleteTransportAfterTest

Scenario Outline Verify that the error is visible after exceeding the pallet limit during edit transport [A-7071]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 418ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 17s 055ms

And Go to "TRANSPORT_TABLE" 595ms

And Show all transport "false" 000ms

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

And Change filled value in details "number-of-pallets-step-0" "number" "1000000" "0" 1s 654ms

And Click "save-transport" save button 1s 488ms

Then Verify that the error is visible after exceeding the pallet limit 069ms

Hooks

After Hooks.deleteTransportAfterTest() 911ms

View Feature Pallet limit

@deleteTransportAfterTest @rollbackMaxPalletLimit @TmsLink=A-7073 @FLAKY-A-8314

Scenario Outline Check if it is possible to create advice when pallet limit equals 1 [A-7073]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-pgf" 235ms

And Prepare max pallet limit "1" in "Magazyn Łódź" 042ms

And Set "transport" inputs from JSON file "CREATE_UNLOAD" "super-admin-pgf" 001ms

When Login as "pgf-admin" 5s 503ms

And Go to new transport "UNLOAD" 15s 507ms

And Fill transport form 32s 242ms

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

And Set advice window in schedule 2s 621ms

And Check is transport created in schedule and set transport id 2s 711ms

And Go to "TRANSPORT_TABLE" 502ms

And Go to transport details "UNLOAD" 30s 712ms

Then Check are transport values equals 26s 143ms

Hooks

After Hooks.deleteTransportAfterTest() 748ms

After Hooks.rollbackMaxPalletLimit() 013ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are not visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create default mode of transportation by API with "pba1-carrier" 464ms

And Set status of MOT to "AWAITING_VERIFICATION" 268ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 253ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 646ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 550ms

When Login as "super-admin-bausch" 6s 105ms

And Go to "TRANSPORT_TABLE" 487ms

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

And Set advice window in schedule 3s 418ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 16s 419ms

Hooks

After Hooks.deleteTransportAfterTest() 587ms

After Hooks.deleteModeOfTransportationAfterTest() 306ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are not visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create default mode of transportation by API with "pba1-carrier" 441ms

And Set status of MOT to "DISABLED" 305ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 119ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 651ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 438ms

When Login as "super-admin-bausch" 2s 611ms

And Go to "TRANSPORT_TABLE" 400ms

And Click button advice in transport table "LOAD_EXPORT" 329ms

And Set advice window in schedule 3s 358ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 16s 487ms

Hooks

After Hooks.deleteTransportAfterTest() 598ms

After Hooks.deleteModeOfTransportationAfterTest() 253ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Create default mode of transportation by API with "pba1-carrier" 447ms

And Set status of MOT to "ACCEPTED" 302ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 135ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 660ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 449ms

When Login as "super-admin-bausch" 2s 587ms

And Go to "TRANSPORT_TABLE" 509ms

And Click button advice in transport table "LOAD_EXPORT" 285ms

And Set advice window in schedule 3s 391ms

Then Check if "AAAA0000" MOT can be selected in advice form 1s 549ms

Hooks

After Hooks.deleteTransportAfterTest() 615ms

After Hooks.deleteModeOfTransportationAfterTest() 327ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create default mode of transportation by API with "pba1-carrier" 455ms

And Set status of MOT to "UPDATED" 320ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 131ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 666ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 458ms

When Login as "super-admin-bausch" 2s 614ms

And Go to "TRANSPORT_TABLE" 512ms

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

And Set advice window in schedule 3s 344ms

Then Check if "AAAA0000" MOT can be selected in advice form 1s 658ms

Hooks

After Hooks.deleteTransportAfterTest() 618ms

After Hooks.deleteModeOfTransportationAfterTest() 295ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible but not available during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create default mode of transportation by API with "pba1-carrier" 462ms

And Set status of MOT to "REJECTED" 270ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 141ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 655ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 457ms

When Login as "super-admin-bausch" 2s 587ms

And Go to "TRANSPORT_TABLE" 549ms

And Click button advice in transport table "LOAD_EXPORT" 237ms

And Set advice window in schedule 3s 434ms

Then Check if "AAAA0000" MOT is visible in advice form 1s 524ms

And Check if "AAAA0000" MOT cannot be selected in advice form 15s 448ms

Hooks

After Hooks.deleteTransportAfterTest() 585ms

After Hooks.deleteModeOfTransportationAfterTest() 303ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible but not available during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create default mode of transportation by API with "pba1-carrier" 446ms

And Set status of MOT to "BLOCKED" 291ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 088ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 620ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 446ms

When Login as "super-admin-bausch" 2s 504ms

And Go to "TRANSPORT_TABLE" 538ms

And Click button advice in transport table "LOAD_EXPORT" 240ms

And Set advice window in schedule 3s 338ms

Then Check if "AAAA0000" MOT is visible in advice form 1s 451ms

And Check if "AAAA0000" MOT cannot be selected in advice form 15s 480ms

Hooks

After Hooks.deleteTransportAfterTest() 667ms

After Hooks.deleteModeOfTransportationAfterTest() 309ms

View Feature SK Api - Statuses confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm statuses by SkApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Add transport by SKApi in "MGW" assigned to "" 2s 355ms

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

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

And Set advice window in schedule 3s 451ms

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

And Fill advice form 20s 467ms

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

And Find transport in table with status "planned" 3s 733ms

And Confirm statuses until reach "left-the-factory" through SKAPI 49s 787ms

Then Check if transport has "left-the-factory" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 822ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 690ms

And Go to "TRANSPORT_TABLE" 359ms

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

Then Check are transport values equals 1s 285ms

Hooks

After Hooks.deleteTransportAfterTest() 600ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 349ms

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

Then Check are transport values equals 1s 215ms

Hooks

After Hooks.deleteTransportAfterTest() 602ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 125ms

And Go to "TRANSPORT_TABLE" 362ms

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

Then Check are transport values equals 1s 225ms

Hooks

After Hooks.deleteTransportAfterTest() 584ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Add transport by SKApi in "HRL" assigned to "" 025ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 670ms

And Go to "TRANSPORT_TABLE" 379ms

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

Then Check are transport values equals 148ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.nXQC78}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 9cf8c623213683dad42f700c3a1a1e2f
	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.getAttribute(RemoteWebElement.java:128)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:121)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:263)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:239)
	at ✽.Check are transport values equals(file:Features/Atom/SK_API/SkApiTransport.feature:11)

Hooks

After Hooks.deleteTransportAfterTest() 616ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Add transport by SKApi in "HRL" assigned to "" 021ms

Then Check is transport "CONTAINER" created in transport table and set transport id 4s 062ms

And Go to "TRANSPORT_TABLE" 383ms

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

Then Check are transport values equals 1s 147ms

Hooks

After Hooks.deleteTransportAfterTest() 599ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

When Add transport by SKApi in "HRL" assigned to "" 026ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 178ms

And Go to "TRANSPORT_TABLE" 364ms

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

Then Check are transport values equals 1s 096ms

Hooks

After Hooks.deleteTransportAfterTest() 580ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi with specific client name

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Set another client name "Pepsi" 000ms

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

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 745ms

And Check client name in database "Pepsi" "TRANSPORT_ORDER" 196ms

Hooks

After Hooks.deleteTransportAfterTest() 692ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it transport created by SKApi without `warehouse_alias` field is in default warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Add transport by SKApi in "" assigned to "" 020ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 743ms

And Go to "TRANSPORT_TABLE" 486ms

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

Then Check if transport has warehouse "MGW" in step section "0" 173ms

Hooks

After Hooks.deleteTransportAfterTest() 588ms

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

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

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

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 7s 051ms

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

And Set advice window in schedule 3s 523ms

And Fill advice form 20s 239ms

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

And Go to "TRANSPORT_TABLE" 433ms

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

Then Check are advice values equals 4s 918ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 387ms

After Hooks.deleteTransportAfterTest() 846ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 394ms

And Fill advice form 20s 478ms

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

And Go to "TRANSPORT_TABLE" 449ms

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

Then Check are advice values equals 4s 929ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 160ms

After Hooks.deleteTransportAfterTest() 810ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 318ms

And Fill advice form 20s 136ms

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

And Go to "TRANSPORT_TABLE" 480ms

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

Then Check are advice values equals 4s 983ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 335ms

After Hooks.deleteTransportAfterTest() 781ms

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

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

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

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

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

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

And Set advice window in schedule 3s 399ms

And Fill advice form 20s 050ms

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

And Go to "TRANSPORT_TABLE" 523ms

And Go to transport details "TRANSPORT_ORDER" 3s 040ms

Then Check are advice values equals 4s 882ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 621ms

After Hooks.deleteTransportAfterTest() 796ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 30s 125ms

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=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.nXQC78}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 9cf8c623213683dad42f700c3a1a1e2f
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:82)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

And Fill advice form 000ms

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

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 773ms

After Hooks.deleteTransportAfterTest() 536ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 322ms

And Fill advice form 20s 415ms

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

And Go to "TRANSPORT_TABLE" 454ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 217ms

After Hooks.deleteTransportAfterTest() 831ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 379ms

And Fill advice form 20s 424ms

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

And Go to "TRANSPORT_TABLE" 441ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 400ms

After Hooks.deleteTransportAfterTest() 819ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 371ms

And Fill advice form 20s 368ms

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

And Go to "TRANSPORT_TABLE" 436ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 273ms

After Hooks.deleteTransportAfterTest() 813ms

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

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 351ms

And Fill advice form 20s 235ms

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

And Go to "TRANSPORT_TABLE" 526ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 198ms

After Hooks.deleteTransportAfterTest() 910ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 424ms

And Fill advice form 20s 309ms

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

And Go to "TRANSPORT_TABLE" 442ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 713ms

After Hooks.deleteTransportAfterTest() 850ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if not possible to advice transport in the past when advice is created from transports table and transport is created by sk API

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

And Set advice window in schedule in the past 3s 338ms

And Fill advice form 20s 516ms

And Click advice save button to check error message 192ms

Then Check if possible advice alert is displayed 062ms

Hooks

After Hooks.deleteTransportAfterTest() 574ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that 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" 2s 765ms

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

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

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-skz" 4s 053ms

And Go to "TRANSPORT_TABLE" 379ms

When Go to transport details "OWN_COLLECTION" 2s 906ms

And Expand advice panel 326ms

And Edit advice in transport details 19s 197ms

And Fill arrival date field 2s 617ms

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

Then Check advice data in database after edition "OWN_COLLECTION" 096ms

Hooks

After Hooks.deleteTransportAfterTest() 950ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that 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" 2s 857ms

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

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

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" 4s 835ms

And Go to "TRANSPORT_TABLE" 385ms

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

And Expand advice panel 286ms

And Edit advice in transport details 19s 441ms

And Fill arrival date field 2s 641ms

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

Then Check advice data in database after edition "CONTAINER" 094ms

Hooks

After Hooks.deleteTransportAfterTest() 728ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that 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" 2s 827ms

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

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

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_TRANSPORT_ORDER" as "super-admin-skz" 4s 789ms

And Go to "TRANSPORT_TABLE" 341ms

When Go to transport details "TRANSPORT_ORDER" 2s 957ms

And Expand advice panel 224ms

And Edit advice in transport details 19s 187ms

And Fill arrival date field 2s 653ms

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

Then Check advice data in database after edition "TRANSPORT_ORDER" 091ms

Hooks

After Hooks.deleteTransportAfterTest() 864ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 285ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 190ms

When Go to "WAREHOUSE_TAB" 1s 241ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 863ms

And Select view "DAYS_2" 2s 167ms

Then Check if gray window is in the schedule 2s 039ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 413ms

And Select view "DAYS_2" 2s 124ms

And Check if gray window is in the schedule 2s 040ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 608ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-producer" and set token of apiUsername "super-admin-hochland" 10s 405ms

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 211ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 193ms

When Go to "WAREHOUSE_TAB" 1s 316ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 949ms

And Select view "DAYS_2" 2s 176ms

Then Check if gray window is in the schedule 2s 045ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 432ms

And Select view "DAYS_2" 2s 138ms

And Check if gray window is in the schedule 2s 039ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 610ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pha1-carrier@qa.qa-test" and set token of apiUsername "super-admin-hochland" 9s 627ms

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 308ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 337ms

When Go to "WAREHOUSE_TAB" 1s 493ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 869ms

And Select view "DAYS_2" 2s 166ms

Then Check if gray window is in the schedule 2s 046ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 424ms

And Select view "DAYS_2" 2s 132ms

And Check if gray window is in the schedule 2s 040ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 576ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create "CREATE_GRAY_WINDOW_MGW" window by JSON file for test as "super-admin-skz" 217ms

And Create "CREATE_GRAY_WINDOW_HRL" window by JSON file for test as "super-admin-skz" 198ms

When Go to "WAREHOUSE_TAB" 988ms

And Select warehouse "MGW" 1s 399ms

And Select view "DAYS_2" 2s 216ms

Then Check if gray window is in the schedule 2s 043ms

And Select warehouse "HRL" 1s 560ms

And Select view "DAYS_2" 2s 135ms

And Check if gray window is in the schedule 2s 042ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 552ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 259ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_WAREHOUSE_STEP_ONLY" "super-admin-neuca" 001ms

And Get package type settings for transportType "DELIVERY" from "neuca" 266ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;false" 430ms

When Login as "neuca-admin" 7s 675ms

And Go to new transport "DELIVERY" 712ms

And Fill transport form 39s 506ms

And Get sum of pallets of "load" in transport form 084ms

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

And Set advice window in schedule 2s 380ms

And Check is transport created in schedule and set transport id 3s 668ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 213ms

Hooks

After Hooks.deleteTransportAfterTest() 977ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 148ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 276ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_COMPANY_STEP_ONLY" "super-admin-neuca" 000ms

And Get package type settings for transportType "DELIVERY" from "neuca" 124ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "false;true" 237ms

When Login as "neuca-admin" 2s 528ms

And Go to new transport "DELIVERY" 666ms

And Fill transport form 39s 515ms

And Get sum of pallets of "unload" in transport form 065ms

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

And Set advice window in schedule 2s 392ms

And Check is transport created in schedule and set transport id 3s 190ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 270ms

Hooks

After Hooks.deleteTransportAfterTest() 958ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 162ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 251ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_WAREHOUSE_AND_COMPANY_STEPS" "super-admin-neuca" 000ms

And Get package type settings for transportType "DELIVERY" from "neuca" 138ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;true" 229ms

When Login as "neuca-admin" 2s 520ms

And Go to new transport "DELIVERY" 659ms

And Fill transport form 42s 436ms

And Get sum of pallets of "unload" in transport form 084ms

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

And Set advice window in schedule 2s 398ms

And Check is transport created in schedule and set transport id 3s 214ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 274ms

Hooks

After Hooks.deleteTransportAfterTest() 906ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 133ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 188ms

And Mark custom fields as not obligatory 2s 917ms

And Login as "hochland-admin" 10s 057ms

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

When Find transport in table with status "advice-added" 3s 680ms

And Confirm statuses until reach "process-ended" 22s 976ms

Then Check if transport has "process-ended" 072ms

Hooks

After Hooks.deleteTransportAfterTest() 788ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 640ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-pgf" 239ms

And Get custom field settings for "UNLOAD" transport type and "pgf" company 110ms

And Mark custom fields as not obligatory 004ms

And Login as "pgf-admin" 4s 730ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 442ms

When Find transport in table with status "planned" 17s 623ms

And Confirm statuses until reach "process-ended" 11s 526ms

Then Check if transport has "process-ended" 071ms

Hooks

After Hooks.deleteTransportAfterTest() 808ms

After Hooks.rollbackAllCustomFieldsSettings() 423ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "adama" company 116ms

And Mark custom fields as not obligatory 005ms

And Login as "adama-admin" 4s 732ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 746ms

When Find transport in table with status "planned" 3s 714ms

And Confirm statuses until reach "process-ended" 11s 410ms

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 682ms

After Hooks.rollbackAllCustomFieldsSettings() 419ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "lantmannen" company 093ms

And Mark custom fields as not obligatory 005ms

And Login as "lantmannen-admin" 4s 682ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 831ms

When Find transport in table with status "potwierdzony" 3s 652ms

And Confirm statuses until reach "process-ended" 21s 829ms

Then Check if transport has "process-ended" 069ms

Hooks

After Hooks.deleteTransportAfterTest() 752ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "LOAD" transport type and "lantmannen" company 095ms

And Mark custom fields as not obligatory 005ms

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

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

When Find transport in table with status "created" 3s 697ms

And Confirm statuses until reach "process-ended" 27s 118ms

Then Check if transport has "process-ended" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 768ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 107ms

And Mark custom fields as not obligatory 590ms

And Login as "keeeper-admin" 5s 689ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 877ms

When Find transport in table with status "planned" 3s 706ms

And Confirm statuses until reach "process-ended" 21s 855ms

Then Check if transport has "process-ended" 087ms

Hooks

After Hooks.deleteTransportAfterTest() 793ms

After Hooks.rollbackAllCustomFieldsSettings() 662ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 111ms

And Mark custom fields as not obligatory 567ms

And Login as "keeeper-admin" 5s 615ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 938ms

When Find transport in table with status "planned" 3s 619ms

And Confirm statuses until reach "process-ended" 21s 862ms

Then Check if transport has "process-ended" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 985ms

After Hooks.rollbackAllCustomFieldsSettings() 773ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 783ms

And Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 506ms

And Show "SMALLS_IMPORT" 216ms

When Accept or reject "accept" transferred transport 2s 976ms

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

And Click button advice in transport table "SMALLS_IMPORT" 238ms

And Set advice window in schedule 3s 399ms

And Fill advice form 20s 299ms

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

And Check if window is "silver" 4s 076ms

And Go to "TRANSPORT_TABLE" 480ms

Then Check if transport has "process-ended" 080ms

Hooks

After Hooks.deleteTransportAfterTest() 874ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 667ms

And Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 724ms

And Show "SMALLS_EXPORT" 199ms

When Accept or reject "accept" transferred transport 18s 067ms

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

And Click button advice in transport table "SMALLS_EXPORT" 290ms

And Set advice window in schedule 3s 477ms

And Fill advice form 20s 186ms

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

And Check if window is "silver" 4s 072ms

And Go to "TRANSPORT_TABLE" 454ms

Then Check if transport has "process-ended" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 860ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to edit advice after reach specific status

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_ADVICE" "CHECKPOINT_BASED" "ARRIVAL" 436ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 193ms

And Mark custom fields as not obligatory 2s 686ms

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

When Login as "hochland-admin" 10s 108ms

And Find transport in table with status "advice-added" 3s 806ms

And Confirm statuses until reach "arrived" 6s 305ms

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

Then Check if it is not possible to edit advice 1s 371ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 003ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 499ms

After Hooks.rollbackAddedActionAuthorities() 287ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check is transport color changed after confirm status

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 196ms

And Mark custom fields as not obligatory 2s 953ms

And Login as "hochland-admin" 9s 854ms

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

When Find transport in table with status "advice-added" 3s 698ms

And Check if transport row is "blue" 3s 240ms

And Confirm statuses until reach "arrived" 6s 308ms

And Check if transport row is "green" 3s 219ms

And Confirm statuses until reach "during-unload" 6s 214ms

Then Check if transport row is "orange" 3s 204ms

And Confirm statuses until reach "unloaded" 6s 236ms

Then Check if transport row is "darkgoldenrod" 3s 222ms

And Confirm statuses until reach "process-ended" 6s 236ms

Then Check if transport row is "silver" 3s 213ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 503ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "piast" company 246ms

And Mark custom fields as not obligatory 010ms

And Login as "piast-admin" 5s 426ms

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

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

And Show all transport types 1s 155ms

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

And Set advice window in schedule 3s 331ms

And Fill advice form 12s 850ms

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

And Go to "TRANSPORT_TABLE" 451ms

And Find transport in table with status "advice-added" 3s 675ms

And Confirm statuses until reach "left-the-area" 32s 299ms

Then Check if next status is not possible to confirm 315ms

Hooks

After Hooks.deleteTransportAfterTest() 790ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 855ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "LOAD" transport type and "piast" company 246ms

And Mark custom fields as not obligatory 008ms

And Login as "piast-admin" 5s 695ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 953ms

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

And Show all transport types 1s 158ms

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

And Set advice window in schedule 3s 351ms

And Fill advice form 13s 045ms

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

And Go to "TRANSPORT_TABLE" 442ms

And Find transport in table with status "advice-added" 3s 717ms

And Confirm statuses until reach "left-the-area" 32s 284ms

Then Check if next status is not possible to confirm 301ms

Hooks

After Hooks.deleteTransportAfterTest() 770ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 460ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "piast" company 231ms

And Mark custom fields as not obligatory 011ms

And Login as "piast-admin" 5s 734ms

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

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

And Show all transport types 1s 157ms

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

And Set advice window in schedule 3s 332ms

And Fill advice form 13s 074ms

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

And Go to "TRANSPORT_TABLE" 521ms

And Find transport in table with status "advice-added" 3s 716ms

When Add file to transport by API 2s 583ms

And Confirm statuses until reach "process-ended" 41s 033ms

Then Check if transport has "process-ended" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 212ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 533ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "LOAD" transport type and "piast" company 314ms

And Mark custom fields as not obligatory 010ms

And Login as "piast-admin" 7s 016ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 240ms

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

And Show all transport types 1s 178ms

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

And Set advice window in schedule 3s 512ms

And Fill advice form 13s 241ms

And Click advice save button and wait for advice form to disappear 35s 071ms

And Go to "TRANSPORT_TABLE" 488ms

And Find transport in table with status "advice-added" 3s 783ms

When Add file to transport by API 1s 842ms

And Confirm statuses until reach "process-ended" 33s 265ms

Error message

java.lang.AssertionError: Wartość advice-added-magazyn-hala-a atrybutu data-status-name nie zmieniła się w webelemencie [[ChromeDriver: chrome on LINUX (9cf8c623213683dad42f700c3a1a1e2f)] -> xpath: //td[contains(@data-status-name, 'advice-added')]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.StatusUtil.waitUntilAttributeOfWebElementChangeValue(StatusUtil.java:43)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:310)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:297)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:88)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:119)

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 221ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 204ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 338ms

And Mark custom fields as not obligatory 9s 138ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 1s 140ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 2s 138ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Login as "hochland-admin" 12s 162ms

And Show all transport types 1s 190ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 391ms

And Set advice window in schedule 7s 591ms

And Fill advice form 19s 276ms

And Click advice save button and wait for advice form to disappear 35s 087ms

And Go to "TRANSPORT_TABLE" 477ms

And Find transport in table with status "advice-added" 3s 632ms

And Confirm statuses until reach "during-load" 11s 741ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 643ms

And Check if next status is not possible to confirm in status confirmation modal 336ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 624ms

After Hooks.rollbackAllCustomFieldsSettings() 9s 183ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 281ms

And Get custom field settings for "LOAD" transport type and "keeeper" company 153ms

And Mark custom fields as not obligatory 1s 648ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 269ms

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

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

And Login as "keeeper-admin" 6s 380ms

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 426ms

And Fill advice form 19s 098ms

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

And Go to "TRANSPORT_TABLE" 470ms

And Find transport in table with status "advice-added" 3s 789ms

And Confirm statuses until reach "arrived" 6s 346ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 647ms

And Check if next status is not possible to confirm in status confirmation modal 280ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 309ms

After Hooks.rollbackAllCustomFieldsSettings() 966ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 435ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 159ms

And Mark custom fields as not obligatory 1s 215ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 362ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 2s 099ms

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

And Login as "keeeper-admin" 7s 015ms

And Show all transport types 1s 179ms

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

And Set advice window in schedule 3s 412ms

And Fill advice form 19s 156ms

And Click advice save button and wait for advice form to disappear 34s 476ms

And Go to "TRANSPORT_TABLE" 470ms

And Find transport in table with status "advice-added" 3s 722ms

And Confirm statuses until reach "arrived" 6s 470ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 637ms

And Check if next status is not possible to confirm in status confirmation modal 283ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 208ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 436ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 113ms

And Mark custom fields as not obligatory 772ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 312ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 234ms

And Login as "keeeper-admin" 6s 836ms

And Go to "TRANSPORT_TABLE" 464ms

And Find transport in table with status "planned" 3s 693ms

And Confirm statuses until reach "arrived" 6s 348ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 673ms

And Check if next status is not possible to confirm in status confirmation modal 276ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 156ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 111ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 421ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 140ms

And Mark custom fields as not obligatory 1s 344ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 511ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 713ms

And Login as "keeeper-admin" 6s 386ms

And Go to "TRANSPORT_TABLE" 442ms

And Find transport in table with status "planned" 3s 707ms

And Confirm statuses until reach "arrived" 6s 377ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 610ms

And Check if next status is not possible to confirm in status confirmation modal 253ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 480ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 055ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 203ms

And Mark custom fields as not obligatory 5s 327ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 4s 051ms

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

And Login as "hochland-admin" 12s 049ms

And Go to "TRANSPORT_TABLE" 543ms

And Find transport in table with status "advice-added" 3s 762ms

And Confirm statuses until reach "during-unload" 11s 633ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 721ms

And Check if next status is not possible to confirm in status confirmation modal 433ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 118ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 059ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 255ms

And Get custom field settings for "LOAD" transport type and "keeeper" company 127ms

And Mark custom fields as not obligatory 764ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 211ms

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

And Login as "keeeper-admin" 5s 456ms

And Show all transport types 1s 286ms

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

And Set advice window in schedule 3s 249ms

And Fill advice form 18s 747ms

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

And Go to "TRANSPORT_TABLE" 444ms

And Find transport in table with status "advice-added" 3s 654ms

When Confirm statuses until reach "arrived" 6s 228ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 562ms

And Check if next status is not possible to confirm in status confirmation modal 252ms

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

And Click cancel in status confirmation modal 15s 354ms

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

And Open section: "advice-panel" 1s 154ms

And Fill transport form 28s 623ms

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

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

And Open section: "advice-panel" 1s 162ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 30s 612ms

And Confirm statuses until reach "process-ended" 16s 554ms

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 843ms

After Hooks.rollbackAllCustomFieldsSettings() 884ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 235ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 122ms

And Mark custom fields as not obligatory 769ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 222ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 888ms

And Login as "keeeper-admin" 5s 889ms

And Show all transport types 1s 166ms

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

And Set advice window in schedule 3s 225ms

And Fill advice form 18s 778ms

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

And Go to "TRANSPORT_TABLE" 448ms

And Find transport in table with status "advice-added" 3s 674ms

When Confirm statuses until reach "arrived" 6s 274ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 542ms

And Check if next status is not possible to confirm in status confirmation modal 216ms

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

And Click cancel in status confirmation modal 15s 309ms

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

And Open section: "advice-panel" 1s 139ms

And Fill transport form 28s 689ms

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

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

And Open section: "advice-panel" 1s 151ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 30s 625ms

And Confirm statuses until reach "process-ended" 16s 624ms

Then Check if transport has "process-ended" 063ms

Hooks

After Hooks.deleteTransportAfterTest() 798ms

After Hooks.rollbackAllCustomFieldsSettings() 907ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 245ms

And Mark custom fields as not obligatory 4s 889ms

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

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 415ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 937ms

And Login as "hochland-admin" 10s 368ms

And Show all transport types 1s 150ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 094ms

And Set advice window in schedule 7s 512ms

And Fill advice form 18s 741ms

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

And Go to "TRANSPORT_TABLE" 464ms

And Find transport in table with status "advice-added" 3s 642ms

When Confirm statuses until reach "during-load" 11s 521ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 608ms

And Check if next status is not possible to confirm in status confirmation modal 321ms

And Set "transport" inputs from JSON file "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 000ms

And Click cancel in status confirmation modal 15s 402ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 3s 001ms

And Open section: "advice-panel" 1s 158ms

And Fill transport form 39s 949ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 912ms

And Open section: "advice-panel" 1s 355ms

And Fill "warehouseman-(u)" in transport form 30s 687ms

And Confirm statuses until reach "process-ended" 32s 223ms

Then Check if transport has "process-ended" 062ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 061ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 215ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 252ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 112ms

And Mark custom fields as not obligatory 564ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 245ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 986ms

And Login as "keeeper-admin" 5s 870ms

And Go to "TRANSPORT_TABLE" 432ms

And Find transport in table with status "planned" 3s 667ms

When Confirm statuses until reach "arrived" 6s 289ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 639ms

And Check if next status is not possible to confirm in status confirmation modal 258ms

And Click cancel in status confirmation modal 15s 409ms

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

And Fill transport form 43s 070ms

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

And Confirm statuses until reach "process-ended" 16s 575ms

Then Check if transport has "process-ended" 080ms

Hooks

After Hooks.deleteTransportAfterTest() 792ms

After Hooks.rollbackAllCustomFieldsSettings() 601ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 226ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 119ms

And Mark custom fields as not obligatory 608ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 249ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 963ms

And Login as "keeeper-admin" 5s 872ms

And Go to "TRANSPORT_TABLE" 419ms

And Find transport in table with status "planned" 3s 646ms

When Confirm statuses until reach "arrived" 6s 252ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 624ms

And Check if next status is not possible to confirm in status confirmation modal 290ms

And Click cancel in status confirmation modal 15s 379ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 860ms

And Fill transport form 43s 203ms

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

And Confirm statuses until reach "process-ended" 16s 625ms

Then Check if transport has "process-ended" 068ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

After Hooks.rollbackAllCustomFieldsSettings() 720ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 210ms

And Mark custom fields as not obligatory 2s 796ms

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

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 745ms

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

And Login as "hochland-admin" 10s 362ms

And Go to "TRANSPORT_TABLE" 482ms

And Find transport in table with status "advice-added" 3s 693ms

When Confirm statuses until reach "during-unload" 11s 461ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 680ms

And Check if next status is not possible to confirm in status confirmation modal 394ms

And Click cancel in status confirmation modal 15s 466ms

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

And Fill transport form 43s 054ms

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

And Confirm statuses until reach "process-ended" 11s 491ms

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 859ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 409ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm status by guard without confirming earlier statuses

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Login as "swiss-krono-delivery-guard" 4s 766ms

And Go to "TRANSPORT_TABLE" 470ms

When Confirm "Departure" status in transport row 169ms

Then Verify that "Departure" has been confirmed 1s 312ms

Hooks

After Hooks.deleteTransportAfterTest() 822ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 271ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 116ms

And Mark custom fields as not obligatory 630ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 267ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 16s 927ms

When Login as "keeeper-admin" 5s 739ms

And Find transport in table with status "planned" 3s 721ms

And Confirm statuses until reach "arrived" 6s 269ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 558ms

And Check if next status is not possible to confirm in status confirmation modal 246ms

And Click cancel in status confirmation modal 15s 365ms

And Go to transport details "UNLOAD" 3s 001ms

And Fill transport form 43s 149ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 342ms

And Check if next status is not possible to confirm in status confirmation modal 225ms

Hooks

After Hooks.deleteTransportAfterTest() 750ms

After Hooks.rollbackAllCustomFieldsSettings() 574ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 225ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 127ms

And Mark custom fields as not obligatory 614ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 254ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 987ms

When Login as "keeeper-admin" 5s 932ms

And Find transport in table with status "planned" 3s 707ms

And Confirm statuses until reach "arrived" 6s 244ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 674ms

And Check if next status is not possible to confirm in status confirmation modal 269ms

And Click cancel in status confirmation modal 15s 387ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 894ms

And Fill transport form 43s 121ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 318ms

And Check if next status is not possible to confirm in status confirmation modal 249ms

Hooks

After Hooks.deleteTransportAfterTest() 755ms

After Hooks.rollbackAllCustomFieldsSettings() 696ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 203ms

And Mark custom fields as not obligatory 2s 793ms

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

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 744ms

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

When Login as "hochland-admin" 10s 192ms

And Find transport in table with status "advice-added" 3s 825ms

And Confirm statuses until reach "during-unload" 11s 542ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 635ms

And Check if next status is not possible to confirm in status confirmation modal 249ms

And Click cancel in status confirmation modal 15s 558ms

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

And Fill transport form 43s 156ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 311ms

And Check if next status is not possible to confirm in status confirmation modal 280ms

Hooks

After Hooks.deleteTransportAfterTest() 834ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 479ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings @rollbackTaskChanges

Scenario Outline Check if it is possible to confirm status with given confirmation date [A-7159]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 279ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 156ms

And Mark custom fields as not obligatory 717ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 2s 084ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 290ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 627ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 445ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 951ms

And Login as "bausch-admin" 6s 550ms

And Go to "TRANSPORT_TABLE" 501ms

And Find transport in table with status "advice-added" 3s 678ms

And Confirm statuses until reach "on-the-way" 16s 705ms

When Open statuses popup 147ms

And Toggle status date confirmation checkbox 387ms

And Confirm statuses until reach "process-ended" 6s 242ms

Then Check if transport has "process-ended" 075ms

Hooks

After Hooks.deleteTransportAfterTest() 895ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 187ms

After Hooks.deleteModeOfTransportationAfterTest() 372ms

After Hooks.rollbackTaskChanges() 201ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings @rollbackTaskChanges

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 317ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 171ms

And Mark custom fields as not obligatory 760ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 718ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 267ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 687ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 454ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 641ms

And Login as "bausch-admin" 6s 392ms

And Go to "TRANSPORT_TABLE" 474ms

And Find transport in table with status "advice-added" 3s 627ms

And Confirm statuses until reach "on-the-way" 16s 850ms

And Open statuses popup 114ms

And Toggle status date confirmation checkbox 405ms

And Change status execution date to "1" days from today 2s 426ms

Then Verify that status cannot be confirmed 1s 191ms

Hooks

After Hooks.deleteTransportAfterTest() 873ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 238ms

After Hooks.deleteModeOfTransportationAfterTest() 333ms

After Hooks.rollbackTaskChanges() 189ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings @rollbackTaskChanges

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 290ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 162ms

And Mark custom fields as not obligatory 759ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 772ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 223ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 717ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 490ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 662ms

And Login as "bausch-admin" 6s 445ms

And Go to "TRANSPORT_TABLE" 489ms

And Find transport in table with status "advice-added" 3s 555ms

And Confirm statuses until reach "on-the-way" 16s 738ms

And Open statuses popup 149ms

And Toggle status date confirmation checkbox 420ms

And Change status execution date to "-1" days from today 2s 442ms

Then Verify that status cannot be confirmed 1s 218ms

Hooks

After Hooks.deleteTransportAfterTest() 907ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 217ms

After Hooks.deleteModeOfTransportationAfterTest() 340ms

After Hooks.rollbackTaskChanges() 203ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Confirmed statuses of existing orders should not be deleted - even after editing the order [A-6874]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 250ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 111ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 2s 020ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 946ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 122ms

When Login as "farmacol-admin" 6s 664ms

And Go to "TRANSPORT_TABLE" 511ms

And Confirm statuses until reach "during-unload" 16s 840ms

And Set actual confirmed transport status list 1s 968ms

And Disable task by API 181ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 963ms

And Edit transport hours and recalculate statuses 30s 696ms

Then Verify that all confirmed statuses are still on transport status list 457ms

Hooks

After Hooks.deleteTransportAfterTest() 796ms

After Hooks.rollbackAllCustomFieldsSettings() 348ms

After Hooks.rollbackTaskChanges() 192ms

View Feature Status confirmation

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest @rollbackAllCustomFieldsSettings @TmsLink=A-8004

Scenario Outline Check if timeliness alert is visible after checkpoint confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 682ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 172ms

And Mark custom fields as not obligatory 728ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 249ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 781ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 515ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "-30m" 4s 714ms

And Login as "super-admin-bausch" 6s 026ms

And Go to "TRANSPORT_TABLE" 528ms

Then Confirm next status and expect alert "Status potwierdzony z opóźnieniem" 1s 659ms

And Wait "1" seconds 1s

And Verify that note was added "Status potwierdzony po czasie" 1s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 862ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 071ms

After Hooks.deleteModeOfTransportationAfterTest() 322ms

View Feature Status confirmation

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest @rollbackAllCustomFieldsSettings @TmsLink=A-8004

Scenario Outline Check if timeliness alert is visible after checkpoint confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 749ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 173ms

And Mark custom fields as not obligatory 701ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 371ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 628ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 428ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "0m" 4s 748ms

And Login as "super-admin-bausch" 6s 008ms

And Go to "TRANSPORT_TABLE" 534ms

Then Confirm next status and expect alert "" 558ms

And Wait "1" seconds 1s

And Verify that note was added "" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 872ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 157ms

After Hooks.deleteModeOfTransportationAfterTest() 335ms

View Feature Status confirmation

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest @rollbackAllCustomFieldsSettings @TmsLink=A-8004

Scenario Outline Check if timeliness alert is visible after checkpoint confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 757ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 174ms

And Mark custom fields as not obligatory 754ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 213ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 626ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 502ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "30m" 4s 713ms

And Login as "super-admin-bausch" 6s 012ms

And Go to "TRANSPORT_TABLE" 513ms

Then Confirm next status and expect alert "Status potwierdzony przed czasem" 1s 648ms

And Wait "1" seconds 1s

And Verify that note was added "Status potwierdzony przed czasem" 1s 354ms

Hooks

After Hooks.deleteTransportAfterTest() 843ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 073ms

After Hooks.deleteModeOfTransportationAfterTest() 329ms

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

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

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

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

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 3s 007ms

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

When Reject status: Book of disinfection 216ms

And Check if reject date is visible 909ms

Then If user is login then logout 276ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 265ms

After Hooks.deleteTransportAfterTest() 754ms

After Hooks.rollbackWarehousesAccess() 765ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status twice and reject date is changing

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 845ms

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

When Reject status: Book of disinfection 224ms

And Check if reject date is visible 581ms

And Get rejection date 089ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 198ms

Then Check if reject date has changed 1s 214ms

Hooks

After Hooks.deleteTransportAfterTest() 757ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 436ms

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

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

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

When Reject status: Book of disinfection 227ms

Then Check if reject date is visible 571ms

Hooks

After Hooks.deleteTransportAfterTest() 907ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in statuses popup

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 465ms

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

And Open statuses popup 202ms

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

When Reject status: Book of disinfection 204ms

Then Open statuses popup 128ms

And Check if reject date is visible 411ms

Hooks

After Hooks.deleteTransportAfterTest() 777ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 10s 551ms

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

And Confirm to the last status by API 1s 718ms

When Find statuses for transport in table 3s 221ms

And Revoke statuses until reach "advice-added" 8s 041ms

Then Check if transport has "advice-added" 059ms

Hooks

After Hooks.deleteTransportAfterTest() 884ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 991ms

And Confirm to the last status by API 1s 511ms

When Find statuses for transport in table 2s 560ms

And Revoke statuses until reach "planned" 8s 112ms

Then Check if transport has "planned" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 857ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after created transport without advice, transport has checkpoints only from "preparation" section

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 6s 185ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 2s 015ms

When Find transport in table with status "new" 3s 654ms

And Open statuses popup 190ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 157ms

Hooks

After Hooks.deleteTransportAfterTest() 694ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after added advice, checkpoints are generated from "steps" section

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 2s 442ms

And Set "advice" inputs from JSON file "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 001ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 2s 004ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 276ms

And Set advice window in schedule 3s 615ms

And Fill advice form 17s 214ms

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

And Go to "TRANSPORT_TABLE" 512ms

When Find transport in table with status "advice-added" 3s 683ms

And Open statuses popup 204ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 154ms

Hooks

After Hooks.deleteTransportAfterTest() 773ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 257ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 108ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 942ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 759ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 123ms

When Login as "farmacol-admin" 2s 427ms

And Go to "TRANSPORT_TABLE" 534ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 11s 626ms

And Disable task by API 182ms

And Find transport pencil button in transports table 1s 646ms

And Click pencil and move transport to next day in schedule 23s 599ms

And Go to "TRANSPORT_TABLE" 541ms

Then Verify that "START_OF_UNLOADING" "is not" visible 416ms

Hooks

After Hooks.deleteTransportAfterTest() 771ms

After Hooks.rollbackAllCustomFieldsSettings() 392ms

After Hooks.rollbackTaskChanges() 237ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 1s 406ms

And Select warehouse "Serownia" 1s 595ms

And Set week view 1s 262ms

And Show yesterday 1s 163ms

And Move window into the past 451ms

Then Check if window is "red" 4s 073ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.nXQC78}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 9cf8c623213683dad42f700c3a1a1e2f
	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.getAttribute(RemoteWebElement.java:128)
	at Utils.TestUtil.elementHasColor(TestUtil.java:30)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:14)

Hooks

After Hooks.deleteTransportAfterTest() 940ms

After Hooks.rollbackAddedAuthorities() 135ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 409ms

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 196ms

When Go to "WAREHOUSE_TAB" 1s 442ms

And Select warehouse "Magazyn - Nowa Sól" 2s 117ms

And Set week view 1s 262ms

And Show yesterday 1s 183ms

And Move window into the past 593ms

Then Check if window is "red" 4s 076ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.nXQC78}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 9cf8c623213683dad42f700c3a1a1e2f
	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.getAttribute(RemoteWebElement.java:128)
	at Utils.TestUtil.elementHasColor(TestUtil.java:30)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:14)

Hooks

After Hooks.deleteTransportAfterTest() 802ms

After Hooks.rollbackAddedAuthorities() 129ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if time window resize with restriction to algorithm settings

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 1s 377ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 020ms

When Go to "WAREHOUSE_TAB" 1s 416ms

And Select warehouse "Magazyn Zimny Kaźmierz" 2s 121ms

And Set week view 1s 289ms

And Check if time window length is correct after "CREATE" 081ms

And Change number of pallets in transport 1m 2s 928ms

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

And Check if time window length is correct after "EDIT" 086ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 013ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get package type settings for transportType "UNLOAD" from "keeeper" 173ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;true" 239ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 672ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 873ms

When Go to "WAREHOUSE_TAB" 713ms

And Select warehouse "Magazyn Surowców" 1s 390ms

And Set week view 1s 263ms

Then Check if time window has proper "60" 069ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 136ms

After Hooks.clearAlgorithmSettings() 668ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 085ms

And Get package type settings for transportType "UNLOAD" from "keeeper" 139ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 225ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 615ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 989ms

When Go to "WAREHOUSE_TAB" 739ms

And Select warehouse "Magazyn Surowców" 1s 360ms

And Set week view 1s 195ms

Then Check if time window has proper "60" 063ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 065ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 138ms

After Hooks.clearAlgorithmSettings() 563ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length after advice is added with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get package type settings for transportType "LOAD" from "keeeper" 132ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 227ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 622ms

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

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

And Show all transport types 1s 162ms

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

And Set advice window in schedule 3s 269ms

And Fill advice form 18s 744ms

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

Then Check if time window has proper "30" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 708ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 140ms

After Hooks.clearAlgorithmSettings() 547ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length after advice is added with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 482ms

And Get package type settings for transportType "CONTAINER" from "keeeper" 118ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "20;false" 233ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 624ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 919ms

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

And Show all transport types 1s 164ms

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

And Set advice window in schedule 3s 254ms

And Fill advice form 18s 526ms

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

Then Check if time window has proper "60" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 779ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 140ms

After Hooks.clearAlgorithmSettings() 560ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings

Scenario Outline Check if supplier can change time window size by change number of pallets

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 815ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 221ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 16s 948ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 7s 714ms

When Go to transport details "DELIVERY" 30s 898ms

And Change filled value in details "number-of-pallets-step-0" "number" "25" "0" 1s 564ms

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

And Go to "WAREHOUSE_TAB" 1s 328ms

And Select warehouse "Serownia" 1s 589ms

And Set week view 1s 258ms

Then Check if time window has proper "60" 088ms

Hooks

After Hooks.deleteTransportAfterTest() 794ms

After Hooks.clearAlgorithmSettings() 870ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 126ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 174ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 386ms

And Go to "WAREHOUSE_TAB" 782ms

And Select warehouse "Magazyn Wyrobów Gotowych" 2s 054ms

And Go to next day in schedule 1s 210ms

And Check if time window counter value equals "1" 225ms

And Select view "DAYS_2" 2s 169ms

And Move advice window "2" 1s 495ms

And Select view "DAY" 2s 157ms

Then Check if time window counter value equals "0" 238ms

And Delete created transport by API 779ms

And Check if time window counter value equals "0" 160ms

And Click in free spot in schedule page to create gray window 485ms

And Check if time window counter value equals "0" 160ms

And Click in free spot in schedule page to create dedicated window 2s 139ms

And Check if time window counter value equals "0" 180ms

Hooks

After Hooks.deleteTransportAfterTest() 664ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "DELIVERY" 699ms

And Fill transport form 20s 680ms

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

And Set advice window in schedule 2s 364ms

And Check is transport created in schedule and set transport id 2s 658ms

And Go to "TRANSPORT_TABLE" 523ms

When Click on time window date 1s 703ms

And Open transport form when in schedule 1s 307ms

Then Check are transport values equals 2s 781ms

Hooks

After Hooks.deleteTransportAfterTest() 776ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-hochland" 000ms

When Go to new transport "DELIVERY" 740ms

And Fill transport form 46s 375ms

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

And Set advice window in schedule 2s 376ms

And Check is transport created in schedule and set transport id 3s 004ms

And Go to "TRANSPORT_TABLE" 590ms

When Click on time window date 1s 635ms

And Open transport form when in schedule 1s 451ms

Then Check are transport values equals 22s 168ms

Hooks

After Hooks.deleteTransportAfterTest() 737ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "CISTERN_DELIVERY" 739ms

And Fill transport form 48s 472ms

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

And Set advice window in schedule 2s 399ms

And Check is transport created in schedule and set transport id 2s 746ms

And Go to "TRANSPORT_TABLE" 510ms

When Click on time window date 3s 151ms

And Open transport form when in schedule 1s 474ms

Then Check are transport values equals 9s 212ms

Hooks

After Hooks.deleteTransportAfterTest() 894ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 000ms

When Go to new transport "CISTERN_COLLECTION" 670ms

And Fill transport form 34s 467ms

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

And Set advice window in schedule 2s 427ms

And Check is transport created in schedule and set transport id 2s 458ms

And Go to "TRANSPORT_TABLE" 515ms

When Click on time window date 3s 215ms

And Open transport form when in schedule 1s 369ms

Then Check are transport values equals 24s 139ms

Hooks

After Hooks.deleteTransportAfterTest() 759ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lantmannen" 000ms

When Go to new transport "DELIVERY" 697ms

And Fill transport form 45s 200ms

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

And Set advice window in schedule 2s 318ms

And Check is transport created in schedule and set transport id 2s 594ms

And Go to "TRANSPORT_TABLE" 457ms

When Click on time window date 1s 772ms

And Open transport form when in schedule 1s 333ms

Then Check are transport values equals 21s 932ms

Hooks

After Hooks.deleteTransportAfterTest() 964ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 455ms

And Set "transport" inputs from JSON file "CREATE_LOAD" "super-admin-lantmannen" 000ms

When Go to new transport "LOAD" 697ms

And Fill transport form 45s 283ms

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

And Set advice window in schedule 2s 380ms

And Check is transport created in schedule and set transport id 2s 696ms

And Go to "TRANSPORT_TABLE" 481ms

When Click on time window date 1s 747ms

And Open transport form when in schedule 1s 315ms

Then Check are transport values equals 22s 006ms

Hooks

After Hooks.deleteTransportAfterTest() 802ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if it is possible to add new warehouse step with new time window to existing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 244ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 404ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 403ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 357ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 907ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 973ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 6s 419ms

And Go to "TRANSPORT_TABLE" 511ms

When Go to transport details "EXTERNAL_DELIVERY" 3s 047ms

And Add step "unload" 222ms

And Change filled value in details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 832ms

And Change filled value in details "weight-step-2" "number" "23" "0" 1s 581ms

And Change filled value in details "number-of-pallets-step-2" "number" "23" "0" 1s 566ms

And Change filled value in details "time-range-from-date-2" "date" "" "0" 3s 744ms

Then Click "save-transport" save button 330ms

And Set advice window in schedule in "2" days 5s 706ms

And Click advice save button and wait for advice form to disappear 36s 670ms

And Go to "TRANSPORT_TABLE" 549ms

And Check if transport has "2" time windows 044ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 058ms

After Hooks.rollbackTransportTypeSettings() 297ms

After Hooks.rollbackAddedActionAuthorities() 375ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest @rollbackTaskSettings

Scenario Outline Check if window changes color properly in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 007ms

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 174ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 296ms

And Prepare task "REGISTRATION" setting "tracked" with value "false" for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 342ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 053ms

And Set double window advice 000ms

And Login as "farmacol-admin" 5s 883ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 4s 550ms

And Go to "TRANSPORT_TABLE" 365ms

And Get checkpoint colors for transport 030ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 1m 25s 123ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 145ms

After Hooks.rollbackTransportTypeSettings() 377ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest @rollbackTaskSettings

Scenario Outline Check if window changes color properly in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 227ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 146ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 331ms

And Prepare task "REGISTRATION" setting "tracked" with value "false" for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 275ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 077ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 606ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 4s 498ms

And Go to "TRANSPORT_TABLE" 422ms

And Get checkpoint colors for transport 021ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 1m 25s 236ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 070ms

After Hooks.rollbackTransportTypeSettings() 326ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest @rollbackTaskSettings @FLAKY

Scenario Outline Check if window changes color properly in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 253ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 167ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 269ms

And Prepare task "REGISTRATION" setting "tracked" with value "false" for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 261ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 140ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 690ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 4s 537ms

And Get checkpoint colors for transport 031ms

And Go to "TRANSPORT_TABLE" 379ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 25s 441ms

Error message

java.lang.AssertionError: Niepoprawna zmiana koloru przy statusie registered-katowice-przyjęcia
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:120)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:253)

Hooks

After Hooks.deleteTransportAfterTest() 1s 164ms

After Hooks.rollbackTransportTypeSettings() 328ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest @rollbackTaskSettings @FLAKY

Scenario Outline Check if window changes color properly in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 217ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 165ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 284ms

And Prepare task "REGISTRATION" setting "tracked" with value "false" for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 276ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 971ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 773ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 4s 539ms

And Get checkpoint colors for transport 025ms

And Go to "TRANSPORT_TABLE" 372ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 46s 259ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 021ms

After Hooks.rollbackTransportTypeSettings() 298ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if window is active after using "create similar" on that window [A-7009]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 2s 023ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 744ms

And Login as "super-admin-farmacol" 6s 092ms

And Show all transport types 1s 159ms

And Click on time window date 2s 060ms

Then Open transport form when in schedule 1s 442ms

And Click create similar button 15s 245ms

And Click cancel button in transport form 203ms

And Open transport form when in schedule 1s 374ms

Then Check if transport form modal is visible 100ms

Hooks

After Hooks.deleteTransportAfterTest() 745ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if min and max advice date changed after moving advice window [A-7503]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 859ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 765ms

And Get min and max advice date of created transport as "super-admin-farmacol" 438ms

And Login as "farmacol-admin" 2s 787ms

And Show all transport types 1s 162ms

And Click on time window date 2s 162ms

And Set week view 2s 654ms

And Move advice window "3" 1s 886ms

Then Check if min and max advice date changed after moving advice window as "super-admin-farmacol" 633ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 408ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if time window can not be moved in specified time before its start

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 197ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 830ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 483ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "60m" 4s 351ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 354ms

And Login as "super-admin-bausch" 6s 177ms

And Go to "WAREHOUSE_TAB" 1s 277ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 739ms

And Wait "2" seconds 2s

When Move window by interval "1h" 585ms

And Alert after moving is displayed "Nie można przesunąć okna czasowego - minął dopuszczalny czas na wykonanie tej akcji" 699ms

Hooks

After Hooks.deleteTransportAfterTest() 849ms

After Hooks.rollbackAddedActionAuthorities() 263ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if time window can not be moved in specified time before its start

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 169ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 645ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 474ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "180m" 4s 638ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 343ms

And Login as "super-admin-bausch" 5s 519ms

And Go to "WAREHOUSE_TAB" 1s 238ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 729ms

And Wait "2" seconds 2s

When Move window by interval "1h" 562ms

And Alert after moving is displayed "" 15s 085ms

Hooks

After Hooks.deleteTransportAfterTest() 876ms

After Hooks.rollbackAddedActionAuthorities() 313ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if time window can not be moved in specified time before its start

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 175ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 674ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 473ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "180m" 4s 608ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 365ms

And Login as "super-admin-bausch" 5s 457ms

And Go to "WAREHOUSE_TAB" 1s 402ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 666ms

And Wait "2" seconds 2s

When Move window by interval "-2h" 556ms

And Alert after moving is displayed "Nie można przesunąć okna czasowego - minął dopuszczalny czas na wykonanie tej akcji" 634ms

Hooks

After Hooks.deleteTransportAfterTest() 864ms

After Hooks.rollbackAddedActionAuthorities() 270ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 7s 191ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 017ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 251ms

And Set proper delay time to move order to archive after task timeout 145ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 108ms

And Go to "WAREHOUSE_TAB" 1s 001ms

And Change warehouse in schedule to: "Katowice" 1s 259ms

And Wait "60" seconds 1m

And Verify that transport window is grey 087ms

And Verify that transport is in archive 7s 351ms

Then Restore transport from archive 2s 713ms

And Verify that transport has been successfully restored 1s 749ms

Hooks

After Hooks.deleteTransportAfterTest() 790ms

After Hooks.rollbackSettings() 118ms

View Feature Move transport to archive

@deleteTransportAfterTest

Scenario Outline Check if removing a transport from the table moves it to the archive

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 4s 516ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 208ms

When Go to "TRANSPORT_TABLE" 406ms

And Delete transport 19s 634ms

When Go to "ARCHIVE_TAB" 556ms

And Show "OWN_COLLECTION" 199ms

And Verify that created transport is "true" in transport table 15s 137ms

Hooks

After Hooks.deleteTransportAfterTest() 533ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if confirming transport status removed it to the archive

Hooks

Before Hooks.showScenarioName(Scenario) 008ms

Steps

Given Set token of apiUsername "super-admin-dayco" 209ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 121ms

And Mark custom fields as not obligatory 013ms

And Login as "dayco-admin" 2s 144ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 068ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 132ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 196ms

When Go to "TRANSPORT_TABLE" 361ms

And Click button advice in transport table "OWN_COLLECTION" 1s 367ms

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 651ms

And Go to "TRANSPORT_TABLE" 374ms

And Find transport in table with status "planned-magazyn-tychy" 3s 698ms

And Confirm statuses until reach "process-ended" 16s 633ms

And Wait until transport disappear from transport table 22s 257ms

Then Go to "ARCHIVE_TAB" 494ms

And Show "OWN_COLLECTION" 194ms

And Verify that created transport is "true" in transport table 15s 152ms

Hooks

After Hooks.deleteTransportAfterTest() 713ms

After Hooks.rollbackAllCustomFieldsSettings() 558ms

After Hooks.rollbackSettings() 142ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

When Fill auction form 16s 159ms

Then Verify that the auction has been added to transport 129ms

Hooks

After Hooks.deleteTransportAfterTest() 615ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Fill auction form 16s 115ms

Then Verify that the auction has been added to transport 139ms

Hooks

After Hooks.deleteTransportAfterTest() 656ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept auction offer with minimum rate

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When If user is login then logout 286ms

And Login as "paa1-carrier@qa.qa-test" 4s 619ms

And Go to auction offer 1s 624ms

And Accept transport with minimum rate 16s 967ms

Then Check if carrier is assigned to transport 082ms

Hooks

After Hooks.deleteTransportAfterTest() 647ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When If user is login then logout 241ms

And Login as "paa1-carrier@qa.qa-test" 2s 674ms

And Go to auction offer 1s 655ms

And Reject auction offer 15s 802ms

Then Verify that offer has been removed from transport 15s 113ms

Hooks

After Hooks.deleteTransportAfterTest() 682ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When If user is login then logout 270ms

And Login as "pskza1-carrier@qa.qa-test" 6s 598ms

And Go to auction offer 2s 604ms

And Reject auction offer 15s 813ms

Then Verify that offer has been removed from transport 15s 099ms

Hooks

After Hooks.deleteTransportAfterTest() 647ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When If user is login then logout 268ms

And Login as "paa1-carrier@qa.qa-test" 2s 376ms

And Go to auction offer 1s 720ms

And Offer prize above maximum - "20000" 519ms

Then Verify that is not possible to add offer 838ms

Hooks

After Hooks.deleteTransportAfterTest() 648ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When If user is login then logout 277ms

And Login as "pskza1-carrier@qa.qa-test" 2s 610ms

And Go to auction offer 2s 770ms

And Offer prize above maximum - "20000" 527ms

Then Verify that is not possible to add offer 890ms

Hooks

After Hooks.deleteTransportAfterTest() 686ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Wait till auction end 1m 58s 015ms

Then Verify that is possible to add auction 125ms

Hooks

After Hooks.deleteTransportAfterTest() 627ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Wait till auction end 1m 58s 015ms

Then Verify that is possible to add auction 157ms

Hooks

After Hooks.deleteTransportAfterTest() 651ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to auction offer 1s 611ms

When Offer "1000" 465ms

Then Verify that offer with "1000" has been added to auction 3s 071ms

Hooks

After Hooks.deleteTransportAfterTest() 652ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to auction offer 1s 537ms

When Offer "1000" 432ms

Then Verify that offer with "1000" has been added to auction 3s 087ms

Hooks

After Hooks.deleteTransportAfterTest() 651ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke an offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to auction offer 1s 533ms

When Offer "1000" 496ms

And Verify that offer with "1000" has been added to auction 3s 085ms

Then Go to auction offer 1s 516ms

And Revoke current offer 752ms

And Verify that offer has been revoked 32s 935ms

Hooks

After Hooks.deleteTransportAfterTest() 621ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to offer more than last price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to auction offer 1s 558ms

When Offer "1000" 482ms

And Verify that offer with "1000" has been added to auction 3s 084ms

Then Go to auction offer 1s 509ms

And Offer "1500" 479ms

And Verify that offer with "1500" has been added to auction 3s 088ms

Hooks

After Hooks.deleteTransportAfterTest() 655ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to finish active auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to auction offer 1s 529ms

When Offer "1000" 487ms

And Verify that offer with "1000" has been added to auction 3s 068ms

Then Login as "swisskrono-admin" 2s 446ms

And Go to auction details 2s 196ms

And Finish active auction 145ms

And Verify that the transport has no active auction 691ms

Hooks

After Hooks.deleteTransportAfterTest() 617ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Go to auction offer 1s 548ms

When Offer "1000" 462ms

Then Verify that carrier can see current place in auction depending on the "true" role 834ms

Hooks

After Hooks.deleteTransportAfterTest() 646ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to auction offer 1s 515ms

When Offer "1000" 495ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 083ms

Hooks

After Hooks.deleteTransportAfterTest() 662ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to add offer below min price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to auction offer 1s 525ms

When Offer "300" 491ms

And Verify that carrier can't add offer to auction 095ms

Hooks

After Hooks.deleteTransportAfterTest() 681ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 000ms

When Go to auction form 1s 619ms

Then Verify carrier selection value "false" 158ms

Hooks

After Hooks.deleteTransportAfterTest() 576ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Hooks

Before Hooks.showScenarioName(Scenario) 011ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 590ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 266ms

And Show all transport "true" 134ms

When Go to auction form 1s 551ms

Then Verify carrier selection value "true" 144ms

Hooks

After Hooks.deleteTransportAfterTest() 695ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Open transport auction form 450ms

And Select all companies checkbox in transport auction form 180ms

And Unselect company "PAA2" in transport auction form 175ms

And Put transport on auction 15s 481ms

And Open transport auction history 212ms

And Open participants section in transport auction history 164ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 034ms

Hooks

After Hooks.deleteTransportAfterTest() 668ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Open transport auction form 598ms

And Select all companies checkbox in transport auction form 189ms

And Unselect company "PSKZA2" in transport auction form 158ms

And Put transport on auction 15s 371ms

And Open transport auction history 201ms

And Open participants section in transport auction history 143ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 684ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if "reason" field has validation error when passing to second carrier in auction [A-7573]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 2s 244ms

And Set transport on auction with "1000" and "1500" by JSON file as "super-admin-varrocrychvald" 2s 789ms

And Add a bid "1500" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 985ms

And Add a bid "1000" to an auction by JSON file as "pvra2-carrier-2" for "super-admin-varrocrychvald" 1s 073ms

When Login as "varrocrychvald-admin" and set token of apiUsername "super-admin-varrocrychvald" 4s 402ms

And Show all transport "true" 146ms

And Open transport auction history 1s 108ms

And Pass transport to "2" carrier in auction history 1s 283ms

Then Verify if "REASON" is visible in pass transport modal 078ms

And Confirm pass transport to carrier in pass transport modal 132ms

And Verify that "REASON" in pass transport modal has validation error 1s 067ms

Hooks

After Hooks.deleteTransportAfterTest() 644ms

View Feature Set transport order on auction

@deleteTransportAfterTest @TmsLink=A-7038

Scenario Outline Check if carriers can see correct position in auction [A-7038]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-varrocrychvald" 227ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 16s 179ms

And Set transport on auction with "100" and "300" by JSON file as "super-admin-varrocrychvald" 2s 761ms

And Add a bid "100" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 912ms

And Add a bid "200" to an auction by JSON file as "pvra2-carrier" for "super-admin-varrocrychvald" 961ms

And Add a bid "300" to an auction by JSON file as "pvra3-carrier" for "super-admin-varrocrychvald" 939ms

When Login as "pvra1-carrier" 3s 722ms

And Check if current position in auction is "1" 686ms

And If user is login then logout 247ms

And Login as "pvra2-carrier" 3s 832ms

And Check if current position in auction is "2" 643ms

And If user is login then logout 270ms

And Login as "pvra3-carrier" 4s 084ms

And Check if current position in auction is "3" 633ms

Hooks

After Hooks.deleteTransportAfterTest() 637ms

View Feature Set transport order on auction

@deleteTransportAfterTest @TMSLink=A-3739

Scenario Outline Check if transport is visible in transport table to auction participants only [A-3739]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Open transport auction form 433ms

And Select all companies checkbox in transport auction form 162ms

And Unselect company "PAA2" in transport auction form 150ms

And Put transport on auction 15s 412ms

When If user is login then logout 248ms

And Login as "paa1-carrier@qa.qa-test" 2s 566ms

And Show "TRANSPORT" 228ms

Then Check if transport is "visible" in table of transports 764ms

And If user is login then logout 248ms

And Login as "paa2-carrier@qa.qa-test" 4s 780ms

And Show "TRANSPORT" 226ms

And Check if transport is "not visible" in table of transports 15s 049ms

Hooks

After Hooks.deleteTransportAfterTest() 602ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 4s 915ms

And Set "transport" inputs from JSON file "CREATE_UNLOAD" "super-admin-pgf" 000ms

When Go to new transport "UNLOAD" 15s 520ms

And Fill transport form 32s 739ms

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

And Set advice window in schedule 2s 470ms

And Check is transport created in schedule and set transport id 2s 621ms

And Go to "TRANSPORT_TABLE" 525ms

And Go to transport details "UNLOAD" 30s 676ms

Then Check are transport values equals 26s 205ms

Hooks

After Hooks.deleteTransportAfterTest() 749ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "DELIVERY" 657ms

And Fill transport form 20s 663ms

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

And Set advice window in schedule 2s 380ms

And Check is transport created in schedule and set transport id 2s 517ms

And Go to "TRANSPORT_TABLE" 495ms

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

Then Check are transport values equals 2s 738ms

Hooks

After Hooks.deleteTransportAfterTest() 772ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "OWN_COLLECTION" 624ms

And Fill transport form 22s 866ms

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

And Set advice window in schedule 2s 404ms

And Check is transport created in schedule and set transport id 2s 487ms

And Go to "TRANSPORT_TABLE" 448ms

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

Then Check are transport values equals 2s 602ms

Hooks

After Hooks.deleteTransportAfterTest() 793ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 10s 060ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-hochland" 000ms

When Go to new transport "DELIVERY" 715ms

And Fill transport form 46s 393ms

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

And Set advice window in schedule 2s 386ms

And Check is transport created in schedule and set transport id 2s 952ms

And Go to "TRANSPORT_TABLE" 566ms

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

Then Check are transport values equals 22s 581ms

Hooks

After Hooks.deleteTransportAfterTest() 855ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 000ms

When Go to new transport "CISTERN_DELIVERY" 790ms

And Fill transport form 48s 402ms

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

And Set advice window in schedule 2s 425ms

And Check is transport created in schedule and set transport id 2s 679ms

And Go to "TRANSPORT_TABLE" 484ms

And Go to transport details "CISTERN_DELIVERY" 2s 904ms

Then Check are transport values equals 9s 111ms

Hooks

After Hooks.deleteTransportAfterTest() 894ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 000ms

When Go to new transport "CISTERN_COLLECTION" 655ms

And Fill transport form 34s 464ms

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

And Set advice window in schedule 2s 475ms

And Check is transport created in schedule and set transport id 2s 423ms

And Go to "TRANSPORT_TABLE" 515ms

And Go to transport details "CISTERN_COLLECTION" 3s 021ms

Then Check are transport values equals 24s 028ms

Hooks

After Hooks.deleteTransportAfterTest() 761ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "OWN_COLLECTION" 703ms

And Fill transport form 39s 694ms

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

And Set advice window in schedule 2s 407ms

And Check is transport created in schedule and set transport id 2s 818ms

And Go to "TRANSPORT_TABLE" 488ms

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

Then Check are transport values equals 22s 158ms

Hooks

After Hooks.deleteTransportAfterTest() 877ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 712ms

And Fill transport form 38s 968ms

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

And Set advice window in schedule 2s 412ms

And Check is transport created in schedule and set transport id 2s 602ms

And Go to "TRANSPORT_TABLE" 426ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 577ms

Then Check are transport values equals 6s 978ms

Hooks

After Hooks.deleteTransportAfterTest() 925ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_EXPORT" "super-admin-hochland" 000ms

When Go to new transport "EXPORT" 774ms

And Fill transport form 48s 103ms

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

And Set advice window in schedule 2s 370ms

And Check is transport created in schedule and set transport id 3s 002ms

And Go to "TRANSPORT_TABLE" 467ms

And Go to transport details "EXPORT" 2s 985ms

Then Check are transport values equals 7s 333ms

Hooks

After Hooks.deleteTransportAfterTest() 986ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 4s 829ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-skd" 000ms

When Go to new transport "DELIVERY" 15s 482ms

And Fill transport form 34s 312ms

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

And Set advice window in schedule 2s 332ms

And Check is transport created in schedule and set transport id 2s 468ms

And Go to "TRANSPORT_TABLE" 478ms

And Go to transport details "DELIVERY" 30s 606ms

Then Check are transport values equals 39s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 717ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lantmannen" 000ms

When Go to new transport "DELIVERY" 668ms

And Fill transport form 45s 080ms

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

And Set advice window in schedule 2s 324ms

And Check is transport created in schedule and set transport id 2s 579ms

And Go to "TRANSPORT_TABLE" 474ms

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

Then Check are transport values equals 22s 008ms

Hooks

After Hooks.deleteTransportAfterTest() 794ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 448ms

And Set "transport" inputs from JSON file "CREATE_LOAD" "super-admin-lantmannen" 000ms

When Go to new transport "LOAD" 653ms

And Fill transport form 45s 155ms

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

And Set advice window in schedule 2s 407ms

And Check is transport created in schedule and set transport id 2s 621ms

And Go to "TRANSPORT_TABLE" 529ms

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

Then Check are transport values equals 22s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 901ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "UNLOAD" 631ms

And Fill transport form 44s 522ms

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

And Set advice window in schedule 2s 358ms

And Check is transport created in schedule and set transport id 2s 703ms

And Go to "TRANSPORT_TABLE" 442ms

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

Then Check are transport values equals 24s 296ms

Hooks

After Hooks.deleteTransportAfterTest() 756ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "TANKER_GRANULATE_DELIVERY" 697ms

And Fill transport form 44s 530ms

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

And Set advice window in schedule 2s 416ms

And Check is transport created in schedule and set transport id 2s 769ms

And Go to "TRANSPORT_TABLE" 472ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 781ms

Then Check are transport values equals 24s 177ms

Hooks

After Hooks.deleteTransportAfterTest() 743ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-alrec" 000ms

When Go to new transport "DELIVERY" 659ms

And Fill transport form 28s 619ms

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

And Set advice window in schedule 2s 368ms

And Check is transport created in schedule and set transport id 2s 548ms

And Go to "TRANSPORT_TABLE" 444ms

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

Then Check are transport values equals 19s 736ms

Hooks

After Hooks.deleteTransportAfterTest() 827ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

When Go to new transport "WEIGHING" 636ms

And Fill "transport" form "CREATE_WEIGHING" by "super-admin-hochland" 16s 034ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 448ms

And Go to transport details "WEIGHING" 2s 995ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 516ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "TRANSPORT" 753ms

And Fill "transport" form "CREATE_TRANSPORT" by "super-admin-adama" 26s 998ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 368ms

And Go to transport details "TRANSPORT" 2s 934ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 570ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "CONTAINER" 681ms

And Fill "transport" form "CREATE_CONTAINER" by "super-admin-adama" 10s 129ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 450ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 513ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 668ms

And Fill "transport" form "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by "super-admin-hochland" 12s 269ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 429ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 3s 002ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 684ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "DELIVERY" 641ms

And Fill "transport" form "CREATE_DELIVERY" by "super-admin-piast" 22s 534ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 444ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 605ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "LOAD" 725ms

And Fill "transport" form "CREATE_LOAD" by "super-admin-piast" 26s 491ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 386ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 671ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "LOAD" 585ms

And Fill "transport" form "CREATE_LOAD" by "super-admin-keeeper" 24s 991ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 412ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 498ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "CONTAINER" 657ms

And Fill "transport" form "CREATE_CONTAINER" by "super-admin-keeeper" 25s 201ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 372ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 516ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "SMALLS_IMPORT" 772ms

And Fill "transport" form "CREATE_SMALLS_IMPORT" by "super-admin-skz" 19s 464ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 441ms

And Go to transport details "SMALLS_IMPORT" 2s 984ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 604ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "SMALLS_EXPORT" 813ms

And Fill "transport" form "CREATE_SMALLS_EXPORT" by "super-admin-skz" 38s 132ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 428ms

And Go to transport details "SMALLS_EXPORT" 2s 942ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 622ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 585ms

When Go to new transport "TRANSPORT_ORDER" 775ms

And Fill "transport" form "CREATE_TRANSPORT_ORDER" by "super-admin-alrec" 24s 225ms

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

And Show all transport "true" 191ms

And Go to "TRANSPORT_TABLE" 374ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 531ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "TRANSPORT" 715ms

And Fill "transport" form "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" by "super-admin-adama" 38s 801ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 405ms

And Go to transport details "TRANSPORT" 2s 977ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 585ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 512ms

When Go to new transport "INBOUND" 729ms

And Fill "transport" form "CREATE_INBOUND_WITHOUT_WAREHOUSES" by "super-admin-alrec" 43s 162ms

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

And Show all transport "true" 187ms

And Go to "TRANSPORT_TABLE" 394ms

And Go to transport details "INBOUND" 2s 862ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 546ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 6s 306ms

When Go to new transport "EXTERNAL_DELIVERY" 695ms

And Fill "transport" form "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" by "super-admin-farmacol" 57s 678ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 388ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 894ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 548ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 5s 921ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 498ms

And Fill "transport" form "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" by "dfa1-supplier" 50s 400ms

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

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 362ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 804ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 528ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 266ms

And Set "transport" inputs from JSON file "EDIT_UNLOAD" "super-admin-pgf" 000ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 359ms

And Show all transport "false" 000ms

When Go to transport details "UNLOAD" 30s 791ms

And Fill transport form 36s 146ms

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

And Go to transport details "UNLOAD" 30s 783ms

Then Check are transport values equals 6s 858ms

Hooks

After Hooks.deleteTransportAfterTest() 808ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Show all transport "false" 000ms

When Go to transport details "TRANSPORT" 2s 893ms

And Fill transport form 11s 311ms

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

And Go to transport details "TRANSPORT" 2s 950ms

Then Check are transport values equals 4s 388ms

Hooks

After Hooks.deleteTransportAfterTest() 565ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Show all transport "false" 000ms

When Go to transport details "CONTAINER" 2s 833ms

And Fill transport form 5s 166ms

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

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

Then Check are transport values equals 161ms

Hooks

After Hooks.deleteTransportAfterTest() 497ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 718ms

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 2s 794ms

And Fill transport form 15s 897ms

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

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

Then Check are transport values equals 2s 457ms

Hooks

After Hooks.deleteTransportAfterTest() 644ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 868ms

And Show all transport "false" 000ms

When Go to transport details "OWN_COLLECTION" 2s 819ms

And Fill transport form 26s 678ms

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

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

Then Check are transport values equals 4s 753ms

Hooks

After Hooks.deleteTransportAfterTest() 703ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 2s 944ms

And Fill transport form 42s 942ms

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

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

Then Check are transport values equals 13s 640ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION" "super-admin-hochland" 000ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 890ms

And Show all transport "false" 000ms

When Go to transport details "OWN_COLLECTION" 3s 042ms

And Fill transport form 43s 245ms

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

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

Then Check are transport values equals 9s

Hooks

After Hooks.deleteTransportAfterTest() 754ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_EXPORT" "super-admin-hochland" 000ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 133ms

And Show all transport "false" 000ms

When Go to transport details "EXPORT" 3s 080ms

And Fill transport form 55s 749ms

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

And Go to transport details "EXPORT" 2s 977ms

Then Check are transport values equals 11s 482ms

Hooks

After Hooks.deleteTransportAfterTest() 827ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 000ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 920ms

And Show all transport "false" 000ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 928ms

And Fill transport form 39s 843ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 799ms

Then Check are transport values equals 13s 395ms

Hooks

After Hooks.deleteTransportAfterTest() 579ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 700ms

And Show all transport "false" 000ms

When Go to transport details "CISTERN_DELIVERY" 2s 928ms

And Fill transport form 32s 832ms

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

And Go to transport details "CISTERN_DELIVERY" 2s 832ms

Then Check are transport values equals 8s 949ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 000ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 611ms

And Show all transport "false" 000ms

When Go to transport details "CISTERN_COLLECTION" 2s 948ms

And Fill transport form 31s 283ms

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

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

Then Check are transport values equals 8s 876ms

Hooks

After Hooks.deleteTransportAfterTest() 771ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_WEIGHING" "super-admin-hochland" 000ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 216ms

And Show all transport "false" 000ms

When Go to transport details "WEIGHING" 2s 881ms

And Fill transport form 16s 527ms

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

And Go to transport details "WEIGHING" 2s 774ms

Then Check are transport values equals 4s 518ms

Hooks

After Hooks.deleteTransportAfterTest() 530ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 000ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 886ms

And Show all transport "false" 000ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 038ms

And Fill transport form 41s 660ms

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

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 868ms

Then Check are transport values equals 9s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 770ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 563ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 646ms

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 30s 699ms

And Fill transport form 30s 756ms

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

And Go to transport details "DELIVERY" 30s 663ms

Then Check are transport values equals 4s 698ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 940ms

And Show all transport "false" 000ms

When Go to transport details "LOAD" 2s 995ms

And Fill transport form 1m 3s 150ms

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

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

Then Check are transport values equals 26s 368ms

Hooks

After Hooks.deleteTransportAfterTest() 642ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 613ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-lantmannen" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 831ms

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 2s 862ms

And Fill transport form 17s 989ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 219ms

And Go to transport details "DELIVERY" 2s 778ms

Then Check are transport values equals 229ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 416ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-lantmannen" 000ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 858ms

And Show all transport "false" 000ms

When Go to transport details "LOAD" 2s 817ms

And Fill transport form 34s 240ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 253ms

And Go to transport details "LOAD" 2s 752ms

Then Check are transport values equals 4s 808ms

Hooks

After Hooks.deleteTransportAfterTest() 806ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 525ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-keeeper" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 869ms

And Show all transport "false" 000ms

When Go to transport details "UNLOAD" 2s 925ms

And Fill transport form 43s 442ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 244ms

And Go to transport details "UNLOAD" 2s 846ms

Then Check are transport values equals 9s 198ms

Hooks

After Hooks.deleteTransportAfterTest() 778ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 567ms

And Set "transport" inputs from JSON file "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 000ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 971ms

And Show all transport "false" 000ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 985ms

And Fill transport form 43s 373ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 236ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 828ms

Then Check are transport values equals 9s 189ms

Hooks

After Hooks.deleteTransportAfterTest() 823ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 561ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 000ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 967ms

And Show all transport "false" 000ms

When Go to transport details "LOAD" 2s 856ms

And Fill transport form 28s 627ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 232ms

And Go to transport details "LOAD" 2s 732ms

Then Check are transport values equals 4s 612ms

Hooks

After Hooks.deleteTransportAfterTest() 501ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 492ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-keeeper" 000ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 856ms

And Show all transport "false" 000ms

When Go to transport details "CONTAINER" 2s 808ms

And Fill transport form 28s 613ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 232ms

And Go to transport details "CONTAINER" 2s 757ms

Then Check are transport values equals 4s 649ms

Hooks

After Hooks.deleteTransportAfterTest() 518ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 841ms

And Set "transport" inputs from JSON file "EDIT_SMALLS_EXPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 161ms

And Show all transport "false" 000ms

When Go to transport details "SMALLS_EXPORT" 2s 918ms

And Fill transport form 36s 313ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 305ms

And Go to transport details "SMALLS_EXPORT" 2s 862ms

Then Check are transport values equals 9s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 604ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 530ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-alrec" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 789ms

And Show all transport "true" 146ms

When Go to transport details "DELIVERY" 2s 784ms

And Fill transport form 25s 010ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 201ms

And Go to transport details "DELIVERY" 2s 753ms

Then Check are transport values equals 2s 534ms

Hooks

After Hooks.deleteTransportAfterTest() 694ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 484ms

And Set "transport" inputs from JSON file "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 000ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 205ms

And Show all transport "true" 141ms

When Go to transport details "TRANSPORT_ORDER" 2s 851ms

And Fill transport form 29s 683ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 194ms

And Go to transport details "TRANSPORT_ORDER" 2s 902ms

Then Check are transport values equals 2s 703ms

Hooks

After Hooks.deleteTransportAfterTest() 561ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-warehouseman" and set token of apiUsername "super-admin-keeeper" 6s 316ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 000ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 912ms

And Show all transport "false" 000ms

When Go to transport details "CONTAINER" 2s 892ms

And Fill transport form 11s 161ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 206ms

And Go to transport details "CONTAINER" 2s 768ms

Then Check are transport values equals 4s 392ms

Hooks

After Hooks.deleteTransportAfterTest() 540ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 117ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 192ms

And Show all transport "false" 000ms

When Delete transport 21s 406ms

Then Transport not displayed in table of transports 15s 092ms

Hooks

After Hooks.deleteTransportAfterTest() 694ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 589ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 022ms

And Show all transport "false" 000ms

When Delete transport 21s 102ms

Then Transport not displayed in table of transports 15s 125ms

Hooks

After Hooks.deleteTransportAfterTest() 528ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 630ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 889ms

And Show all transport "false" 000ms

When Delete transport 20s 735ms

Then Transport not displayed in table of transports 15s 068ms

Hooks

After Hooks.deleteTransportAfterTest() 11s 320ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 608ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 953ms

And Show all transport "false" 000ms

When Delete transport 18s 313ms

Then Transport not displayed in table of transports 15s 101ms

Hooks

After Hooks.deleteTransportAfterTest() 494ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 792ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 178ms

And Show all transport "false" 000ms

When Delete transport 18s 577ms

Then Transport not displayed in table of transports 15s 099ms

Hooks

After Hooks.deleteTransportAfterTest() 556ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 813ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 173ms

And Show all transport "false" 000ms

When Delete transport 18s 667ms

Then Transport not displayed in table of transports 15s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 537ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 665ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 739ms

And Show all transport "true" 157ms

When Delete transport 19s 534ms

Then Transport not displayed in table of transports 15s 133ms

Hooks

After Hooks.deleteTransportAfterTest() 693ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 541ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 234ms

And Show all transport "true" 171ms

When Delete transport 19s 131ms

Then Transport not displayed in table of transports 15s 084ms

Hooks

After Hooks.deleteTransportAfterTest() 536ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 447ms

And Set "transport" inputs from JSON file "EDIT_UNLOAD" "super-admin-pgf" 000ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 438ms

And Show all transport "false" 000ms

When Go to transport details "UNLOAD" 30s 761ms

And Fill transport form 36s 134ms

And Click "save-transport" save button 4s 309ms

And Click cancel button in transport form 196ms

And Go to transport details "UNLOAD" 30s 615ms

Then Check are transport values equals 6s 829ms

Hooks

After Hooks.deleteTransportAfterTest() 759ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 714ms

And Set "transport" inputs from JSON file "EDIT_TRANSPORT" "super-admin-adama" 000ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 069ms

And Show all transport "false" 000ms

When Go to transport details "TRANSPORT" 2s 977ms

And Fill transport form 11s 261ms

And Click "save-transport" save button 2s 041ms

And Click cancel button in transport form 188ms

And Go to transport details "TRANSPORT" 2s 811ms

Then Check are transport values equals 4s 424ms

Hooks

After Hooks.deleteTransportAfterTest() 560ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 564ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 000ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 872ms

And Show all transport "false" 000ms

When Go to transport details "CONTAINER" 2s 895ms

And Fill transport form 5s 173ms

And Click "save-transport" save button 1s 457ms

And Click cancel button in transport form 156ms

And Go to transport details "CONTAINER" 2s 799ms

Then Check are transport values equals 144ms

Hooks

After Hooks.deleteTransportAfterTest() 559ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 578ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-adama" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 754ms

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 2s 811ms

And Fill transport form 15s 778ms

And Click "save-transport" save button 2s 621ms

And Click cancel button in transport form 180ms

And Go to transport details "DELIVERY" 2s 787ms

Then Check are transport values equals 2s 539ms

Hooks

After Hooks.deleteTransportAfterTest() 672ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 663ms

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION" "super-admin-adama" 000ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 765ms

And Show all transport "false" 000ms

When Go to transport details "OWN_COLLECTION" 2s 924ms

And Fill transport form 26s 769ms

And Click "save-transport" save button 2s 603ms

And Click cancel button in transport form 179ms

And Go to transport details "OWN_COLLECTION" 2s 743ms

Then Check are transport values equals 4s 764ms

Hooks

After Hooks.deleteTransportAfterTest() 752ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 124ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 116ms

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 2s 948ms

And Fill transport form 43s 206ms

And Click "save-transport" save button 2s 742ms

And Click cancel button in transport form 290ms

And Go to transport details "DELIVERY" 2s 780ms

Then Check are transport values equals 13s 667ms

Hooks

After Hooks.deleteTransportAfterTest() 887ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 144ms

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION" "super-admin-hochland" 000ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 920ms

And Show all transport "false" 000ms

When Go to transport details "OWN_COLLECTION" 3s 047ms

And Fill transport form 43s 306ms

And Click "save-transport" save button 2s 825ms

And Click cancel button in transport form 189ms

And Go to transport details "OWN_COLLECTION" 2s 856ms

Then Check are transport values equals 9s 209ms

Hooks

After Hooks.deleteTransportAfterTest() 863ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 089ms

And Set "transport" inputs from JSON file "EDIT_EXPORT" "super-admin-hochland" 000ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 073ms

And Show all transport "false" 000ms

When Go to transport details "EXPORT" 3s 078ms

And Fill transport form 56s 369ms

And Click "save-transport" save button 2s 773ms

And Click cancel button in transport form 202ms

And Go to transport details "EXPORT" 2s 849ms

Then Check are transport values equals 11s 439ms

Hooks

After Hooks.deleteTransportAfterTest() 885ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 226ms

And Set "transport" inputs from JSON file "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 000ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 945ms

And Show all transport "false" 000ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 957ms

And Fill transport form 39s 381ms

And Click "save-transport" save button 2s 310ms

And Click cancel button in transport form 186ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 760ms

Then Check are transport values equals 13s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 609ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 195ms

And Set "transport" inputs from JSON file "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 795ms

And Show all transport "false" 000ms

When Go to transport details "CISTERN_DELIVERY" 2s 945ms

And Fill transport form 32s 887ms

And Click "save-transport" save button 2s 600ms

And Click cancel button in transport form 206ms

And Go to transport details "CISTERN_DELIVERY" 2s 804ms

Then Check are transport values equals 8s 929ms

Hooks

After Hooks.deleteTransportAfterTest() 828ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 160ms

And Set "transport" inputs from JSON file "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 000ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 642ms

And Show all transport "false" 000ms

When Go to transport details "CISTERN_COLLECTION" 2s 981ms

And Fill transport form 31s 281ms

And Click "save-transport" save button 2s 595ms

And Click cancel button in transport form 182ms

And Go to transport details "CISTERN_COLLECTION" 2s 809ms

Then Check are transport values equals 8s 853ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 467ms

And Set "transport" inputs from JSON file "EDIT_WEIGHING" "super-admin-hochland" 000ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 201ms

And Show all transport "false" 000ms

When Go to transport details "WEIGHING" 2s 957ms

And Fill transport form 16s 622ms

And Click "save-transport" save button 2s 051ms

And Click cancel button in transport form 180ms

And Go to transport details "WEIGHING" 2s 736ms

Then Check are transport values equals 4s 515ms

Hooks

After Hooks.deleteTransportAfterTest() 488ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 262ms

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 000ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 830ms

And Show all transport "false" 000ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 013ms

And Fill transport form 41s 673ms

And Click "save-transport" save button 2s 668ms

And Click cancel button in transport form 198ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 791ms

Then Check are transport values equals 9s 137ms

Hooks

After Hooks.deleteTransportAfterTest() 852ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 575ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-skd" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 667ms

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 30s 871ms

And Fill transport form 30s 674ms

And Click "save-transport" save button 1s 994ms

And Click cancel button in transport form 180ms

And Go to transport details "DELIVERY" 30s 625ms

Then Check are transport values equals 4s 666ms

Hooks

After Hooks.deleteTransportAfterTest() 758ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 669ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-piast" 000ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 935ms

And Show all transport "false" 000ms

When Go to transport details "LOAD" 2s 972ms

And Fill transport form 1m 2s 953ms

And Click "save-transport" save button 2s 703ms

And Click cancel button in transport form 178ms

And Go to transport details "LOAD" 2s 941ms

Then Check are transport values equals 26s 164ms

Hooks

After Hooks.deleteTransportAfterTest() 662ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 548ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-lantmannen" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 902ms

And Show all transport "false" 000ms

When Go to transport details "DELIVERY" 3s 007ms

And Fill transport form 17s 963ms

And Click "save-transport" save button 2s 067ms

And Click cancel button in transport form 167ms

And Go to transport details "DELIVERY" 2s 779ms

Then Check are transport values equals 218ms

Hooks

After Hooks.deleteTransportAfterTest() 781ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 443ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-lantmannen" 000ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 872ms

And Show all transport "false" 000ms

When Go to transport details "LOAD" 2s 832ms

And Fill transport form 34s 153ms

And Click "save-transport" save button 4s 336ms

And Click cancel button in transport form 206ms

And Go to transport details "LOAD" 2s 706ms

Then Check are transport values equals 4s 796ms

Hooks

After Hooks.deleteTransportAfterTest() 838ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 512ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-keeeper" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 939ms

And Show all transport "false" 000ms

When Go to transport details "UNLOAD" 2s 978ms

And Fill transport form 43s 190ms

And Click "save-transport" save button 2s 571ms

And Click cancel button in transport form 175ms

And Go to transport details "UNLOAD" 2s 794ms

Then Check are transport values equals 9s 157ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 671ms

And Set "transport" inputs from JSON file "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 000ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 998ms

And Show all transport "false" 000ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 891ms

And Fill transport form 43s 192ms

And Click "save-transport" save button 2s 611ms

And Click cancel button in transport form 170ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 769ms

Then Check are transport values equals 9s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 838ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 633ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 000ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 929ms

And Show all transport "false" 000ms

When Go to transport details "LOAD" 2s 845ms

And Fill transport form 28s 593ms

And Click "save-transport" save button 2s 030ms

And Click cancel button in transport form 140ms

And Go to transport details "LOAD" 2s 682ms

Then Check are transport values equals 4s 557ms

Hooks

After Hooks.deleteTransportAfterTest() 567ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 490ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-keeeper" 000ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 919ms

And Show all transport "false" 000ms

When Go to transport details "CONTAINER" 2s 893ms

And Fill transport form 28s 490ms

And Click "save-transport" save button 2s 009ms

And Click cancel button in transport form 137ms

And Go to transport details "CONTAINER" 2s 683ms

Then Check are transport values equals 4s 702ms

Hooks

After Hooks.deleteTransportAfterTest() 533ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 797ms

And Set "transport" inputs from JSON file "EDIT_SMALLS_IMPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 128ms

And Show all transport "false" 000ms

When Go to transport details "SMALLS_IMPORT" 2s 995ms

And Fill transport form 36s 264ms

And Click "save-transport" save button 2s 114ms

And Click cancel button in transport form 179ms

And Go to transport details "SMALLS_IMPORT" 2s 830ms

Then Check are transport values equals 9s 001ms

Hooks

After Hooks.deleteTransportAfterTest() 584ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 672ms

And Set "transport" inputs from JSON file "EDIT_SMALLS_EXPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 160ms

And Show all transport "false" 000ms

When Go to transport details "SMALLS_EXPORT" 2s 900ms

And Fill transport form 36s 257ms

And Click "save-transport" save button 2s 058ms

And Click cancel button in transport form 169ms

And Go to transport details "SMALLS_EXPORT" 2s 777ms

Then Check are transport values equals 8s 944ms

Hooks

After Hooks.deleteTransportAfterTest() 634ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 705ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-alrec" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 782ms

And Show all transport "true" 167ms

When Go to transport details "DELIVERY" 2s 880ms

And Fill transport form 24s 980ms

And Click "save-transport" save button 2s 590ms

And Click cancel button in transport form 179ms

And Go to transport details "DELIVERY" 2s 746ms

Then Check are transport values equals 2s 665ms

Hooks

After Hooks.deleteTransportAfterTest() 747ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 005ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 505ms

And Set "transport" inputs from JSON file "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 000ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 201ms

And Show all transport "true" 139ms

When Go to transport details "TRANSPORT_ORDER" 2s 878ms

And Fill transport form 29s 545ms

And Click "save-transport" save button 2s 060ms

And Click cancel button in transport form 160ms

And Go to transport details "TRANSPORT_ORDER" 2s 764ms

Then Check are transport values equals 2s 693ms

Hooks

After Hooks.deleteTransportAfterTest() 539ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if firstPossibleStart algorithm works properly when creating transport advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 630ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 951ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 1s 288ms

And If user is login then logout 282ms

Then Login as "dka1-supplier" 5s 784ms

And Click button advice in transport table "LOAD" 690ms

And Check if moved to first possible start date in schedule 1s 252ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 1m 31s 801ms

After Hooks.deleteTransportAfterTest() 526ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to create transport with new address [A-7158]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 234ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 000ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 717ms

Then Go to new transport "LOAD" 736ms

And Fill transport form 26s 023ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 241ms

And Go to "COMPANIES_TAB" 990ms

And Go to company "Dostawca Piast Automat 1" details 576ms

And Check if new address with "Adresat" is visible in company details 398ms

And Go to "TRANSPORT_TABLE" 549ms

And Go to transport details "LOAD" 2s 889ms

Hooks

After Hooks.deleteAddressAfterTest() 360ms

After Hooks.deleteTransportAfterTest() 622ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to weight again transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 299ms

And Set "transport" inputs from JSON file "CREATE_WEIGHING" "super-admin-hochland" 000ms

And Go to new transport "WEIGHING" 715ms

And Fill transport form 17s 626ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 156ms

And If user is login then logout 801ms

And Mock weighing by admin panel to "1234" tons 4s 807ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 976ms

And Go to transport details "WEIGHING" 3s 396ms

And Expand weighing panel 245ms

And Click weighing again entry button 2s 244ms

Then Verify if weight changed to "1234" 068ms

Hooks

After Hooks.deleteTransportAfterTest() 492ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 529ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 057ms

When Go to "TRANSPORT_TABLE" 359ms

And Show all transport types 1s 142ms

And Verify that transport has "0" files 079ms

Then Add file to transport by API 1s 806ms

And Verify that transport has "1" files 2s 438ms

Hooks

After Hooks.deleteTransportAfterTest() 506ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 553ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 952ms

When Go to "TRANSPORT_TABLE" 391ms

And Show all transport types 1s 162ms

And Verify that transport has "0" files 089ms

Then Add file to transport by API 1s 369ms

And Verify that transport has "1" files 285ms

Hooks

After Hooks.deleteTransportAfterTest() 542ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 823ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 234ms

When Go to "TRANSPORT_TABLE" 398ms

And Show all transport types 1s 141ms

And Verify that transport has "0" files 081ms

Then Add file to transport by API 1s 412ms

And Verify that transport has "1" files 476ms

Hooks

After Hooks.deleteTransportAfterTest() 884ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 470ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 957ms

When Go to "TRANSPORT_TABLE" 364ms

And Show all transport types 1s 133ms

And Verify that transport has "0" files 087ms

Then Add file to transport by API 1s 364ms

And Verify that transport has "1" files 547ms

Hooks

After Hooks.deleteTransportAfterTest() 533ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 375ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 952ms

And Delete transport 17s 996ms

When Go to "ARCHIVE_TAB" 532ms

And Show "DELIVERY" 131ms

And Verify that transport has "0" files 6s 232ms

Then Add file to transport 381ms

And Verify that transport has "1" files 1s 531ms

Hooks

After Hooks.deleteTransportAfterTest() 514ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 693ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 963ms

And Delete transport 18s 495ms

When Go to "ARCHIVE_TAB" 566ms

And Show "LOAD" 233ms

And Verify that transport has "0" files 4s 527ms

Then Add file to transport 420ms

And Verify that transport has "1" files 1s 596ms

Hooks

After Hooks.deleteTransportAfterTest() 509ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 076ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 068ms

And Delete transport 21s 471ms

When Go to "ARCHIVE_TAB" 605ms

And Show "DELIVERY" 146ms

And Verify that transport has "0" files 5s 110ms

Then Add file to transport 384ms

And Verify that transport has "1" files 1s 805ms

Hooks

After Hooks.deleteTransportAfterTest() 665ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 606ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 935ms

And Delete transport 18s 255ms

When Go to "ARCHIVE_TAB" 579ms

And Show "CONTAINER" 193ms

And Verify that transport has "0" files 3s 512ms

Then Add file to transport 364ms

And Verify that transport has "1" files 1s 493ms

Hooks

After Hooks.deleteTransportAfterTest() 534ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after carrier acceptance when the transport has been passed to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 284ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 965ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 690ms

And Accept transferred transport by Api 738ms

And Login as "paa1-carrier@qa.qa-test" 2s 511ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 927ms

Hooks

After Hooks.deleteTransportAfterTest() 563ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is automatically added to the transport after the transport has been passed to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 749ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 297ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 904ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 689ms

Hooks

After Hooks.deleteTransportAfterTest() 582ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after winning the auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 223ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 051ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 913ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 605ms

And Login as "paa1-carrier@qa.qa-test" 2s 528ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 809ms

Hooks

After Hooks.deleteTransportAfterTest() 631ms

View Feature Transport files

@deleteTransportAfterTest @FLAKY

Scenario Outline Check if it CMR documents are added to transport after creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 374ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 162ms

When Go to "TRANSPORT_TABLE" 352ms

And Show all transport "true" 134ms

Then Verify that transport has "1" CMR file 1s 608ms

Hooks

After Hooks.deleteTransportAfterTest() 590ms

View Feature Transport files

@deleteTransportAfterTest @FLAKY

Scenario Outline Check if it CMR documents are added to transport after creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 331ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 467ms

When Go to "TRANSPORT_TABLE" 352ms

And Show all transport "true" 138ms

Then Verify that transport has "2" CMR file 1s 639ms

Hooks

After Hooks.deleteTransportAfterTest() 638ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 459ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 416ms

When Go to "TRANSPORT_TABLE" 428ms

And Show all transport "true" 154ms

Then Verify that "CMR" document can be downloaded 18s 950ms

Hooks

After Hooks.deleteTransportAfterTest() 620ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 635ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 449ms

And Show all transport "true" 153ms

And Delete transport 19s 245ms

When Go to "ARCHIVE_TAB" 507ms

And Show "TRANSPORT_ORDER" 143ms

Then Verify that "CMR" document can be downloaded 20s 943ms

Hooks

After Hooks.deleteTransportAfterTest() 566ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 100ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 198ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 738ms

And Click pencil and move transport to next day in schedule 20s 810ms

Then Check if transport is in new location in schedule 2s 267ms

And Check if dates in transport form are correct 4s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 779ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 669ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 715ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 841ms

And Click pencil and move transport to next day in schedule 20s 500ms

Then Check if transport is in new location in schedule 2s 277ms

And Check if dates in transport form are correct 3s 842ms

Hooks

After Hooks.deleteTransportAfterTest() 689ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 589ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 907ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 780ms

And Click pencil and move transport to next day in schedule 21s 537ms

Then Check if transport is in new location in schedule 2s 292ms

And Check if dates in transport form are correct 4s 019ms

Hooks

After Hooks.deleteTransportAfterTest() 740ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 717ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 882ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 814ms

And Click pencil and move transport to next day in schedule 20s 565ms

Then Check if transport is in new location in schedule 2s 287ms

And Check if dates in transport form are correct 3s 914ms

Hooks

After Hooks.deleteTransportAfterTest() 761ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 504ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 985ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 835ms

And Click pencil and move transport to next day in schedule 20s 663ms

Then Check if transport is in new location in schedule 2s 271ms

And Check if dates in transport form are correct 3s 965ms

Hooks

After Hooks.deleteTransportAfterTest() 808ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 527ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 2s 979ms

And Show all transport "true" 210ms

When Find transport pencil button in transports table 1s 775ms

And Click pencil and move transport to next day in schedule 5s 460ms

Then Check if transport is in new location in schedule 2s 244ms

And Check if dates in transport form are correct 3s 920ms

Hooks

After Hooks.deleteTransportAfterTest() 764ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to add advice by advice button in transport table and edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 559ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 009ms

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 000ms

When Show all transport types 1s 151ms

And Click button advice in transport table "DELIVERY" 210ms

And Set advice window in schedule 3s 534ms

And Fill advice form 12s 895ms

And Click advice save button and wait for advice form to disappear 33s 178ms

And Go to "TRANSPORT_TABLE" 497ms

And Find transport pencil button in transports table 1s 771ms

And Click pencil and move transport to next day in schedule 22s 801ms

Then Check if transport is in new location in schedule 2s 288ms

And Check if dates in transport form are correct 4s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 090ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 128ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 743ms

And Click pencil and move transport to next day in schedule 20s 682ms

And Move advice window "3" 1s 533ms

Then Check if advice window is in new location 060ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 993ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 624ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 660ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 797ms

And Click pencil and move transport to next day in schedule 20s 480ms

And Move advice window "3" 1s 622ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 283ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 527ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 860ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 749ms

And Click pencil and move transport to next day in schedule 21s 430ms

And Move advice window "3" 1s 692ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 728ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 546ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 884ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 789ms

And Click pencil and move transport to next day in schedule 20s 568ms

And Move advice window "3" 1s 475ms

Then Check if advice window is in new location 066ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 638ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 809ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 921ms

And Show all transport "false" 000ms

When Find transport pencil button in transports table 1s 802ms

And Click pencil and move transport to next day in schedule 20s 624ms

And Move advice window "3" 1s 483ms

Then Check if advice window is in new location 059ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 555ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 487ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 759ms

And Show all transport "true" 141ms

When Find transport pencil button in transports table 1s 707ms

And Click pencil and move transport to next day in schedule 20s 298ms

And Move advice window "3" 1s 607ms

Then Check if advice window is in new location 056ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 255ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report custom fields are visible in proper section

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 342ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 170ms

And Go to transport details "DELIVERY" 2s 974ms

When Open section: "discrepancy-report-panel" 1s 246ms

Then Verify that no discrepancies found label is visible in discrepancy report section 184ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 672ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 255ms

Hooks

After Hooks.deleteTransportAfterTest() 920ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section will open with validation errors

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 044ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 129ms

And Go to transport details "DELIVERY" 2s 913ms

And Fill transport form 43s 073ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 178ms

When Go to transport details "DELIVERY" 2s 887ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 720ms

And Click "save-transport" save button 900ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 078ms

And Verify that discrepancy report section "not contains" validation errors 077ms

Hooks

After Hooks.deleteTransportAfterTest() 799ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 063ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 109ms

When Go to transport details "DELIVERY" 2s 930ms

Then Verify that discrepancy report section is available 084ms

And Open section: "discrepancy-report-panel" 1s 202ms

And Verify that generate new discrepancy report button is visible 118ms

Hooks

After Hooks.deleteTransportAfterTest() 902ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 880ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 877ms

When Go to transport details "OWN_COLLECTION" 3s 018ms

Then Verify that discrepancy report section is available 126ms

And Open section: "discrepancy-report-panel" 1s 262ms

And Verify that generate new discrepancy report button is visible 078ms

Hooks

After Hooks.deleteTransportAfterTest() 859ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 019ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 811ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 990ms

Then Verify that discrepancy report section is available 077ms

And Open section: "discrepancy-report-panel" 1s 147ms

And Verify that generate new discrepancy report button is visible 083ms

Hooks

After Hooks.deleteTransportAfterTest() 873ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 854ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 133ms

When Go to transport details "EXPORT" 3s

Then Verify that discrepancy report section is available 072ms

And Open section: "discrepancy-report-panel" 1s 143ms

And Verify that generate new discrepancy report button is visible 132ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 371ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 326ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 952ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 970ms

Then Verify that discrepancy report section is available 092ms

And Open section: "discrepancy-report-panel" 1s 235ms

And Verify that generate new discrepancy report button is visible 078ms

Hooks

After Hooks.deleteTransportAfterTest() 534ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 911ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 685ms

When Go to transport details "CISTERN_DELIVERY" 2s 844ms

Then Verify that discrepancy report section is not available 15s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 865ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 010ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 601ms

When Go to transport details "CISTERN_COLLECTION" 2s 957ms

Then Verify that discrepancy report section is not available 15s 071ms

Hooks

After Hooks.deleteTransportAfterTest() 861ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 899ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 221ms

When Go to transport details "WEIGHING" 2s 876ms

Then Verify that discrepancy report section is not available 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 613ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report is properly generated

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 116ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 121ms

When Go to "TRANSPORT_TABLE" 378ms

And Go to transport details "DELIVERY" 2s 949ms

And Change filled value in details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 876ms

And Change filled value in details "unloaded-stere" "text" "3" "0" 1s 522ms

And Open section: "discrepancy-report-panel" 1s 170ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 42s 922ms

And Fill discrepancy report section without closing the form 22s 127ms

And Generate discrepancy report 19s 892ms

And Download discrepancy report 361ms

Then Verify that discrepancy report file has correct values 16s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 853ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if edited discrepancy report is properly generated

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 102ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 128ms

When Go to "TRANSPORT_TABLE" 411ms

And Go to transport details "DELIVERY" 2s 960ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Fill transport form 43s 094ms

And Open section: "discrepancy-report-panel" 1s 164ms

And Fill discrepancy report section without closing the form 22s 247ms

And Generate discrepancy report 19s 925ms

And Download discrepancy report 312ms

And Verify that discrepancy report file has correct values 15s 604ms

And Fill edited discrepancy report section 18s 712ms

And Generate edited discrepancy report 4s 053ms

And Download discrepancy report 306ms

Then Verify that discrepancy report file has correct values 15s 586ms

Hooks

After Hooks.deleteTransportAfterTest() 917ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest @TmsLink=A-7987

Scenario Outline Check if it is not possible to confirm next status without filling required fields in status modal [A-7987]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 152ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 078ms

When Go to "TRANSPORT_TABLE" 404ms

And Confirm statuses until reach "during-unload" 11s 604ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 667ms

And Change filled value in details "insp.-accord.-with-ins." "select" "NIE" "0" 3s 813ms

And Check if next status is not possible to confirm in status confirmation modal 227ms

Hooks

After Hooks.deleteTransportAfterTest() 951ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if added step is saved with transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-piast" 244ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 348ms

And Get "LOAD" settings from "piast" 155ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 309ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 973ms

And Login as "piast-admin" 5s 365ms

And Go to "TRANSPORT_TABLE" 512ms

When Go to transport details "LOAD" 3s 026ms

And Add step "unload" 361ms

And Change filled value in details "company-step-2" "autocomplete" "DPA2" "0" 7s 234ms

And Change filled value in details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 992ms

Then Click "save-transport-and-close" save button and wait for form to disappear 30s 238ms

And Go to transport details "LOAD" 3s 025ms

And Verify that transport has "3" steps 041ms

Hooks

After Hooks.deleteTransportAfterTest() 526ms

After Hooks.rollbackTransportTypeSettings() 236ms

After Hooks.rollbackAddedActionAuthorities() 257ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if supplier can't edit time range for load and unload step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier-2@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 382ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 288ms

When Go to "TRANSPORT_TABLE" 508ms

And Go to transport details "SMALLS_IMPORT" 17s 387ms

Then Verify that user can't edit time range for load and unload 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 590ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 219ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 3s 147ms

And Login as "neuca-admin" 2s 152ms

And Go to "TRANSPORT_TABLE" 485ms

And Show all transport types 1s 281ms

When Go to transport details "DELIVERY" 2s 913ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 202ms

Hooks

After Hooks.deleteTransportAfterTest() 930ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 247ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 099ms

And Login as "hochland-admin" 4s 053ms

And Go to "TRANSPORT_TABLE" 403ms

And Show all transport types 1s 179ms

When Go to transport details "EXPORT" 3s 081ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 133ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 112ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackTransportTypeSettings

Scenario Outline Check if sum of number of pallets check message is displayed in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 335ms

And Get "DELIVERY" settings from "neuca" 294ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 421ms

And Login as "neuca-admin" 2s 492ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 16s 971ms

When Go to "TRANSPORT_TABLE" 669ms

And Go to transport details "DELIVERY" 3s 017ms

And Set number of pallets in "load" step in transport - "32" 263ms

And Check if number of pallets check message is not visible in transport form 15s 086ms

And Set number of pallets in "load" step in transport - "34" 337ms

Then Check if number of pallets check message is visible in transport form 096ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

After Hooks.rollbackTransportTypeSettings() 334ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if time range fields are required in new warehouse step

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 243ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 321ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 260ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 289ms

And Login as "farmacol-admin" 5s 862ms

And Go to new transport "EXTERNAL_DELIVERY" 675ms

And Add step "unload" 191ms

And Click "save-transport-and-close" save button 879ms

Then Verify that "time-range-from-date-2" has validation error 1s 066ms

Then Verify that "time-range-to-date-2" has validation error 1s 064ms

And Change filled value in details "time-range-from-date-2" "date" "" "0" 3s 732ms

And Click "save-transport-and-close" save button 857ms

And Verify that "time-range-from-date-2" has no validation error 063ms

And Verify that "time-range-to-date-2" has no validation error 061ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.rollbackTransportTypeSettings() 366ms

After Hooks.rollbackAddedActionAuthorities() 295ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if new step is added in proper column in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 243ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 331ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 007ms

When Login as "piast-admin" 5s 376ms

And Go to transport details "LOAD" 3s 124ms

And Set "transport" inputs from JSON file "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 000ms

And Add step "unload" 313ms

And Fill step data 16s 068ms

And Set "transport" inputs from JSON file "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 000ms

And Add step "load" 233ms

And Fill step data 5s 802ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 201ms

Then Go to transport details "LOAD" 3s 105ms

And Check if "unload" step is added as "3" step in transport form 094ms

And Check if "load" step is added as "4" step in transport form 095ms

Hooks

After Hooks.deleteTransportAfterTest() 517ms

After Hooks.rollbackAddedActionAuthorities() 269ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackRemovedActionAuthorities

Scenario Outline Check if step is draggable according to authority @A-6865

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 233ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 354ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 058ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 112ms

When Login as "super-admin-skz" 7s 688ms

And Go to transport details "SMALLS_EXPORT" 2s 949ms

And Check if step is draggable "LOAD" 180ms

And Check if step is not draggable "UNLOAD" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 633ms

After Hooks.rollbackAddedActionAuthorities() 272ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created without advice by similar button has correct values

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 000ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 669ms

When Go to new transport "SMALLS_IMPORT" 717ms

And Fill transport form 21s 406ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 206ms

And Show all transport "false" 000ms

And Go to transport details "SMALLS_IMPORT" 2s 955ms

And Click create similar button 15s 253ms

And Fill "transport" form "CREATE_SIMILAR_SMALLS_IMPORT" by "super-admin-skz" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 251ms

And Open similar transport details 482ms

Then Check are transport values equals 081ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu contact-person są niepoprawne, wartość na stronie:  wartość poprawna: osoba expected:<[osoba]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:123)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:263)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:239)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/TransportForm/TransportForm.feature:16)

Hooks

After Hooks.deleteSimilarTransportAfterTest() 589ms

After Hooks.deleteTransportAfterTest() 571ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created with advice by similar button has correct values

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 000ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 7s 940ms

When Go to new transport "DELIVERY" 750ms

And Fill transport form 42s 758ms

And Click "save-transport" save button and wait for form to disappear 30s 297ms

And Set advice window in schedule 2s 371ms

And Check is transport created in schedule and set transport id 3s 365ms

And Go to "TRANSPORT_TABLE" 521ms

And Go to transport details "DELIVERY" 2s 853ms

And Click create similar button 15s 274ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 13s 994ms

And Click "save-transport" save button and wait for form to disappear 30s 215ms

And Set advice window in schedule in "2" days 4s 527ms

And Go to "TRANSPORT_TABLE" 437ms

And Open similar transport details 2s 763ms

Then Check are transport values equals 26s 424ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 845ms

After Hooks.deleteTransportAfterTest() 837ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 000ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 2s 627ms

When Go to new transport "DELIVERY" 700ms

And Fill transport form 42s 785ms

And Click "save-transport" save button and wait for form to disappear 30s 211ms

And Set advice window in schedule 2s 405ms

And Check is transport created in schedule and set transport id 3s 328ms

And Go to "TRANSPORT_TABLE" 498ms

And Go to transport details "DELIVERY" 2s 895ms

And Click create similar button 15s 244ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 13s 909ms

And Click "save-transport" save button and wait for form to disappear 30s 237ms

And Set advice window in schedule in "2" days 4s 479ms

And Go to "TRANSPORT_TABLE" 432ms

And Open similar transport details 2s 686ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 065ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 921ms

After Hooks.deleteTransportAfterTest() 810ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible to show transport details print form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 769ms

And Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT_FOR_PRINT" "super-admin-skz" 000ms

When Go to new transport "SMALLS_IMPORT" 750ms

And Fill transport form 36s 343ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 267ms

And Go to transport details "SMALLS_IMPORT" 2s 985ms

And Go to transport print details form 3s 667ms

Then Check are transport values equals 8s 904ms

Hooks

After Hooks.deleteTransportAfterTest() 614ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 998ms

And Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 145ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 906ms

And Go to transport details "SMALLS_IMPORT" 2s 900ms

Then Verify that the transport can be edited 1s 358ms

And Close transport details 15s 241ms

And If user is login then logout 264ms

And Login as "pskza1-carrier@qa.qa-test" 2s 825ms

And Go to transport details "SMALLS_IMPORT" 3s 924ms

And Verify that the transport cannot be edited 31s 332ms

Hooks

After Hooks.deleteTransportAfterTest() 671ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 855ms

And Set "transport" inputs from JSON file "CREATE_SMALLS_EXPORT" "super-admin-skz" 002ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 136ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 830ms

And Go to transport details "SMALLS_EXPORT" 3s 025ms

Then Verify that the transport can be edited 2s 046ms

And Close transport details 15s 233ms

And If user is login then logout 310ms

And Login as "pskza1-carrier@qa.qa-test" 2s 898ms

And Go to transport details "SMALLS_EXPORT" 3s 892ms

And Verify that the transport cannot be edited 46s 900ms

Hooks

After Hooks.deleteTransportAfterTest() 609ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 846ms

And Set "transport" inputs from JSON file "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 435ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 846ms

And Go to transport details "SMALLS_IMPORT" 2s 825ms

Then Verify that the hidden data in transport are not visible 1s 131ms

And Close transport details 15s 197ms

And If user is login then logout 268ms

And Login as "swisskrono-admin" 2s 842ms

And Go to transport details "SMALLS_IMPORT" 3s 038ms

And Verify that the hidden data in transport are visible 1s 718ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 684ms

And Set "transport" inputs from JSON file "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 510ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 842ms

And Go to transport details "SMALLS_EXPORT" 2s 821ms

Then Verify that the hidden data in transport are not visible 1s 107ms

And Close transport details 15s 178ms

And If user is login then logout 274ms

And Login as "swisskrono-admin" 2s 967ms

And Go to transport details "SMALLS_EXPORT" 3s 073ms

And Verify that the hidden data in transport are visible 1s 651ms

Hooks

After Hooks.deleteTransportAfterTest() 652ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible use 'save' and 'save transport and close' buttons after editing transport and fill discrepancy report panel

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 037ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 166ms

When Go to transport details "DELIVERY" 2s 964ms

And Change filled value in details "unloaded-stere" "text" "3" "0" 1s 564ms

And Change filled value in details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 903ms

And Change filled value in details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 848ms

And Fill discrepancy report section without closing the form 22s 334ms

And Click "save-transport" save button 2s 716ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 277ms

And Check if transport details form is disappeared 15s 108ms

Hooks

After Hooks.deleteTransportAfterTest() 823ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can add description to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 229ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 316ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 1s 236ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 3s 236ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 10s 190ms

When Go to "TRANSPORT_TABLE" 493ms

And Go to transport details "DELIVERY" 2s 952ms

And Change filled value in details "transport-description" "text" "opis" "0" 1s 549ms

Then Verify that "transport-description" in transport has value "opis" 071ms

Hooks

After Hooks.deleteTransportAfterTest() 922ms

After Hooks.rollbackAddedActionAuthorities() 268ms

After Hooks.rollbackWarehousesAccess() 688ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can't add description to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 227ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 3s 157ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 354ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 622ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 8s 730ms

When Go to "TRANSPORT_TABLE" 501ms

And Go to transport details "DELIVERY" 2s 888ms

Then Verify that "transport-description" in transport form is disabled 094ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 225ms

After Hooks.rollbackRemovedActionAuthorities() 293ms

After Hooks.rollbackWarehousesAccess() 640ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 264ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 425ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 201ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 8s 954ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 459ms

And Go to transport details "DELIVERY" 3s 008ms

Then Verify that "CARRIER" in transport form is visible 095ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 058ms

After Hooks.rollbackAddedActionAuthorities() 392ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 234ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 349ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 124ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 823ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 376ms

And Go to transport details "TRANSPORT" 2s 965ms

Then Verify that "CARRIER" in transport form is visible 102ms

Hooks

After Hooks.deleteTransportAfterTest() 606ms

After Hooks.rollbackAddedActionAuthorities() 289ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 249ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 323ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 247ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 437ms

And Show all transport "true" 167ms

When Go to "TRANSPORT_TABLE" 353ms

And Go to transport details "TRANSPORT_ORDER" 2s 902ms

Then Verify that "CARRIER" in transport form is visible 124ms

Hooks

After Hooks.deleteTransportAfterTest() 631ms

After Hooks.rollbackAddedActionAuthorities() 269ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 236ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 352ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 130ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 8s 823ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 463ms

And Go to transport details "DELIVERY" 2s 940ms

Then Verify that "CARRIER" in transport form is not visible 15s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 759ms

After Hooks.rollbackRemovedActionAuthorities() 274ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 228ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 328ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 099ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 985ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 392ms

And Go to transport details "TRANSPORT" 2s 917ms

Then Verify that "CARRIER" in transport form is not visible 15s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 598ms

After Hooks.rollbackRemovedActionAuthorities() 275ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 235ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 338ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 180ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 362ms

And Show all transport "true" 172ms

When Go to "TRANSPORT_TABLE" 419ms

And Go to transport details "TRANSPORT_ORDER" 2s 927ms

Then Verify that "CARRIER" in transport form is not visible 15s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 607ms

After Hooks.rollbackRemovedActionAuthorities() 270ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 260ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 319ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 314ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 138ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 211ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 505ms

And Go to transport details "DELIVERY" 2s 921ms

Then Verify that "CARRIER" in transport form is not disabled 098ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 245ms

After Hooks.rollbackAddedActionAuthorities() 542ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 231ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 335ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 318ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 111ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 679ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 341ms

And Go to transport details "TRANSPORT" 2s 917ms

Then Verify that "CARRIER" in transport form is not disabled 097ms

Hooks

After Hooks.deleteTransportAfterTest() 636ms

After Hooks.rollbackAddedActionAuthorities() 559ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 237ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 317ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 310ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 209ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 238ms

And Show all transport "true" 164ms

When Go to "TRANSPORT_TABLE" 358ms

And Go to transport details "TRANSPORT_ORDER" 2s 922ms

Then Verify that "CARRIER" in transport form is not disabled 095ms

Hooks

After Hooks.deleteTransportAfterTest() 595ms

After Hooks.rollbackAddedActionAuthorities() 556ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 230ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 322ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 315ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 116ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 8s 707ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 492ms

And Go to transport details "DELIVERY" 2s 945ms

Then Verify that "CARRIER" in transport form is disabled 092ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 235ms

After Hooks.rollbackAddedActionAuthorities() 260ms

After Hooks.rollbackRemovedActionAuthorities() 295ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 241ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 326ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 063ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 112ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 633ms

And Show all transport "false" 000ms

When Go to "TRANSPORT_TABLE" 418ms

And Go to transport details "TRANSPORT" 2s 885ms

Then Verify that "CARRIER" in transport form is disabled 141ms

Hooks

After Hooks.deleteTransportAfterTest() 591ms

After Hooks.rollbackAddedActionAuthorities() 255ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 240ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 329ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 129ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 155ms

And Show all transport "true" 156ms

When Go to "TRANSPORT_TABLE" 423ms

And Go to transport details "TRANSPORT_ORDER" 2s 957ms

Then Verify that "CARRIER" in transport form is disabled 112ms

Hooks

After Hooks.deleteTransportAfterTest() 588ms

After Hooks.rollbackAddedActionAuthorities() 248ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if user can add description to archived transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-adama" 242ms

And Get custom field settings for "DELIVERY" transport type and "" company 112ms

And Mark custom fields as not obligatory 003ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 682ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 335ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 336ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 315ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 587ms

When Find transport in table with status "planned" 3s 737ms

And Confirm statuses until reach "process-ended" 11s 498ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 536ms

And Show "DELIVERY" 179ms

And Go to transport details "DELIVERY" 30s 697ms

And Change filled value in details "transport-description" "text" "opis" "0" 1s 560ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 236ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 30s 627ms

Then Verify that "transport-description" in transport has value "opis" 072ms

Hooks

After Hooks.deleteTransportAfterTest() 614ms

After Hooks.rollbackAllCustomFieldsSettings() 005ms

After Hooks.rollbackAddedActionAuthorities() 265ms

After Hooks.rollbackRemovedActionAuthorities() 551ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 10s 043ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 169ms

When Go to transport details "DELIVERY" 3s 005ms

And Fill transport form 43s 603ms

And Change filled value in details "driver-name" "text" "XXX ZZZ" "0" 1s 701ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 233ms

And Go to new transport "DELIVERY" 664ms

Then Verify that driver "XXX ZZZ" is in list 923ms

Hooks

After Hooks.deleteTransportAfterTest() 825ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if 'rate' field is visible in transport form with proper value and currency after passing transport to carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 3s 117ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 163ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 958ms

And If user is login then logout 319ms

And Login as "pskza1-carrier@qa.qa-test" 2s 927ms

Then Verify that the transport has been transferred 3s 437ms

And Accept or reject "accept" transferred transport 16s 588ms

And Go to transport details "SMALLS_IMPORT" 2s 916ms

And Verify that "transaction-price" in transport form is visible 126ms

And Verify that transaction price field has correct value 072ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 156ms

Hooks

After Hooks.deleteTransportAfterTest() 577ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if 'rate' field is visible in transport form with proper value and currency after passing transport to carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 794ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 169ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 746ms

And If user is login then logout 277ms

And Login as "pskza1-carrier@qa.qa-test" 2s 807ms

Then Verify that the transport has been transferred 3s 524ms

And Accept or reject "accept" transferred transport 16s 649ms

And Go to transport details "SMALLS_EXPORT" 2s 898ms

And Verify that "transaction-price" in transport form is visible 120ms

And Verify that transaction price field has correct value 077ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 179ms

Hooks

After Hooks.deleteTransportAfterTest() 548ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 227ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 115ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 070ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 000ms

When Login as "dayco-admin" 4s 334ms

And Click button advice in transport table "OWN_COLLECTION" 812ms

And Set advice window in schedule 3s 321ms

And Fill advice form 11s 597ms

And Click advice save button and wait for advice form to disappear 33s 304ms

And Go to "TRANSPORT_TABLE" 469ms

And Find transport in table with status "planned" 3s 737ms

And Confirm statuses until reach "on-the-area" 6s 253ms

And Go to transport details "OWN_COLLECTION" 2s 883ms

And Click create similar button 15s 259ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 7s 059ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 214ms

And Open similar transport details 512ms

Then Check if transport form modal is visible 085ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 580ms

After Hooks.deleteTransportAfterTest() 780ms

After Hooks.rollbackAllCustomFieldsSettings() 504ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 226ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 118ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 027ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 000ms

When Login as "dayco-admin" 4s 423ms

And Click button advice in transport table "OWN_COLLECTION" 789ms

And Set advice window in schedule 3s 264ms

And Fill advice form 11s 517ms

And Click advice save button and wait for advice form to disappear 33s 255ms

And Go to "TRANSPORT_TABLE" 451ms

And Find transport in table with status "planned" 3s 690ms

And Confirm statuses until reach "during-load" 11s 446ms

And Go to transport details "OWN_COLLECTION" 2s 868ms

And Click create similar button 15s 248ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 983ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 227ms

And Open similar transport details 496ms

Then Check if transport form modal is visible 070ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 503ms

After Hooks.deleteTransportAfterTest() 731ms

After Hooks.rollbackAllCustomFieldsSettings() 474ms

View Feature Transport form

@deleteTransportAfterTest @deleteCustomFieldAfterTest @rollbackWarehousesAccess

Scenario Outline Check if date and time custom field appeared in transport details after creating transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-lisner" 212ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lisner" 000ms

And Add access to the warehouse "Magazyn Dostaw Lisner Poznań" to the user "lisner-admin" by JSON file 1s 039ms

And Create custom field with "CREATE_DELIVERY_DATE_AND_TIME_CFD" by "super-admin-lisner" 2s 923ms

When Login as "lisner-admin" and set token of apiUsername "super-admin-lisner" 6s 181ms

And Go to new transport "DELIVERY" 694ms

And Fill transport form 33s 438ms

And Click "save-transport" save button and wait for form to disappear 30s 232ms

And Set advice window in schedule 2s 402ms

And Go to "TRANSPORT_TABLE" 458ms

And Show all transport types 1s 170ms

And Go to transport details "DELIVERY" 2s 733ms

Then Verify that "date-and-time" in transport form is visible 091ms

Hooks

After Hooks.deleteTransportAfterTest() 888ms

After Hooks.deleteCustomFieldAfterTest() 2s 630ms

After Hooks.rollbackWarehousesAccess() 780ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 8s 450ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 160ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 664ms

When Click invoice button 3s 334ms

And Set default invoice currency value 167ms

Then Check that default currency value in invoice form is "EUR" 146ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_IMPORT" and principal alias "swisskrono" 220ms

And Clear all cache 2s 424ms

And Login as "swisskrono-admin" 10s 938ms

And Go to "TRANSPORT_TABLE" 413ms

And Show all transport types 1s 184ms

And Click invoice button 638ms

Then Check that default currency value in invoice form is "USD" 160ms

Hooks

After Hooks.deleteTransportAfterTest() 783ms

After Hooks.rollbackInvoiceCurrency() 2s 217ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 10s 968ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 165ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 666ms

When Click invoice button 3s 462ms

And Set default invoice currency value 166ms

Then Check that default currency value in invoice form is "EUR" 138ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_EXPORT" and principal alias "swisskrono" 188ms

And Clear all cache 2s 123ms

And Login as "swisskrono-admin" 10s 663ms

And Go to "TRANSPORT_TABLE" 386ms

And Show all transport types 1s 190ms

And Click invoice button 822ms

Then Check that default currency value in invoice form is "USD" 166ms

Hooks

After Hooks.deleteTransportAfterTest() 771ms

After Hooks.rollbackInvoiceCurrency() 2s 313ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport details button is not shown

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 5s 914ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 804ms

And Show all transport types 1s 146ms

Then Check if transport number is visible "DELIVERY" 15s 155ms

And Check if transport details is not visible 15s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 742ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 15s 830ms

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 390ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 160ms

When Click on transport row 159ms

Then Verify if transport row is selected 094ms

Hooks

After Hooks.deleteTransportAfterTest() 978ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 6s 325ms

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 359ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 733ms

When Click on transport row 152ms

Then Verify if transport row is selected 076ms

Hooks

After Hooks.deleteTransportAfterTest() 826ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 5s 192ms

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 407ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 638ms

When Click on transport row 163ms

Then Verify if transport row is selected 068ms

Hooks

After Hooks.deleteTransportAfterTest() 803ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 5s 137ms

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 403ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 801ms

When Click on transport row 149ms

Then Verify if transport row is selected 082ms

Hooks

After Hooks.deleteTransportAfterTest() 862ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 7s 594ms

And Show all transport "false" 000ms

And Go to "TRANSPORT_TABLE" 365ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 834ms

When Click on transport row 152ms

Then Verify if transport row is selected 079ms

Hooks

After Hooks.deleteTransportAfterTest() 835ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 5s 889ms

And Show all transport "true" 160ms

And Go to "TRANSPORT_TABLE" 350ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 716ms

When Click on transport row 178ms

Then Verify if transport row is selected 077ms

Hooks

After Hooks.deleteTransportAfterTest() 833ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 242ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 041ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 619ms

Then Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 5s 142ms

And Show "TRANSPORT" 173ms

When Accept or reject "accept" transferred transport 18s 243ms

Then Verify that transport is accept or reject "accept" 084ms

Hooks

After Hooks.deleteTransportAfterTest() 562ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 240ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 106ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 612ms

Then Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 790ms

And Show "TRANSPORT" 166ms

When Accept or reject "reject" transferred transport 17s 300ms

Then Verify that transport is accept or reject "reject" 15s 110ms

Hooks

After Hooks.deleteTransportAfterTest() 579ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 236ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 183ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 665ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 9s 022ms

And Show "SMALLS_IMPORT" 154ms

When Accept or reject "accept" transferred transport 18s 466ms

Then Verify that transport is accept or reject "accept" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 562ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 230ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 139ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 621ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 837ms

And Show "SMALLS_IMPORT" 156ms

When Accept or reject "reject" transferred transport 18s 113ms

Then Verify that transport is accept or reject "reject" 15s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 580ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 233ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 159ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 631ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 810ms

And Show "SMALLS_EXPORT" 139ms

When Accept or reject "accept" transferred transport 18s 563ms

Then Verify that transport is accept or reject "accept" 068ms

Hooks

After Hooks.deleteTransportAfterTest() 587ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 242ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 164ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 635ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 806ms

And Show "SMALLS_EXPORT" 145ms

When Accept or reject "reject" transferred transport 18s 320ms

Then Verify that transport is accept or reject "reject" 15s 111ms

Hooks

After Hooks.deleteTransportAfterTest() 587ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 704ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 123ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 745ms

And If user is login then logout 249ms

And Login as "paa1-carrier@qa.qa-test" 3s 047ms

Then Verify that the transport has been transferred with "true" 1s 541ms

Hooks

After Hooks.deleteTransportAfterTest() 799ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 571ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 070ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 931ms

And If user is login then logout 299ms

And Login as "paa1-carrier@qa.qa-test" 2s 966ms

Then Verify that the transport has been transferred with "false" 1s 646ms

Hooks

After Hooks.deleteTransportAfterTest() 589ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 697ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 114ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 693ms

And If user is login then logout 312ms

And Login as "pskza1-carrier@qa.qa-test" 2s 905ms

Then Verify that the transport has been transferred 3s 470ms

Hooks

After Hooks.deleteTransportAfterTest() 781ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 725ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 145ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 797ms

And If user is login then logout 256ms

And Login as "pskza1-carrier@qa.qa-test" 3s 074ms

Then Verify that the transport has been transferred 3s 577ms

Hooks

After Hooks.deleteTransportAfterTest() 769ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier during auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 721ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 578ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 799ms

And Go to auction offer 1s 618ms

When Offer "1000" 472ms

And Verify that offer with "1000" has been added to auction 3s 075ms

And If user is login then logout 223ms

And Login as "swisskrono-admin" 2s 759ms

Then Go to auction details 1s 867ms

And Pass transport to carrier from auction details 1s 514ms

And If user is login then logout 6s 271ms

And Login as "pskza1-carrier@qa.qa-test" 2s 455ms

And Verify that the transport has been transferred 3s 322ms

Hooks

After Hooks.deleteTransportAfterTest() 831ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier when auction is finished

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 731ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 462ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 934ms

And Go to auction offer 1s 775ms

When Offer "1000" 442ms

And Verify that offer with "1000" has been added to auction 3s 090ms

And Wait till auction end 1m 52s 014ms

And If user is login then logout 273ms

Then Login as "swisskrono-admin" 2s 915ms

And Go to auction details 2s 263ms

And Pass transport to carrier from auction details 1s 636ms

And If user is login then logout 6s 267ms

And Login as "pskza1-carrier@qa.qa-test" 2s 361ms

And Verify that the transport has been transferred 3s 423ms

Hooks

After Hooks.deleteTransportAfterTest() 788ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if enabled carriers are shown in transport transfer select

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 706ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 150ms

And Go to "TRANSPORT_TABLE" 487ms

When Open transport transfer modal 1s 641ms

Then Verify that all enabled companies from "swisskrono" are shown in select 344ms

Hooks

After Hooks.deleteTransportAfterTest() 610ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest @rollbackRejectedSections

Scenario Outline Check if blocked carriers are shown as disabled in transport transfer select

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 260ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 822ms

And Login as "adama-admin" 2s 220ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 241ms

And Go to "TRANSPORT_TABLE" 435ms

When Open transport transfer modal 1s 595ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 253ms

Hooks

After Hooks.deleteTransportAfterTest() 609ms

After Hooks.rollbackRejectedSections() 490ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if transport is not visible to carrier after expiring of time to accept transport [A-7037]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 571ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 053ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 35s 405ms

And If user is login then logout 290ms

When Login as "paa1-carrier@qa.qa-test" 5s 339ms

And Verify that the transport has been transferred with "true" 1s 679ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 074ms

Hooks

After Hooks.deleteTransportAfterTest() 612ms

View Feature Assortment Group

@deleteTransportAfterTest

Scenario Outline Check if assortment group select is disabled when transport is during edition

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 552ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 351ms

When Go to "TRANSPORT_TABLE" 424ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 916ms

Then Check if new assortment group is disabled in transport form 070ms

Hooks

After Hooks.deleteTransportAfterTest() 907ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to advice transport after double cancellation.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 528ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 941ms

And Set "advice" inputs from JSON file "CREATE_ADVICE_CONTAINER" "super-admin-adama" 001ms

When Show all transport types 1s 153ms

And Click button advice in transport table "CONTAINER" 316ms

And Set advice window in schedule 3s 168ms

And Click button cancel in advice form 16s 129ms

And Set advice window in schedule 2s 366ms

And Click button cancel in advice form 16s 091ms

And Set advice window in schedule 2s 302ms

And Fill advice form 21s 929ms

And Click advice save button and wait for advice form to disappear 33s 820ms

And Go to "TRANSPORT_TABLE" 436ms

And Go to transport details "CONTAINER" 2s 869ms

Then Check are advice values equals 5s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 686ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer and retransfer transport to carrier

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 652ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-adama" 000ms

When Go to new transport "TRANSPORT" 706ms

And Fill transport form 28s 729ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 264ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 833ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 385ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 808ms

And Accept or reject "reject" transferred transport 17s 808ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 624ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 825ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 705ms

And Accept or reject "accept" transferred transport 18s 027ms

Then Verify that transport is accept or reject "accept" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 556ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest @FLAKY-A-7905 @FLAKY-A-6187

Scenario Outline Check if possible to edit transport after advice cancellation.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 756ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 000ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 010ms

When Show all transport types 1s 155ms

And Click button advice in transport table "DELIVERY" 269ms

And Set advice window in schedule 3s 393ms

And Click button cancel in advice form 16s 192ms

And Go to "TRANSPORT_TABLE" 444ms

When Go to transport details "DELIVERY" 2s 822ms

And Fill transport form 1m 8s 636ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 229ms

And Go to transport details "DELIVERY" 2s 880ms

Then Check are transport values equals 26s 363ms

Hooks

After Hooks.deleteTransportAfterTest() 688ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	4255	9	6	0	0	4270	422	9	431	7h 4m 12s 144ms	Failed

Tag Report