Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.123	18 sie 2021, 06:09

	Steps	Scenarios	Features
@deleteTransportAfterTest	4244	9	12	0	0	4265	423	9	432	7h 26m 55s 977ms	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" 5s 447ms

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

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 040ms

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

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

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

And Fill advice form 21s 957ms

And Click advice save button to check error message 182ms

Then Check if possible advice alert is displayed 072ms

Hooks

After Hooks.deleteTransportAfterTest() 555ms

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

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

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

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

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

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

And Fill advice form 13s 071ms

And Click advice save button to check error message 188ms

Then Check if possible advice alert is displayed 070ms

Hooks

After Hooks.deleteTransportAfterTest() 681ms

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

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

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 025ms

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

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

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

And Fill advice form 13s 002ms

And Click advice save button to check error message 207ms

Then Check if possible advice alert is displayed 071ms

Hooks

After Hooks.deleteTransportAfterTest() 512ms

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

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

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

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

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

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

And Fill advice form 18s 768ms

And Click advice save button to check error message 204ms

Then Check if possible advice alert is displayed 072ms

Hooks

After Hooks.deleteTransportAfterTest() 516ms

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

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

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

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

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

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

And Fill advice form 18s 756ms

And Click advice save button to check error message 210ms

Then Check if possible advice alert is displayed 071ms

Hooks

After Hooks.deleteTransportAfterTest() 548ms

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

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

And Show all transport types 1s 174ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 58s 823ms

And Go to "TRANSPORT_TABLE" 475ms

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

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

And Fill transport form 5s 178ms

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

And Expand advice panel 280ms

And Edit advice in transport details 17s 679ms

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

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

And Expand advice panel 220ms

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

Hooks

After Hooks.deleteTransportAfterTest() 751ms

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

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

And Show all transport types 1s 174ms

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

And Go to "TRANSPORT_TABLE" 497ms

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

When Go to transport details "DELIVERY" 2s 909ms

And Fill transport form 1m 8s 997ms

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

And Expand advice panel 272ms

And Edit advice in transport details 8s 218ms

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

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

And Expand advice panel 365ms

Then Check are advice values equals after edition 323ms

Hooks

After Hooks.deleteTransportAfterTest() 956ms

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

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

And Show all transport types 1s 155ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-piast" 50s 092ms

And Go to "TRANSPORT_TABLE" 435ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 022ms

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

And Fill transport form 1m 3s 571ms

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

And Expand advice panel 281ms

And Edit advice in transport details 8s 147ms

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

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

And Expand advice panel 469ms

Then Check are advice values equals after edition 331ms

Hooks

After Hooks.deleteTransportAfterTest() 894ms

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

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

And Show all transport types 1s 160ms

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

And Go to "TRANSPORT_TABLE" 439ms

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

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

And Fill transport form 28s 749ms

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

And Expand advice panel 273ms

And Edit advice in transport details 23s 698ms

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

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

And Expand advice panel 271ms

Then Check are advice values equals after edition 8s 964ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

View Feature Advice transport

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 006ms

Steps

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

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

And Show all transport types 1s 146ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-keeeper" 55s 508ms

And Go to "TRANSPORT_TABLE" 479ms

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

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

And Fill transport form 28s 767ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-keeeper" 024ms

And Expand advice panel 272ms

And Edit advice in transport details 23s 828ms

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

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

And Expand advice panel 296ms

Then Check are advice values equals after edition 8s 976ms

Hooks

After Hooks.deleteTransportAfterTest() 792ms

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

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

And Show all transport types 1s 170ms

And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 58s 091ms

And Go to "TRANSPORT_TABLE" 474ms

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

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

And Fill transport form 8s 599ms

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

And Expand advice panel 268ms

And Edit advice in transport details 19s 274ms

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

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

And Expand advice panel 258ms

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

Hooks

After Hooks.deleteTransportAfterTest() 863ms

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

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

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

When Show all transport types 1s 166ms

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

And Set advice window in schedule 3s 164ms

And Fill advice form 18s 324ms

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

And Go to "TRANSPORT_TABLE" 446ms

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

Then Check are advice values equals 2s 970ms

Hooks

After Hooks.deleteTransportAfterTest() 801ms

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" 11s 813ms

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

And Get inputs from database "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 023ms

When Show all transport types 1s 147ms

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

And Set advice window in schedule 7s 527ms

And Fill advice form 17s 176ms

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

And Go to "TRANSPORT_TABLE" 471ms

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

Then Check are advice values equals 4s 923ms

Hooks

After Hooks.deleteTransportAfterTest() 948ms

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

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

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

When Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 384ms

And Fill advice form 13s 056ms

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

And Go to "TRANSPORT_TABLE" 469ms

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

Then Check are advice values equals 2s 713ms

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:150)
	at ✽.Check are advice values equals(file:Features/Atom/Advice/AdviceTransport.feature:61)

Hooks

After Hooks.deleteTransportAfterTest() 785ms

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

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

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 018ms

When Show all transport types 1s 131ms

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

And Set advice window in schedule 3s 361ms

And Fill advice form 13s 117ms

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

And Go to "TRANSPORT_TABLE" 474ms

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

Then Check are advice values equals 2s 712ms

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:150)
	at ✽.Check are advice values equals(file:Features/Atom/Advice/AdviceTransport.feature:61)

Hooks

After Hooks.deleteTransportAfterTest() 810ms

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

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

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

When Show all transport types 1s 164ms

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

And Set advice window in schedule 3s 248ms

And Fill advice form 18s 704ms

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

And Go to "TRANSPORT_TABLE" 412ms

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

Then Check are advice values equals 5s 005ms

Hooks

After Hooks.deleteTransportAfterTest() 768ms

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

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

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 022ms

When Show all transport types 1s 165ms

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

And Set advice window in schedule 3s 236ms

And Fill advice form 18s 705ms

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

And Go to "TRANSPORT_TABLE" 404ms

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

Then Check are advice values equals 2s 722ms

Error message

java.lang.AssertionError: Wartości w formularzu w polu driver-language są niepoprawne, wartość na stronie:  wartość poprawna: PL
	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:150)
	at ✽.Check are advice values equals(file:Features/Atom/Advice/AdviceTransport.feature:61)

Hooks

After Hooks.deleteTransportAfterTest() 752ms

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

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 726ms

And Go to new transport "DELIVERY" 716ms

And Fill transport form 48s 388ms

And Select warehouse "Katowice" in step section "1" 976ms

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

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

Then Set advice window in schedule 2s 434ms

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

And Go to "TRANSPORT_TABLE" 504ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 886ms

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

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

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

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

And Accept transferred transport by Api 805ms

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

And Get inputs from database "ADVICE_TRANSPORT" "super-admin-adama" 034ms

When Show all transport types 1s 404ms

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

And Set advice window in schedule 3s 229ms

And Fill advice form 17s 127ms

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

And Go to "TRANSPORT_TABLE" 499ms

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

Then Check are advice values equals 4s 972ms

Hooks

After Hooks.deleteTransportAfterTest() 826ms

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

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

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

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

And Accept transferred transport by Api 883ms

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

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

When Show all transport types 1s 209ms

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

And Set advice window in schedule 3s 331ms

And Fill advice form 20s 382ms

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

And Go to "TRANSPORT_TABLE" 462ms

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

Then Check are advice values equals 5s 151ms

Hooks

After Hooks.deleteTransportAfterTest() 976ms

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

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

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

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

And Accept transferred transport by Api 739ms

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

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 032ms

When Show all transport types 1s 218ms

And Click button advice in transport table "SMALLS_EXPORT" 842ms

And Set advice window in schedule 3s 440ms

And Fill advice form 20s 434ms

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

And Go to "TRANSPORT_TABLE" 450ms

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

Then Check are advice values equals 5s 109ms

Hooks

After Hooks.deleteTransportAfterTest() 894ms

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

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

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

And Accept transferred transport by Api 711ms

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

When Show all transport types 1s 250ms

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

And Set week view 1s 964ms

And Show yesterday 1s 161ms

Then Check if advice restriction blockade windows are visible 051ms

Hooks

After Hooks.deleteTransportAfterTest() 586ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 16s 012ms

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

And Accept transferred transport by Api 697ms

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

When Show all transport types 1s 179ms

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

And Set week view 2s 448ms

And Show yesterday 1s 186ms

Then Check if advice restriction blockade windows are visible 469ms

Hooks

After Hooks.deleteTransportAfterTest() 629ms

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

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

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

And Accept transferred transport by Api 648ms

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

When Show all transport types 1s 197ms

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

And Set week view 2s 589ms

And Show yesterday 1s 178ms

Then Check if advice restriction blockade windows are visible 325ms

Hooks

After Hooks.deleteTransportAfterTest() 573ms

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

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

And Show all transport "false" 104ms

And Click on time window date 1s 681ms

And Select view "DAYS_4" 2s 167ms

And Move advice window "3" 1s 493ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 052ms

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

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

And Show all transport "false" 093ms

And Click on time window date 16s 158ms

And Select view "DAYS_4" 2s 150ms

And Move advice window "3" 1s 703ms

Then Check if advice window is in new location 075ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 491ms

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

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

And Show all transport "false" 085ms

And Click on time window date 15s 882ms

And Select view "DAYS_4" 2s 172ms

And Move advice window "3" 1s 578ms

Then Check if advice window is in new location 069ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 750ms

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

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

And Show all transport "false" 076ms

And Click on time window date 1s 919ms

And Select view "DAYS_4" 2s 158ms

And Move advice window "3" 1s 579ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 754ms

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

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

And Show all transport "false" 091ms

And Click on time window date 1s 769ms

And Select view "DAYS_4" 2s 161ms

And Move advice window "3" 1s 484ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 773ms

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

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

And Show all transport "true" 236ms

And Click on time window date 1s 822ms

And Select view "DAYS_4" 2s 168ms

And Move advice window "3" 1s 494ms

Then Check if advice window is in new location 063ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 312ms

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

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

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

When Show all transport types 1s 159ms

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

And Set advice window in schedule 3s 381ms

And Fill advice form 12s 991ms

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

And Go to "TRANSPORT_TABLE" 472ms

And Click on time window date 1s 862ms

And Select view "DAYS_4" 2s 184ms

And Move advice window "3" 1s 650ms

Then Check if advice window is in new location 067ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 560ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 976ms

View Feature Advice transport

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

And Go to "TRANSPORT_TABLE" 399ms

And Show all transport types 1s 148ms

And Click on time window date 1s 668ms

And Scroll to time window "adviceWindow" 140ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 3s 153ms

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

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

And Go to "TRANSPORT_TABLE" 419ms

And Show all transport types 1s 144ms

And Click on time window date 1s 894ms

And Scroll to time window "adviceWindow" 159ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 889ms

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

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

And Go to "TRANSPORT_TABLE" 428ms

And Show all transport types 1s 152ms

And Click on time window date 1s 702ms

And Scroll to time window "adviceWindow" 140ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 871ms

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

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

And Go to "TRANSPORT_TABLE" 575ms

And Show all transport types 1s 156ms

And Click on time window date 2s 522ms

And Scroll to time window "adviceWindow" 238ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 3s 256ms

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

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

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

When Show all transport types 1s 152ms

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

And Set advice window in schedule 3s 386ms

And Fill advice form 13s 049ms

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

And Go to "TRANSPORT_TABLE" 495ms

And Click on time window date 1s 832ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 3s 649ms

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

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 021ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 136ms

And Go to "WAREHOUSE_TAB" 1s 351ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 292ms

When Go to new transport "DELIVERY" 726ms

And Fill transport form 47s 331ms

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

And Click previous page button in browser 065ms

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

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 Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 024ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 964ms

And Go to "WAREHOUSE_TAB" 1s 267ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 398ms

When Go to new transport "DELIVERY" 720ms

And Fill transport form 47s 222ms

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

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

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

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

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

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

And Get inputs from database "ADVICE_TRANSPORT" "super-admin-adama" 017ms

When Show all transport types 1s 147ms

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

And Fill advice form 16s 303ms

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

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

And Open statuses popup 195ms

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() 560ms

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

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

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

And Login as "farmacol-admin" 6s 595ms

And Go to "WAREHOUSE_TAB" 1s 149ms

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

And Set week view 2s 765ms

And Move cursor over time window element 460ms

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

Hooks

After Hooks.deleteTransportAfterTest() 781ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 350ms

And Show all transport types 1s 135ms

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

And Fill advice form 12s 984ms

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

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

And Set advice window in schedule 3s 176ms

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

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

And Go to "TRANSPORT_TABLE" 471ms

And Show all transport types 1s 162ms

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

Then Check are advice values equals 4s 778ms

Hooks

After Hooks.deleteTransportAfterTest() 849ms

After Hooks.deleteModeOfTransportationAfterTest() 340ms

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

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

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

And Fill transport form 41s 267ms

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

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

And Set advice window in schedule 2s 422ms

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

Then Go to "OWN_COMPANY_TAB" 693ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 006ms

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 "daa1-supplier-3" and set token of apiUsername "super-admin-alrec" 4s 731ms

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

And Fill transport form 21s 186ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//li//span[text()='Magazyn Alrec Łódź'] | //li[text()='Magazyn Alrec Łódź' and @role='option']"}
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.Wp7ONc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e145d6961212f956fc0dcb269d0fc6f2
*** Element info: {Using=xpath, value=//li//span[text()='Magazyn Alrec Łódź'] | //li[text()='Magazyn Alrec Łódź' and @role='option']}
	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 CucumberTests.Transport.Transport.selectValue(Transport.java:231)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:216)
	at CucumberTests.Transport.Transport.fillFields(Transport.java:172)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:150)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:184)
	at ✽.Fill transport form(file:Features/Atom/Companies/CompanyResources.feature:8)

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

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

And Set advice window in schedule 000ms

And Check is transport created in schedule and set transport id 000ms

Then Go to "OWN_COMPANY_TAB" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

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" 6s 977ms

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

And Go to "SETTINGS_TAB" 958ms

When Go to "CONTAINER" transport type settings 753ms

And Go to custom fields settings 398ms

And Click add new custom field 438ms

And Fill custom field form 6s 837ms

And Click save button 153ms

And Click back to custom field settings button 313ms

And Set custom field id 3s 046ms

And Refresh page 2s 258ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 2s 867ms

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

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

And Go to "SETTINGS_TAB" 791ms

When Go to "LOAD" transport type settings 693ms

And Go to custom fields settings 441ms

And Click add new custom field 466ms

And Fill custom field form 6s 848ms

And Click save button 164ms

And Click back to custom field settings button 332ms

And Set custom field id 3s 319ms

And Refresh page 2s 231ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 3s 042ms

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" 16s 019ms

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

And Go to "SETTINGS_TAB" 921ms

When Go to "DELIVERY" transport type settings 607ms

And Go to custom fields settings 398ms

And Click add new custom field 443ms

And Fill custom field form 6s 892ms

And Click save button 143ms

And Click back to custom field settings button 317ms

And Set custom field id 6s 176ms

And Refresh page 2s 296ms

Then Go to new transport "DELIVERY" 8s 043ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 5s 888ms

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

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

And Go to "SETTINGS_TAB" 800ms

When Go to "CONTAINER" transport type settings 725ms

And Go to custom fields settings 400ms

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

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

And Click save button 148ms

And Refresh page 2s 266ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 2s 922ms

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

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

And Go to "SETTINGS_TAB" 681ms

When Go to "LOAD" transport type settings 742ms

And Go to custom fields settings 438ms

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

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

And Click save button 150ms

And Refresh page 2s 234ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 3s 104ms

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

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

And Go to "SETTINGS_TAB" 976ms

When Go to "DELIVERY" transport type settings 587ms

And Go to custom fields settings 404ms

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

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

And Click save button 151ms

And Refresh page 2s 269ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 5s 906ms

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

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

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

When Go to "TRANSPORT_TABLE" 497ms

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

And Show all transport types 1s 207ms

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

Hooks

After Hooks.deleteTransportAfterTest() 635ms

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

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

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

When Go to "TRANSPORT_TABLE" 472ms

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

And Show all transport types 1s 194ms

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

Hooks

After Hooks.deleteTransportAfterTest() 598ms

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

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

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

When Go to "TRANSPORT_TABLE" 351ms

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

And Show all transport types 1s 188ms

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

Hooks

After Hooks.deleteTransportAfterTest() 585ms

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

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

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

When Go to "TRANSPORT_TABLE" 426ms

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

And Show all transport types 1s 193ms

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

Hooks

After Hooks.deleteTransportAfterTest() 646ms

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

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

And Delete created transport by API 674ms

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

When Go to "ARCHIVE_TAB" 507ms

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

And Show "SMALLS_IMPORT" 192ms

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

Hooks

After Hooks.deleteTransportAfterTest() 602ms

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

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

And Delete created transport by API 648ms

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

When Go to "ARCHIVE_TAB" 502ms

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

And Show "SMALLS_IMPORT" 181ms

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

Hooks

After Hooks.deleteTransportAfterTest() 601ms

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

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

And Delete created transport by API 649ms

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

When Go to "ARCHIVE_TAB" 505ms

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

And Show "SMALLS_IMPORT" 189ms

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

Hooks

After Hooks.deleteTransportAfterTest() 612ms

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

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

And Delete created transport by API 586ms

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

When Go to "ARCHIVE_TAB" 510ms

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

And Show "SMALLS_IMPORT" 169ms

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

Hooks

After Hooks.deleteTransportAfterTest() 595ms

View Feature Filters

@deleteTransportAfterTest

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

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

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

And Go to "TRANSPORT_TABLE" 420ms

And Show all transport "true" 263ms

And Select transportType "TRANSPORT_ORDER" 1s 321ms

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

Hooks

After Hooks.deleteTransportAfterTest() 532ms

View Feature Filters

@deleteTransportAfterTest

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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 8s 074ms

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

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

And Accept transferred transport by Api 650ms

And Create advice "ADVICE_SMALLS" "SMALLS_IMPORT" "super-admin-skz" 1m 053ms

And Delete created transport by API 858ms

When Go to "ARCHIVE_TAB" 511ms

And Show "SMALLS_IMPORT" 183ms

Then Check if it is possible to search with different date property selects 1m 29s 911ms

Hooks

After Hooks.deleteTransportAfterTest() 790ms

View Feature Filters

@deleteTransportAfterTest

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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 845ms

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

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

And Accept transferred transport by Api 680ms

And Create advice "ADVICE_SMALLS" "SMALLS_EXPORT" "super-admin-skz" 1m 275ms

And Delete created transport by API 871ms

When Go to "ARCHIVE_TAB" 505ms

And Show "SMALLS_EXPORT" 215ms

Then Check if it is possible to search with different date property selects 1m 29s 393ms

Hooks

After Hooks.deleteTransportAfterTest() 770ms

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

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

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

And Login as "neuca-admin" 8s 967ms

And Go to "TRANSPORT_TABLE" 523ms

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

And Toggle transport table days limit filter 194ms

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

Hooks

After Hooks.deleteTransportAfterTest() 856ms

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

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

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

When Go to "TRANSPORT_TABLE" 405ms

And Go to auction form 1s 658ms

And Select contractors group "Kraj" 273ms

Then Verify that carrier "PSKZA1" is selected 087ms

Hooks

After Hooks.deleteTransportAfterTest() 655ms

After Hooks.removeContractorsGroup() 286ms

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 488ms

And Go to auction form 1s 574ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 607ms

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

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

When Go to "TRANSPORT_TABLE" 492ms

And Go to auction form 1s 566ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 696ms

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

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

And Show all transport "false" 075ms

And Get inputs from database "ADD_INDEX" "super-admin-adama" 015ms

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

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

And Expand index panel 270ms

And Click add index button 319ms

And Fill index form 11s 707ms

And Click ok button in index form 15s 261ms

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

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

And Expand index panel 263ms

Then Check are transport values equals 266ms

Hooks

After Hooks.deleteTransportAfterTest() 550ms

After Hooks.deleteProductAfterTest() 196ms

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

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

And Show all transport "true" 217ms

And Get inputs from database "ADD_INDEX" "super-admin-alrec" 020ms

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

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

And Expand index panel 319ms

And Click add index button 310ms

And Fill index form 8s 687ms

And Click ok button in index form 15s 268ms

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

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

And Expand index panel 287ms

Then Check are transport values equals 2s 362ms

Hooks

After Hooks.deleteTransportAfterTest() 535ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Crud index

@deleteTransportAfterTest

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

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

And Show all transport "false" 080ms

And Get inputs from database "ADD_INDEX" "super-admin-adama" 016ms

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

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

And Expand index panel 255ms

And Click add index button 277ms

And Fill index form 11s 767ms

And Click ok button in index form 15s 249ms

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

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

And Expand index panel 253ms

And Click edit index button 298ms

And Edit index quantity to "999" 366ms

And Click ok button in index form 15s 211ms

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

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

And Expand index panel 250ms

And Verify if index quantity equals "999" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 576ms

View Feature Crud index

@deleteTransportAfterTest

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

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

And Show all transport "true" 230ms

And Get inputs from database "ADD_INDEX" "super-admin-alrec" 028ms

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

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

And Expand index panel 352ms

And Click add index button 303ms

And Fill index form 8s 759ms

And Click ok button in index form 15s 281ms

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

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

And Expand index panel 269ms

And Click edit index button 263ms

And Edit index quantity to "999" 347ms

And Click ok button in index form 15s 226ms

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

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

And Expand index panel 279ms

And Verify if index quantity equals "999" 079ms

Hooks

After Hooks.deleteTransportAfterTest() 532ms

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

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

And Show all transport "false" 079ms

And Get inputs from database "ADD_INDEX" "super-admin-adama" 016ms

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

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

And Add index to transport 27s 608ms

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

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

And Expand index panel 273ms

And Click delete index button 179ms

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

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

And Expand index panel 226ms

Then Verify that transport has no indexes 15s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 555ms

After Hooks.deleteProductAfterTest() 153ms

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

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

And Show all transport "true" 217ms

And Get inputs from database "ADD_INDEX" "super-admin-alrec" 021ms

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

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

And Add index to transport 24s 619ms

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

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

And Expand index panel 245ms

And Click delete index button 190ms

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

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

And Expand index panel 261ms

Then Verify that transport has no indexes 15s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 534ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if indexes displayed after click indexes datails 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 478ms

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

And Get inputs from database "ADD_INDEX" "super-admin-dayco" 017ms

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

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

And Add index to transport 25s 963ms

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

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 678ms

When Click on index details icon 228ms

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

Hooks

After Hooks.deleteTransportAfterTest() 702ms

After Hooks.deleteProductAfterTest() 135ms

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

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

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

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

And Show all transport types 1s 132ms

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

And Set advice window in schedule 3s 449ms

And Fill advice form 17s 201ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 842ms

After Hooks.cleanUserDetailsAfterTest() 1s 359ms

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

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

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

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

And Show all transport types 1s 155ms

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

And Set advice window in schedule 3s 438ms

And Fill advice form 12s 956ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 764ms

After Hooks.cleanUserDetailsAfterTest() 1s 059ms

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

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

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

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

And Show all transport types 1s 168ms

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

And Set advice window in schedule 3s 289ms

And Fill advice form 18s 595ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 752ms

After Hooks.cleanUserDetailsAfterTest() 1s 552ms

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

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

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

And Show all transport types 1s 164ms

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

And Go to "TRANSPORT_TABLE" 452ms

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

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

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

And Fill transport form 5s 148ms

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

And Expand advice panel 258ms

And Edit advice in transport details 17s 487ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 765ms

After Hooks.cleanUserDetailsAfterTest() 1s 397ms

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

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

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

And Show all transport types 1s 156ms

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

And Go to "TRANSPORT_TABLE" 461ms

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

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

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

And Fill transport form 1m 8s 823ms

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

And Expand advice panel 238ms

And Edit advice in transport details 8s 121ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 967ms

After Hooks.cleanUserDetailsAfterTest() 1s 105ms

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

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

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

And Show all transport types 1s 171ms

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

And Go to "TRANSPORT_TABLE" 469ms

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

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

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

And Fill transport form 28s 791ms

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

And Expand advice panel 266ms

And Edit advice in transport details 23s 730ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 797ms

After Hooks.cleanUserDetailsAfterTest() 1s 651ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 795ms

After Hooks.cleanUserDetailsAfterTest() 940ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 778ms

After Hooks.cleanUserDetailsAfterTest() 1s 640ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

After Hooks.cleanUserDetailsAfterTest() 2s 122ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 586ms

After Hooks.cleanUserDetailsAfterTest() 2s 167ms

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

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 715ms

After Hooks.cleanUserDetailsAfterTest() 2s 328ms

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 672ms

After Hooks.cleanUserDetailsAfterTest() 1s 349ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 598ms

After Hooks.cleanUserDetailsAfterTest() 2s 202ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 592ms

After Hooks.cleanUserDetailsAfterTest() 2s 308ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 591ms

After Hooks.cleanUserDetailsAfterTest() 2s 121ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

After Hooks.cleanUserDetailsAfterTest() 2s 046ms

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

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

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

And Go to "TRANSPORT_TABLE" 418ms

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

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

And Fill transport form 43s 013ms

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

And Fill discrepancy report section 52s 368ms

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

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

And Generate discrepancy report 21s 562ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 947ms

After Hooks.cleanUserDetailsAfterTest() 3s 380ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 442ms

And Select warehouse "Serownia" 1s 652ms

And Set week view 1s 240ms

And Show yesterday 1s 149ms

And Move window into the past 436ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

After Hooks.cleanUserDetailsAfterTest() 2s 341ms

After Hooks.rollbackAddedAuthorities() 120ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 596ms

After Hooks.cleanUserDetailsAfterTest() 2s 154ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 582ms

After Hooks.cleanUserDetailsAfterTest() 2s 150ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 799ms

After Hooks.cleanUserDetailsAfterTest() 2s 001ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 601ms

After Hooks.cleanUserDetailsAfterTest() 2s 039ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

Then If user is login then logout 259ms

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

And Go to auction details 1s 908ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 891ms

After Hooks.cleanUserDetailsAfterTest() 2s 744ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 685ms

After Hooks.cleanUserDetailsAfterTest() 2s 750ms

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

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

When Go to new transport "DELIVERY" 784ms

And Fill transport form 48s 303ms

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

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

And Set advice window in schedule 2s 437ms

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

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

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

And Go to "TRANSPORT_TABLE" 597ms

And Show all transport "false" 079ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 913ms

View Feature Pallet limit

@deleteTransportAfterTest @rollbackMaxPalletLimit @TmsLink=A-7073

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

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

And Get inputs from database "CREATE_UNLOAD" "super-admin-pgf" 022ms

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

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

And Fill transport form 32s 654ms

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

And Set advice window in schedule 2s 456ms

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

And Go to "TRANSPORT_TABLE" 513ms

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

Then Check are transport values equals 26s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 749ms

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 261ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 391ms

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

And Set advice window in schedule 3s 431ms

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

Hooks

After Hooks.deleteTransportAfterTest() 635ms

After Hooks.deleteModeOfTransportationAfterTest() 291ms

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

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

And Set status of MOT to "DISABLED" 311ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 488ms

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

And Set advice window in schedule 3s 376ms

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

Hooks

After Hooks.deleteTransportAfterTest() 583ms

After Hooks.deleteModeOfTransportationAfterTest() 266ms

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

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

And Set status of MOT to "ACCEPTED" 286ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 461ms

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

And Set advice window in schedule 3s 375ms

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

Hooks

After Hooks.deleteTransportAfterTest() 625ms

After Hooks.deleteModeOfTransportationAfterTest() 329ms

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

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

And Set status of MOT to "UPDATED" 302ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 475ms

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

And Set advice window in schedule 3s 402ms

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

Hooks

After Hooks.deleteTransportAfterTest() 622ms

After Hooks.deleteModeOfTransportationAfterTest() 316ms

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

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

And Set status of MOT to "REJECTED" 303ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 507ms

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

And Set advice window in schedule 3s 378ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 566ms

After Hooks.deleteModeOfTransportationAfterTest() 297ms

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

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

And Set status of MOT to "BLOCKED" 297ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 374ms

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

And Set advice window in schedule 3s 343ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 609ms

After Hooks.deleteModeOfTransportationAfterTest() 300ms

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

When Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms

And Add transport by SKApi in "MGW" assigned to "" 1s 956ms

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

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

And Set advice window in schedule 3s 319ms

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

And Fill advice form 20s 528ms

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

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

And Confirm statuses until reach "left-the-factory" through SKAPI 34s 417ms

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

Hooks

After Hooks.deleteTransportAfterTest() 831ms

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 Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 018ms

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

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

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

And Go to "TRANSPORT_TABLE" 373ms

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

Then Check are transport values equals 1s 270ms

Hooks

After Hooks.deleteTransportAfterTest() 617ms

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 Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms

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

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

Then Check is transport "CONTAINER" created in transport table and set transport id 9s 931ms

And Go to "TRANSPORT_TABLE" 348ms

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

Then Check are transport values equals 1s 249ms

Hooks

After Hooks.deleteTransportAfterTest() 606ms

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 Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms

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

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

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 135ms

And Go to "TRANSPORT_TABLE" 361ms

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

Then Check are transport values equals 1s 239ms

Hooks

After Hooks.deleteTransportAfterTest() 581ms

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 Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms

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

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

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

And Go to "TRANSPORT_TABLE" 357ms

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

Then Check are transport values equals 1s 164ms

Hooks

After Hooks.deleteTransportAfterTest() 611ms

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 Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms

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

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

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

And Go to "TRANSPORT_TABLE" 358ms

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

Then Check are transport values equals 141ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.Wp7ONc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e145d6961212f956fc0dcb269d0fc6f2
	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() 575ms

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 Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms

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

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

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 113ms

And Go to "TRANSPORT_TABLE" 364ms

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

Then Check are transport values equals 1s 156ms

Hooks

After Hooks.deleteTransportAfterTest() 572ms

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

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms

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

And Set another client name "Pepsi" 000ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 633ms

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 Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms

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

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

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

And Go to "TRANSPORT_TABLE" 349ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 584ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 346ms

And Fill advice form 20s 266ms

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

And Go to "TRANSPORT_TABLE" 481ms

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

Then Check are advice values equals 4s 936ms

Hooks

After Hooks.deleteTransportAfterTest() 798ms

After Hooks.cleanUserDetailsAfterTest() 2s 238ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 391ms

And Fill advice form 20s 353ms

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

And Go to "TRANSPORT_TABLE" 444ms

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

Then Check are advice values equals 4s 969ms

Hooks

After Hooks.deleteTransportAfterTest() 802ms

After Hooks.cleanUserDetailsAfterTest() 2s 059ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 360ms

And Fill advice form 20s 478ms

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

And Go to "TRANSPORT_TABLE" 484ms

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

Then Check are advice values equals 5s 152ms

Hooks

After Hooks.deleteTransportAfterTest() 832ms

After Hooks.cleanUserDetailsAfterTest() 2s 119ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 577ms

And Fill advice form 20s 247ms

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

And Go to "TRANSPORT_TABLE" 468ms

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

Then Check are advice values equals 4s 991ms

Hooks

After Hooks.deleteTransportAfterTest() 784ms

After Hooks.cleanUserDetailsAfterTest() 2s 704ms

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

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

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

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

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

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

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

And Set advice window in schedule 30s 193ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.Wp7ONc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e145d6961212f956fc0dcb269d0fc6f2
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

And Fill advice form 000ms

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

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 567ms

After Hooks.cleanUserDetailsAfterTest() 1s 771ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 401ms

And Fill advice form 20s 497ms

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

And Go to "TRANSPORT_TABLE" 450ms

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

Hooks

After Hooks.deleteTransportAfterTest() 805ms

After Hooks.cleanUserDetailsAfterTest() 2s 113ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 378ms

And Fill advice form 20s 452ms

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

And Go to "TRANSPORT_TABLE" 451ms

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

Hooks

After Hooks.deleteTransportAfterTest() 849ms

After Hooks.cleanUserDetailsAfterTest() 2s 341ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 347ms

And Fill advice form 20s 451ms

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

And Go to "TRANSPORT_TABLE" 424ms

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

Hooks

After Hooks.deleteTransportAfterTest() 830ms

After Hooks.cleanUserDetailsAfterTest() 2s 073ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 400ms

And Fill advice form 20s 508ms

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

And Go to "TRANSPORT_TABLE" 504ms

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

Hooks

After Hooks.deleteTransportAfterTest() 923ms

After Hooks.cleanUserDetailsAfterTest() 2s 933ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 357ms

And Fill advice form 20s 453ms

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

And Go to "TRANSPORT_TABLE" 446ms

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

Hooks

After Hooks.deleteTransportAfterTest() 853ms

After Hooks.cleanUserDetailsAfterTest() 1s 660ms

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

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

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

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

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

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

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

And Fill advice form 20s 496ms

And Click advice save button to check error message 182ms

Then Check if possible advice alert is displayed 070ms

Hooks

After Hooks.deleteTransportAfterTest() 581ms

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

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

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

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

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

And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 312ms

And Go to "TRANSPORT_TABLE" 465ms

When Go to transport details "OWN_COLLECTION" 2s 905ms

And Expand advice panel 296ms

And Edit advice in transport details 18s 853ms

And Fill arrival date field 2s 659ms

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

Then Check advice data in database after edition "OWN_COLLECTION" 092ms

Hooks

After Hooks.deleteTransportAfterTest() 803ms

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

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

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

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

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

And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 476ms

And Go to "TRANSPORT_TABLE" 467ms

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

And Expand advice panel 294ms

And Edit advice in transport details 18s 922ms

And Fill arrival date field 2s 624ms

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

Then Check advice data in database after edition "CONTAINER" 099ms

Hooks

After Hooks.deleteTransportAfterTest() 810ms

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

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

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

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

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

And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 462ms

And Go to "TRANSPORT_TABLE" 496ms

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

And Expand advice panel 320ms

And Edit advice in transport details 18s 919ms

And Fill arrival date field 2s 650ms

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

Then Check advice data in database after edition "TRANSPORT_ORDER" 106ms

Hooks

After Hooks.deleteTransportAfterTest() 831ms

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

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 257ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 199ms

When Go to "WAREHOUSE_TAB" 1s 325ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 258ms

And Select view "DAYS_2" 2s 184ms

Then Check if gray window is in the schedule 2s 047ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 442ms

And Select view "DAYS_2" 2s 137ms

And Check if gray window is in the schedule 2s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 568ms

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 215ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 241ms

When Go to "WAREHOUSE_TAB" 1s 354ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 309ms

And Select view "DAYS_2" 2s 180ms

Then Check if gray window is in the schedule 2s 049ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 416ms

And Select view "DAYS_2" 2s 156ms

And Check if gray window is in the schedule 2s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 611ms

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 298ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 347ms

When Go to "WAREHOUSE_TAB" 1s 416ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 356ms

And Select view "DAYS_2" 2s 191ms

Then Check if gray window is in the schedule 2s 046ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 428ms

And Select view "DAYS_2" 2s 139ms

And Check if gray window is in the schedule 2s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 555ms

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

And Create "CREATE_GRAY_WINDOW_MGW" window by JSON file for test as "super-admin-skz" 206ms

And Create "CREATE_GRAY_WINDOW_HRL" window by JSON file for test as "super-admin-skz" 205ms

When Go to "WAREHOUSE_TAB" 941ms

And Select warehouse "MGW" 1s 394ms

And Select view "DAYS_2" 2s 216ms

Then Check if gray window is in the schedule 2s 046ms

And Select warehouse "HRL" 1s 534ms

And Select view "DAYS_2" 2s 115ms

And Check if gray window is in the schedule 2s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 561ms

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

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

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;false" 357ms

When Login as "neuca-admin" 9s 324ms

And Go to new transport "DELIVERY" 706ms

And Fill transport form 39s 549ms

And Get sum of pallets of "load" in transport form 088ms

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

And Set advice window in schedule 2s 409ms

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

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 263ms

Hooks

After Hooks.deleteTransportAfterTest() 997ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 146ms

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_COMPANY_STEP_ONLY" "super-admin-neuca" 001ms

And Get package type settings for transportType "DELIVERY" from "neuca" 129ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "false;true" 224ms

When Login as "neuca-admin" 2s 492ms

And Go to new transport "DELIVERY" 717ms

And Fill transport form 39s 555ms

And Get sum of pallets of "unload" in transport form 087ms

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

And Set advice window in schedule 2s 370ms

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

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 206ms

Hooks

After Hooks.deleteTransportAfterTest() 887ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 139ms

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_WAREHOUSE_AND_COMPANY_STEPS" "super-admin-neuca" 001ms

And Get package type settings for transportType "DELIVERY" from "neuca" 127ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;true" 219ms

When Login as "neuca-admin" 2s 493ms

And Go to new transport "DELIVERY" 709ms

And Fill transport form 42s 621ms

And Get sum of pallets of "unload" in transport form 090ms

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

And Set advice window in schedule 2s 425ms

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

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 282ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 142ms

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 200ms

And Mark custom fields as not obligatory 2s 840ms

And Login as "hochland-admin" 9s 772ms

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

When Find transport in table with status "advice-added" 3s 655ms

And Confirm statuses until reach "process-ended" 22s 907ms

Then Check if transport has "process-ended" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 775ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 515ms

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

And Get custom field settings for "UNLOAD" transport type and "pgf" company 118ms

And Mark custom fields as not obligatory 005ms

And Login as "pgf-admin" 4s 744ms

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

When Find transport in table with status "planned" 17s 569ms

And Confirm statuses until reach "process-ended" 12s 646ms

Then Check if transport has "process-ended" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 763ms

After Hooks.rollbackAllCustomFieldsSettings() 447ms

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

And Get custom field settings for "DELIVERY" transport type and "adama" company 110ms

And Mark custom fields as not obligatory 005ms

And Login as "adama-admin" 4s 986ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 697ms

When Find transport in table with status "planned" 3s 691ms

And Confirm statuses until reach "process-ended" 11s 512ms

Then Check if transport has "process-ended" 071ms

Hooks

After Hooks.deleteTransportAfterTest() 684ms

After Hooks.rollbackAllCustomFieldsSettings() 416ms

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 "DELIVERY" transport type and "lantmannen" company 094ms

And Mark custom fields as not obligatory 004ms

And Login as "lantmannen-admin" 4s 542ms

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

When Find transport in table with status "potwierdzony" 3s 700ms

And Confirm statuses until reach "process-ended" 21s 831ms

Then Check if transport has "process-ended" 081ms

Hooks

After Hooks.deleteTransportAfterTest() 758ms

After Hooks.rollbackAllCustomFieldsSettings() 005ms

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

And Get custom field settings for "LOAD" transport type and "lantmannen" company 096ms

And Mark custom fields as not obligatory 003ms

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

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

When Find transport in table with status "created" 3s 687ms

And Confirm statuses until reach "process-ended" 27s 030ms

Then Check if transport has "process-ended" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 736ms

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

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 113ms

And Mark custom fields as not obligatory 605ms

And Login as "keeeper-admin" 5s 647ms

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

When Find transport in table with status "planned" 3s 673ms

And Confirm statuses until reach "process-ended" 21s 756ms

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 750ms

After Hooks.rollbackAllCustomFieldsSettings() 614ms

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

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 116ms

And Mark custom fields as not obligatory 570ms

And Login as "keeeper-admin" 5s 507ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 925ms

When Find transport in table with status "planned" 3s 697ms

And Confirm statuses until reach "process-ended" 21s 912ms

Then Check if transport has "process-ended" 073ms

Hooks

After Hooks.deleteTransportAfterTest() 753ms

After Hooks.rollbackAllCustomFieldsSettings() 831ms

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 Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 524ms

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

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

When Accept or reject "accept" transferred transport 19s 665ms

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

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

And Set advice window in schedule 3s 602ms

And Fill advice form 20s 382ms

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

And Check if window is "silver" 4s 070ms

And Go to "TRANSPORT_TABLE" 471ms

Then Check if transport has "process-ended" 907ms

Hooks

After Hooks.deleteTransportAfterTest() 913ms

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 Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 640ms

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

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

When Accept or reject "accept" transferred transport 19s 835ms

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

And Click button advice in transport table "SMALLS_EXPORT" 234ms

And Set advice window in schedule 3s 528ms

And Fill advice form 20s 321ms

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

And Check if window is "silver" 4s 076ms

And Go to "TRANSPORT_TABLE" 477ms

Then Check if transport has "process-ended" 1s 175ms

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

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_ADVICE" "CHECKPOINT_BASED" "ARRIVAL" 439ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 180ms

And Mark custom fields as not obligatory 2s 812ms

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

When Login as "hochland-admin" 10s 105ms

And Find transport in table with status "advice-added" 3s 799ms

And Confirm statuses until reach "arrived" 6s 284ms

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

Then Check if it is not possible to edit advice 1s 458ms

Hooks

After Hooks.deleteTransportAfterTest() 805ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 498ms

After Hooks.rollbackAddedActionAuthorities() 259ms

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 195ms

And Mark custom fields as not obligatory 2s 795ms

And Login as "hochland-admin" 9s 726ms

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

When Find transport in table with status "advice-added" 3s 674ms

And Check if transport row is "blue" 3s 208ms

And Confirm statuses until reach "arrived" 6s 287ms

And Check if transport row is "green" 3s 223ms

And Confirm statuses until reach "during-unload" 6s 227ms

Then Check if transport row is "orange" 3s 216ms

And Confirm statuses until reach "unloaded" 6s 208ms

Then Check if transport row is "darkgoldenrod" 3s 223ms

And Confirm statuses until reach "process-ended" 6s 219ms

Then Check if transport row is "silver" 3s 227ms

Hooks

After Hooks.deleteTransportAfterTest() 830ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 451ms

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

And Get custom field settings for "DELIVERY" transport type and "piast" company 236ms

And Mark custom fields as not obligatory 006ms

And Login as "piast-admin" 5s 628ms

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

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

And Show all transport types 1s 158ms

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

And Set advice window in schedule 3s 397ms

And Fill advice form 12s 968ms

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

And Go to "TRANSPORT_TABLE" 518ms

And Find transport in table with status "advice-added" 3s 617ms

And Confirm statuses until reach "left-the-area" 32s 297ms

Then Check if next status is not possible to confirm 325ms

Hooks

After Hooks.deleteTransportAfterTest() 789ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 806ms

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

And Get custom field settings for "LOAD" transport type and "piast" company 258ms

And Mark custom fields as not obligatory 010ms

And Login as "piast-admin" 5s 802ms

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

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 024ms

And Show all transport types 1s 152ms

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

And Set advice window in schedule 3s 334ms

And Fill advice form 13s 011ms

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

And Go to "TRANSPORT_TABLE" 416ms

And Find transport in table with status "advice-added" 3s 659ms

And Confirm statuses until reach "left-the-area" 32s 221ms

Then Check if next status is not possible to confirm 303ms

Hooks

After Hooks.deleteTransportAfterTest() 781ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 399ms

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" 223ms

And Get custom field settings for "DELIVERY" transport type and "piast" company 232ms

And Mark custom fields as not obligatory 012ms

And Login as "piast-admin" 5s 611ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 007ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 017ms

And Show all transport types 1s 133ms

And Click button advice in transport table "DELIVERY" 267ms

And Set advice window in schedule 3s 356ms

And Fill advice form 12s 856ms

And Click advice save button and wait for advice form to disappear 33s 267ms

And Go to "TRANSPORT_TABLE" 476ms

And Find transport in table with status "advice-added" 3s 662ms

When Add file to transport by API 1s 921ms

And Confirm statuses until reach "process-ended" 37s 672ms

Then Check if transport has "process-ended" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 805ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 861ms

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" 235ms

And Get custom field settings for "LOAD" transport type and "piast" company 257ms

And Mark custom fields as not obligatory 013ms

And Login as "piast-admin" 5s 839ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 969ms

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 025ms

And Show all transport types 1s 149ms

And Click button advice in transport table "LOAD" 231ms

And Set advice window in schedule 3s 409ms

And Fill advice form 13s 053ms

And Click advice save button and wait for advice form to disappear 33s 300ms

And Go to "TRANSPORT_TABLE" 461ms

And Find transport in table with status "advice-added" 3s 684ms

When Add file to transport by API 1s 363ms

And Confirm statuses until reach "process-ended" 37s 385ms

Then Check if transport has "process-ended" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 769ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 456ms

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" 223ms

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 240ms

And Mark custom fields as not obligatory 4s 970ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 467ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 927ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Login as "hochland-admin" 10s 024ms

And Show all transport types 1s 162ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 121ms

And Set advice window in schedule 7s 544ms

And Fill advice form 18s 877ms

And Click advice save button and wait for advice form to disappear 33s 901ms

And Go to "TRANSPORT_TABLE" 464ms

And Find transport in table with status "advice-added" 3s 628ms

And Confirm statuses until reach "during-load" 11s 618ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 609ms

And Check if next status is not possible to confirm in status confirmation modal 280ms

Hooks

After Hooks.deleteTransportAfterTest() 942ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 138ms

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) 000ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 234ms

And Get custom field settings for "LOAD" transport type and "keeeper" company 116ms

And Mark custom fields as not obligatory 794ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 225ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 919ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Login as "keeeper-admin" 5s 928ms

And Show all transport types 1s 164ms

And Click button advice in transport table "LOAD" 249ms

And Set advice window in schedule 3s 276ms

And Fill advice form 18s 841ms

And Click advice save button and wait for advice form to disappear 33s 283ms

And Go to "TRANSPORT_TABLE" 468ms

And Find transport in table with status "advice-added" 3s 690ms

And Confirm statuses until reach "arrived" 6s 263ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 566ms

And Check if next status is not possible to confirm in status confirmation modal 256ms

Hooks

After Hooks.deleteTransportAfterTest() 746ms

After Hooks.rollbackAllCustomFieldsSettings() 860ms

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" 238ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 130ms

And Mark custom fields as not obligatory 709ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 233ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 905ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 001ms

And Login as "keeeper-admin" 5s 816ms

And Show all transport types 1s 216ms

And Click button advice in transport table "CONTAINER" 277ms

And Set advice window in schedule 3s 236ms

And Fill advice form 18s 677ms

And Click advice save button and wait for advice form to disappear 33s 204ms

And Go to "TRANSPORT_TABLE" 440ms

And Find transport in table with status "advice-added" 3s 673ms

And Confirm statuses until reach "arrived" 6s 308ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 553ms

And Check if next status is not possible to confirm in status confirmation modal 229ms

Hooks

After Hooks.deleteTransportAfterTest() 756ms

After Hooks.rollbackAllCustomFieldsSettings() 904ms

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) 002ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 244ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 115ms

And Mark custom fields as not obligatory 545ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 231ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 834ms

And Login as "keeeper-admin" 5s 845ms

And Go to "TRANSPORT_TABLE" 417ms

And Find transport in table with status "planned" 3s 682ms

And Confirm statuses until reach "arrived" 6s 280ms

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 266ms

Hooks

After Hooks.deleteTransportAfterTest() 887ms

After Hooks.rollbackAllCustomFieldsSettings() 556ms

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) 000ms

Steps

Given Set token of apiUsername "super-admin-keeeper" 229ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 113ms

And Mark custom fields as not obligatory 582ms

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" 253ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 948ms

And Login as "keeeper-admin" 5s 595ms

And Go to "TRANSPORT_TABLE" 388ms

And Find transport in table with status "planned" 3s 622ms

And Confirm statuses until reach "arrived" 6s 274ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 617ms

And Check if next status is not possible to confirm in status confirmation modal 225ms

Hooks

After Hooks.deleteTransportAfterTest() 922ms

After Hooks.rollbackAllCustomFieldsSettings() 730ms

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" 212ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 210ms

And Mark custom fields as not obligatory 2s 726ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 1s 218ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 055ms

And Login as "hochland-admin" 10s 027ms

And Go to "TRANSPORT_TABLE" 471ms

And Find transport in table with status "advice-added" 3s 644ms

And Confirm statuses until reach "during-unload" 11s 506ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 681ms

And Check if next status is not possible to confirm in status confirmation modal 234ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 059ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 490ms

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" 236ms

And Get custom field settings for "LOAD" transport type and "keeeper" company 147ms

And Mark custom fields as not obligatory 779ms

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" 265ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 947ms

And Login as "keeeper-admin" 5s 622ms

And Show all transport types 1s 281ms

And Click button advice in transport table "LOAD" 256ms

And Set advice window in schedule 3s 300ms

And Fill advice form 18s 821ms

And Click advice save button and wait for advice form to disappear 33s 269ms

And Go to "TRANSPORT_TABLE" 423ms

And Find transport in table with status "advice-added" 3s 709ms

When Confirm statuses until reach "arrived" 6s 292ms

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 271ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 387ms

And Go to transport details "LOAD" 2s 871ms

And Open section: "advice-panel" 1s 174ms

And Fill transport form 28s 640ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 263ms

And Go to transport details "LOAD" 2s 851ms

And Open section: "advice-panel" 1s 164ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 30s 641ms

And Confirm statuses until reach "process-ended" 16s 664ms

Then Check if transport has "process-ended" 078ms

Hooks

After Hooks.deleteTransportAfterTest() 791ms

After Hooks.rollbackAllCustomFieldsSettings() 893ms

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" 232ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 115ms

And Mark custom fields as not obligatory 726ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 251ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 937ms

And Login as "keeeper-admin" 5s 912ms

And Show all transport types 1s 163ms

And Click button advice in transport table "CONTAINER" 237ms

And Set advice window in schedule 3s 315ms

And Fill advice form 18s 755ms

And Click advice save button and wait for advice form to disappear 33s 246ms

And Go to "TRANSPORT_TABLE" 415ms

And Find transport in table with status "advice-added" 3s 683ms

When Confirm statuses until reach "arrived" 6s 263ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 564ms

And Check if next status is not possible to confirm in status confirmation modal 257ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 407ms

And Go to transport details "CONTAINER" 2s 805ms

And Open section: "advice-panel" 1s 148ms

And Fill transport form 28s 713ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 239ms

And Go to transport details "CONTAINER" 2s 929ms

And Open section: "advice-panel" 1s 170ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 30s 630ms

And Confirm statuses until reach "process-ended" 15s 567ms

Then Check if transport has "process-ended" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 819ms

After Hooks.rollbackAllCustomFieldsSettings() 920ms

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" 231ms

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 244ms

And Mark custom fields as not obligatory 4s 830ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 399ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 933ms

And Login as "hochland-admin" 10s 095ms

And Show all transport types 1s 158ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 097ms

And Set advice window in schedule 7s 498ms

And Fill advice form 19s 032ms

And Click advice save button and wait for advice form to disappear 33s 850ms

And Go to "TRANSPORT_TABLE" 483ms

And Find transport in table with status "advice-added" 3s 629ms

When Confirm statuses until reach "during-load" 11s 571ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 613ms

And Check if next status is not possible to confirm in status confirmation modal 307ms

And Set "transport" inputs from JSON file "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Click cancel in status confirmation modal 15s 337ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 961ms

And Open section: "advice-panel" 1s 157ms

And Fill transport form 39s 943ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 231ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 951ms

And Open section: "advice-panel" 1s 367ms

And Fill "warehouseman-(u)" in transport form 30s 689ms

And Confirm statuses until reach "process-ended" 32s 199ms

Then Check if transport has "process-ended" 081ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 074ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 140ms

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" 258ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 116ms

And Mark custom fields as not obligatory 560ms

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" 248ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 912ms

And Login as "keeeper-admin" 6s 179ms

And Go to "TRANSPORT_TABLE" 427ms

And Find transport in table with status "planned" 3s 686ms

When Confirm statuses until reach "arrived" 6s 249ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 633ms

And Check if next status is not possible to confirm in status confirmation modal 240ms

And Click cancel in status confirmation modal 15s 368ms

And Go to transport details "UNLOAD" 2s 924ms

And Fill transport form 43s 236ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 169ms

And Confirm statuses until reach "process-ended" 16s 680ms

Then Check if transport has "process-ended" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 829ms

After Hooks.rollbackAllCustomFieldsSettings() 598ms

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" 219ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 131ms

And Mark custom fields as not obligatory 602ms

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" 247ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 889ms

And Login as "keeeper-admin" 6s 154ms

And Go to "TRANSPORT_TABLE" 405ms

And Find transport in table with status "planned" 3s 632ms

When Confirm statuses until reach "arrived" 6s 251ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 671ms

And Check if next status is not possible to confirm in status confirmation modal 243ms

And Click cancel in status confirmation modal 15s 362ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 892ms

And Fill transport form 43s 265ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 196ms

And Confirm statuses until reach "process-ended" 16s 683ms

Then Check if transport has "process-ended" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 795ms

After Hooks.rollbackAllCustomFieldsSettings() 718ms

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 198ms

And Mark custom fields as not obligatory 2s 745ms

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" 707ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 140ms

And Login as "hochland-admin" 10s 293ms

And Go to "TRANSPORT_TABLE" 506ms

And Find transport in table with status "advice-added" 3s 645ms

When Confirm statuses until reach "during-unload" 11s 475ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 657ms

And Check if next status is not possible to confirm in status confirmation modal 229ms

And Click cancel in status confirmation modal 15s 563ms

And Go to transport details "DELIVERY" 3s 017ms

And Fill transport form 43s 052ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 198ms

And Confirm statuses until reach "process-ended" 11s 483ms

Then Check if transport has "process-ended" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 850ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 380ms

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" 247ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 761ms

And Confirm status "REPORTING" by Public API "v1" 542ms

And Confirm status "ARRIVAL" by Public API "v1" 656ms

And Login as "swiss-krono-delivery-guard" 4s 880ms

And Go to "TRANSPORT_TABLE" 476ms

When Confirm "Departure" status in transport row 262ms

Then Verify that "Departure" has been confirmed 1s 343ms

Hooks

After Hooks.deleteTransportAfterTest() 812ms

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" 238ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 113ms

And Mark custom fields as not obligatory 584ms

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" 246ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 16s 721ms

When Login as "keeeper-admin" 5s 820ms

And Find transport in table with status "planned" 3s 713ms

And Confirm statuses until reach "arrived" 6s 290ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 567ms

And Check if next status is not possible to confirm in status confirmation modal 268ms

And Click cancel in status confirmation modal 15s 402ms

And Go to transport details "UNLOAD" 2s 991ms

And Fill transport form 43s 207ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 337ms

And Check if next status is not possible to confirm in status confirmation modal 227ms

Hooks

After Hooks.deleteTransportAfterTest() 782ms

After Hooks.rollbackAllCustomFieldsSettings() 608ms

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" 224ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 123ms

And Mark custom fields as not obligatory 561ms

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" 244ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 939ms

When Login as "keeeper-admin" 5s 939ms

And Find transport in table with status "planned" 3s 726ms

And Confirm statuses until reach "arrived" 6s 277ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 616ms

And Check if next status is not possible to confirm in status confirmation modal 262ms

And Click cancel in status confirmation modal 15s 398ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 964ms

And Fill transport form 43s 264ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 321ms

And Check if next status is not possible to confirm in status confirmation modal 229ms

Hooks

After Hooks.deleteTransportAfterTest() 749ms

After Hooks.rollbackAllCustomFieldsSettings() 711ms

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-hochland" 230ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 190ms

And Mark custom fields as not obligatory 2s 715ms

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" 721ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 172ms

When Login as "hochland-admin" 9s 942ms

And Find transport in table with status "advice-added" 3s 802ms

And Confirm statuses until reach "during-unload" 11s 503ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 666ms

And Check if next status is not possible to confirm in status confirmation modal 248ms

And Click cancel in status confirmation modal 15s 605ms

And Go to transport details "DELIVERY" 2s 958ms

And Fill transport form 43s 013ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 331ms

And Check if next status is not possible to confirm in status confirmation modal 289ms

Hooks

After Hooks.deleteTransportAfterTest() 813ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 383ms

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" 246ms

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 586ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 175ms

And Mark custom fields as not obligatory 751ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 2s 006ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 361ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 731ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 386ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 630ms

And Login as "bausch-admin" 6s 283ms

And Go to "TRANSPORT_TABLE" 520ms

And Find transport in table with status "advice-added" 3s 623ms

And Confirm statuses until reach "on-the-way" 16s 788ms

When Open statuses popup 137ms

And Toggle status date confirmation checkbox 433ms

And Confirm statuses until reach "process-ended" 6s 183ms

Then Check if transport has "process-ended" 078ms

Hooks

After Hooks.deleteTransportAfterTest() 916ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 107ms

After Hooks.deleteModeOfTransportationAfterTest() 391ms

After Hooks.rollbackTaskChanges() 212ms

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" 222ms

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 284ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 177ms

And Mark custom fields as not obligatory 766ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 727ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 216ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 658ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 402ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 632ms

And Login as "bausch-admin" 6s 331ms

And Go to "TRANSPORT_TABLE" 504ms

And Find transport in table with status "advice-added" 3s 680ms

And Confirm statuses until reach "on-the-way" 16s 709ms

And Open statuses popup 155ms

And Toggle status date confirmation checkbox 396ms

And Change status execution date to "1" days from today 2s 501ms

Then Verify that status cannot be confirmed 1s 233ms

Hooks

After Hooks.deleteTransportAfterTest() 860ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 108ms

After Hooks.deleteModeOfTransportationAfterTest() 338ms

After Hooks.rollbackTaskChanges() 191ms

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" 235ms

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 298ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 181ms

And Mark custom fields as not obligatory 748ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 693ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 158ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 643ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 414ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 601ms

And Login as "bausch-admin" 6s 202ms

And Go to "TRANSPORT_TABLE" 517ms

And Find transport in table with status "advice-added" 3s 665ms

And Confirm statuses until reach "on-the-way" 16s 746ms

And Open statuses popup 148ms

And Toggle status date confirmation checkbox 390ms

And Change status execution date to "-1" days from today 2s 475ms

Then Verify that status cannot be confirmed 1s 240ms

Hooks

After Hooks.deleteTransportAfterTest() 851ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 132ms

After Hooks.deleteModeOfTransportationAfterTest() 335ms

After Hooks.rollbackTaskChanges() 191ms

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) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 252ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 112ms

And Mark custom fields as not obligatory 006ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 988ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 915ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 119ms

When Login as "farmacol-admin" 7s 289ms

And Go to "TRANSPORT_TABLE" 507ms

And Confirm statuses until reach "during-unload" 16s 958ms

And Set actual confirmed transport status list 2s 057ms

And Disable task by API 189ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 968ms

And Edit transport hours and recalculate statuses 30s 647ms

Then Verify that all confirmed statuses are still on transport status list 508ms

Hooks

After Hooks.deleteTransportAfterTest() 750ms

After Hooks.rollbackAllCustomFieldsSettings() 340ms

After Hooks.rollbackTaskChanges() 205ms

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" 233ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 702ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 171ms

And Mark custom fields as not obligatory 744ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 291ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 666ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 402ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "-30m" 4s 677ms

And Login as "super-admin-bausch" 6s 428ms

And Go to "TRANSPORT_TABLE" 522ms

Then Confirm next status and expect alert "Status potwierdzony z opóźnieniem" 1s 658ms

And Wait "1" seconds 1s

And Verify that note was added "Status potwierdzony po czasie" 1s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 833ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 161ms

After Hooks.deleteModeOfTransportationAfterTest() 334ms

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" 231ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 708ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 174ms

And Mark custom fields as not obligatory 755ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 260ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 643ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 398ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "0m" 4s 580ms

And Login as "super-admin-bausch" 6s 397ms

And Go to "TRANSPORT_TABLE" 498ms

Then Confirm next status and expect alert "" 536ms

And Wait "1" seconds 1s

And Verify that note was added "" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 854ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 089ms

After Hooks.deleteModeOfTransportationAfterTest() 327ms

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) 000ms

Steps

Given Set token of apiUsername "super-admin-bausch" 247ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 745ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 168ms

And Mark custom fields as not obligatory 740ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 228ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 655ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 395ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "30m" 4s 496ms

And Login as "super-admin-bausch" 6s 462ms

And Go to "TRANSPORT_TABLE" 450ms

Then Confirm next status and expect alert "Status potwierdzony przed czasem" 1s 092ms

And Wait "1" seconds 1s

And Verify that note was added "Status potwierdzony przed czasem" 1s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 832ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 111ms

After Hooks.deleteModeOfTransportationAfterTest() 323ms

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 552ms

And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 973ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 078ms

And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 754ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 576ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 855ms

And Check if reject date is not visible 15s 038ms

When Reject status: Book of disinfection 210ms

And Check if reject date is visible 1s 042ms

Then If user is login then logout 5s 655ms

And Login as "lantmannen-admin" 2s 174ms

And Check if note was added to transport after status rejection 1s 704ms

And Check if history note was added to transport after status rejection - "LOAD" 7s 314ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 3m 19s 833ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 856ms

After Hooks.cleanUserDetailsAfterTest() 1s 209ms

After Hooks.rollbackWarehousesAccess() 802ms

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) 001ms

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 4s 809ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 996ms

And Check if reject date is not visible 15s 028ms

When Reject status: Book of disinfection 227ms

And Check if reject date is visible 616ms

And Get rejection date 090ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 214ms

Then Check if reject date has changed 1s 206ms

Hooks

After Hooks.deleteTransportAfterTest() 788ms

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 571ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 819ms

And Go to transport details "LOAD" 2s 869ms

And Check if reject date is not visible 15s 027ms

When Reject status: Book of disinfection 199ms

Then Check if reject date is visible 546ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

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 492ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 963ms

And Open statuses popup 257ms

And Check if reject date is not visible 15s 054ms

When Reject status: Book of disinfection 231ms

Then Open statuses popup 159ms

And Check if reject date is visible 423ms

Hooks

After Hooks.deleteTransportAfterTest() 894ms

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 233ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 159ms

And Confirm to the last status by API 1s 373ms

When Find statuses for transport in table 3s 304ms

And Revoke statuses until reach "advice-added" 8s 090ms

Then Check if transport has "advice-added" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 759ms

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 843ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 900ms

And Confirm to the last status by API 1s 415ms

When Find statuses for transport in table 2s 630ms

And Revoke statuses until reach "planned" 8s 232ms

Then Check if transport has "planned" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 864ms

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 950ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 958ms

When Find transport in table with status "new" 3s 698ms

And Open statuses popup 168ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 172ms

Hooks

After Hooks.deleteTransportAfterTest() 568ms

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 543ms

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 019ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 996ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 258ms

And Set advice window in schedule 3s 592ms

And Fill advice form 17s 113ms

And Click advice save button and wait for advice form to disappear 33s 848ms

And Go to "TRANSPORT_TABLE" 487ms

When Find transport in table with status "advice-added" 3s 658ms

And Open statuses popup 165ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 153ms

Hooks

After Hooks.deleteTransportAfterTest() 764ms

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" 230ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 112ms

And Mark custom fields as not obligatory 006ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 960ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 738ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 131ms

When Login as "farmacol-admin" 2s 553ms

And Go to "TRANSPORT_TABLE" 487ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 11s 707ms

And Disable task by API 188ms

And Find transport pencil button in transports table 1s 808ms

And Click pencil and move transport to next day in schedule 23s 335ms

And Go to "TRANSPORT_TABLE" 558ms

Then Verify that "START_OF_UNLOADING" is not visible 428ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

After Hooks.rollbackAllCustomFieldsSettings() 367ms

After Hooks.rollbackTaskChanges() 188ms

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 078ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 207ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 265ms

When Go to "WAREHOUSE_TAB" 1s 341ms

And Select warehouse "Serownia" 1s 612ms

And Set week view 1s 261ms

And Show yesterday 1s 163ms

And Move window into the past 431ms

Then Check if window is "red" 4s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 828ms

After Hooks.rollbackAddedAuthorities() 133ms

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) 000ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 321ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 885ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 188ms

When Go to "WAREHOUSE_TAB" 1s 403ms

And Select warehouse "Magazyn - Nowa Sól" 2s 825ms

And Set week view 1s 260ms

And Show yesterday 1s 164ms

And Move window into the past 606ms

Then Check if window is "red" 4s 073ms

Hooks

After Hooks.deleteTransportAfterTest() 841ms

After Hooks.rollbackAddedAuthorities() 137ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past 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 783ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 020ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 229ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 019ms

When Show all transport types 1s 153ms

And Click button advice in transport table "DELIVERY" 275ms

And Set advice window in schedule 3s 401ms

And Fill advice form 13s 089ms

And Click advice save button and wait for advice form to disappear 33s 853ms

And Select warehouse "Magazyn Hala A" 1s 403ms

And Set week view 2s 470ms

And Show yesterday 1s 252ms

And Move window into the past 1s 008ms

Then Check if window is "red" 4s 085ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:35)

Hooks

After Hooks.deleteTransportAfterTest() 779ms

After Hooks.rollbackAddedAuthorities() 135ms

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" 8s 789ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 020ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 1s 318ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 110ms

When Go to "WAREHOUSE_TAB" 1s 301ms

And Select warehouse "Magazyn Zimny Kaźmierz" 2s 158ms

And Set week view 1s 273ms

And Check if time window length is correct after "CREATE" 086ms

And Change number of pallets in transport 1m 2s 211ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 244ms

And Check if time window length is correct after "EDIT" 092ms

Hooks

After Hooks.deleteTransportAfterTest() 872ms

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 647ms

And Get package type settings for transportType "UNLOAD" from "keeeper" 128ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;true" 228ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 658ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 919ms

When Go to "WAREHOUSE_TAB" 752ms

And Select warehouse "Magazyn Surowców" 1s 367ms

And Set week view 1s 256ms

Then Check if time window has proper "60" 084ms

Hooks

After Hooks.deleteTransportAfterTest() 898ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 139ms

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 094ms

And Get package type settings for transportType "UNLOAD" from "keeeper" 117ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 224ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 630ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 876ms

When Go to "WAREHOUSE_TAB" 719ms

And Select warehouse "Magazyn Surowców" 1s 355ms

And Set week view 1s 255ms

Then Check if time window has proper "60" 068ms

Hooks

After Hooks.deleteTransportAfterTest() 881ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 127ms

After Hooks.clearAlgorithmSettings() 526ms

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 970ms

And Get package type settings for transportType "LOAD" from "keeeper" 127ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 222ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 610ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 917ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 022ms

And Show all transport types 1s 156ms

And Click button advice in transport table "LOAD" 257ms

And Set advice window in schedule 3s 255ms

And Fill advice form 18s 715ms

And Click advice save button and wait for advice form to disappear 33s 274ms

Then Check if time window has proper "30" 081ms

Hooks

After Hooks.deleteTransportAfterTest() 831ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 155ms

After Hooks.clearAlgorithmSettings() 535ms

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 953ms

And Get package type settings for transportType "CONTAINER" from "keeeper" 119ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "20;false" 220ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 619ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 968ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 016ms

And Show all transport types 1s 156ms

And Click button advice in transport table "CONTAINER" 259ms

And Set advice window in schedule 3s 279ms

And Fill advice form 18s 543ms

And Click advice save button and wait for advice form to disappear 33s 230ms

Then Check if time window has proper "60" 087ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 126ms

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" 225ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 807ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 233ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 17s 059ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 7s 596ms

When Go to transport details "DELIVERY" 30s 909ms

And Change filled value in details "number-of-pallets-step-0" "number" "25" "0" 1s 559ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 183ms

And Go to "WAREHOUSE_TAB" 1s 344ms

And Select warehouse "Serownia" 1s 589ms

And Set week view 1s 217ms

Then Check if time window has proper "60" 071ms

Hooks

After Hooks.deleteTransportAfterTest() 820ms

After Hooks.clearAlgorithmSettings() 902ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 085ms

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 952ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 55s 407ms

And Check if time window counter value equals "1" 216ms

And Select view "DAYS_2" 2s 185ms

And Move advice window "2" 1s 492ms

And Select view "DAY" 2s 152ms

Then Check if time window counter value equals "0" 194ms

And Delete created transport by API 779ms

And Check if time window counter value equals "0" 148ms

And Click in free spot in schedule page to create gray window 502ms

And Check if time window counter value equals "0" 183ms

And Click in free spot in schedule page to create dedicated window 2s 165ms

And Check if time window counter value equals "0" 181ms

Hooks

After Hooks.deleteTransportAfterTest() 651ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 018ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 106ms

When Go to new transport "DELIVERY" 745ms

And Fill transport form 13s 558ms

And Click "save-transport" save button and wait for form to disappear 30s 214ms

And Set advice window in schedule 2s 413ms

And Check is transport created in schedule and set transport id 2s 577ms

And Go to "TRANSPORT_TABLE" 530ms

When Click on time window date 1s 703ms

And Open transport form when in schedule 1s 319ms

Then Check are transport values equals 444ms

Hooks

After Hooks.deleteTransportAfterTest() 778ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 021ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 033ms

When Go to new transport "DELIVERY" 730ms

And Fill transport form 46s 485ms

And Click "save-transport" save button and wait for form to disappear 30s 259ms

And Set advice window in schedule 2s 398ms

And Check is transport created in schedule and set transport id 2s 900ms

And Go to "TRANSPORT_TABLE" 566ms

When Click on time window date 1s 658ms

And Open transport form when in schedule 1s 414ms

Then Check are transport values equals 22s 160ms

Hooks

After Hooks.deleteTransportAfterTest() 772ms

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 Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 018ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 109ms

When Go to new transport "CISTERN_DELIVERY" 739ms

And Fill transport form 48s 524ms

And Click "save-transport" save button and wait for form to disappear 30s 255ms

And Set advice window in schedule 2s 477ms

And Check is transport created in schedule and set transport id 2s 671ms

And Go to "TRANSPORT_TABLE" 473ms

When Click on time window date 2s 926ms

And Open transport form when in schedule 1s 405ms

Then Check are transport values equals 9s 178ms

Hooks

After Hooks.deleteTransportAfterTest() 911ms

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 Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 022ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 067ms

When Go to new transport "CISTERN_COLLECTION" 680ms

And Fill transport form 34s 609ms

And Click "save-transport" save button and wait for form to disappear 30s 171ms

And Set advice window in schedule 2s 444ms

And Check is transport created in schedule and set transport id 2s 413ms

And Go to "TRANSPORT_TABLE" 523ms

When Click on time window date 3s 182ms

And Open transport form when in schedule 1s 380ms

Then Check are transport values equals 24s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 747ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 019ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 860ms

When Go to new transport "DELIVERY" 679ms

And Fill transport form 45s 214ms

And Click "save-transport" save button and wait for form to disappear 30s 250ms

And Set advice window in schedule 2s 386ms

And Check is transport created in schedule and set transport id 2s 603ms

And Go to "TRANSPORT_TABLE" 471ms

When Click on time window date 1s 854ms

And Open transport form when in schedule 1s 304ms

Then Check are transport values equals 22s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

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 Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 021ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 507ms

When Go to new transport "LOAD" 676ms

And Fill transport form 45s 229ms

And Click "save-transport" save button and wait for form to disappear 30s 251ms

And Set advice window in schedule 2s 439ms

And Check is transport created in schedule and set transport id 2s 621ms

And Go to "TRANSPORT_TABLE" 560ms

When Click on time window date 1s 786ms

And Open transport form when in schedule 1s 337ms

Then Check are transport values equals 22s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 918ms

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" 234ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 411ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 411ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 281ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 817ms

And Login as "farmacol-admin" 6s 949ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 55s 223ms

And Go to "TRANSPORT_TABLE" 636ms

When Go to transport details "EXTERNAL_DELIVERY" 2s 879ms

And Add step "unload" 220ms

And Change filled value in details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 778ms

And Change filled value in details "weight-step-2" "number" "23" "0" 1s 582ms

And Change filled value in details "number-of-pallets-step-2" "number" "23" "0" 1s 582ms

And Change filled value in details "time-range-from-date-2" "date" "" "0" 3s 769ms

Then Click "save-transport" save button 338ms

And Set advice window in schedule in "2" days 5s 714ms

And Click advice save button and wait for advice form to disappear 34s 915ms

And Go to "TRANSPORT_TABLE" 490ms

And Check if transport has "2" time windows 040ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 084ms

After Hooks.rollbackTransportTypeSettings() 321ms

After Hooks.rollbackAddedActionAuthorities() 321ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 219ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 152ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 260ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 101ms

And Set double window advice 000ms

And Login as "farmacol-admin" 6s 767ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 1m 141ms

And Go to "TRANSPORT_TABLE" 607ms

And Get checkpoint colors for transport 031ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 1m 7s 348ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 044ms

After Hooks.rollbackTransportTypeSettings() 337ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

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" 240ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 157ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 307ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 089ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 715ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 1m 371ms

And Go to "TRANSPORT_TABLE" 591ms

And Get checkpoint colors for transport 023ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 1m 7s 228ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 026ms

After Hooks.rollbackTransportTypeSettings() 362ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

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" 238ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 157ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 274ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 046ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 673ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 1m 398ms

And Get checkpoint colors for transport 016ms

And Go to "TRANSPORT_TABLE" 617ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 9s 712ms

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:247)

Hooks

After Hooks.deleteTransportAfterTest() 946ms

After Hooks.rollbackTransportTypeSettings() 235ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 203ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 173ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 287ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 916ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 664ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 1m 392ms

And Get checkpoint colors for transport 025ms

And Go to "TRANSPORT_TABLE" 602ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 30s 391ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 018ms

After Hooks.rollbackTransportTypeSettings() 372ms

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" 218ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 985ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 807ms

And Login as "super-admin-farmacol" 6s 842ms

And Show all transport types 1s 169ms

And Click on time window date 2s 090ms

Then Open transport form when in schedule 1s 455ms

And Click create similar button 15s 259ms

And Click cancel button in transport form 233ms

And Open transport form when in schedule 1s 319ms

Then Check if transport form modal is visible 085ms

Hooks

After Hooks.deleteTransportAfterTest() 750ms

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" 217ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 896ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 758ms

And Get min and max advice date of created transport as "super-admin-farmacol" 445ms

And Login as "farmacol-admin" 2s 759ms

And Show all transport types 1s 168ms

And Click on time window date 2s 092ms

And Set week view 2s 697ms

And Move advice window "3" 1s 904ms

Then Check if min and max advice date changed after moving advice window as "super-admin-farmacol" 679ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 542ms

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" 222ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 151ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 752ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 399ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "60m" 4s 538ms

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" 6s 526ms

And Go to "WAREHOUSE_TAB" 1s 326ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 725ms

And Wait "2" seconds 2s

When Move window by interval "1h" 557ms

And Alert after moving is displayed "Nie można przesunąć okna czasowego - minął dopuszczalny czas na wykonanie tej akcji" 723ms

Hooks

After Hooks.deleteTransportAfterTest() 824ms

After Hooks.rollbackAddedActionAuthorities() 286ms

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" 218ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 123ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 638ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 399ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "180m" 4s 492ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 331ms

And Login as "super-admin-bausch" 5s 976ms

And Go to "WAREHOUSE_TAB" 1s 272ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 721ms

And Wait "2" seconds 2s

When Move window by interval "1h" 588ms

And Alert after moving is displayed "" 15s 094ms

Hooks

After Hooks.deleteTransportAfterTest() 873ms

After Hooks.rollbackAddedActionAuthorities() 268ms

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" 215ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 165ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 662ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 412ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "180m" 4s 577ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 360ms

And Login as "super-admin-bausch" 5s 879ms

And Go to "WAREHOUSE_TAB" 1s 216ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 660ms

And Wait "2" seconds 2s

When Move window by interval "-2h" 602ms

And Alert after moving is displayed "Nie można przesunąć okna czasowego - minął dopuszczalny czas na wykonanie tej akcji" 675ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

After Hooks.rollbackAddedActionAuthorities() 255ms

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) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 780ms

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" 133ms

And Set proper delay time to move order to archive after task timeout 151ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 909ms

And Go to "WAREHOUSE_TAB" 998ms

And Change warehouse in schedule to: "Katowice" 1s 759ms

And Wait "60" seconds 1m

And Verify that transport window is grey 073ms

And Verify that transport is in archive 7s 388ms

Then Restore transport from archive 2s 905ms

And Verify that transport has been successfully restored 1s 765ms

Hooks

After Hooks.deleteTransportAfterTest() 751ms

After Hooks.rollbackSettings() 134ms

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) 001ms

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 6s 712ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 096ms

When Go to "TRANSPORT_TABLE" 353ms

And Delete transport 19s 593ms

When Go to "ARCHIVE_TAB" 592ms

And Show "OWN_COLLECTION" 199ms

And Verify that created transport is "true" in transport table 15s 154ms

Hooks

After Hooks.deleteTransportAfterTest() 522ms

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) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 208ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 128ms

And Mark custom fields as not obligatory 005ms

And Login as "dayco-admin" 2s 227ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 029ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 144ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 182ms

When Go to "TRANSPORT_TABLE" 395ms

And Click button advice in transport table "OWN_COLLECTION" 1s 314ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 207ms

And Go to "TRANSPORT_TABLE" 477ms

And Find transport in table with status "planned-magazyn-tychy" 3s 722ms

And Confirm statuses until reach "process-ended" 16s 684ms

And Wait until transport disappear from transport table 40s 363ms

Then Go to "ARCHIVE_TAB" 540ms

And Show "OWN_COLLECTION" 187ms

And Verify that created transport is "true" in transport table 15s 126ms

Hooks

After Hooks.deleteTransportAfterTest() 711ms

After Hooks.rollbackAllCustomFieldsSettings() 525ms

After Hooks.rollbackSettings() 125ms

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 "adama-admin" and set token of apiUsername "super-admin-adama" 4s 930ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 091ms

When Fill auction form 16s 190ms

Then Verify that the auction has been added to transport 162ms

Hooks

After Hooks.deleteTransportAfterTest() 632ms

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 891ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 160ms

When Fill auction form 16s 199ms

Then Verify that the auction has been added to transport 164ms

Hooks

After Hooks.deleteTransportAfterTest() 689ms

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 532ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 067ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 813ms

When If user is login then logout 262ms

And Login as "paa1-carrier@qa.qa-test" 4s 881ms

And Go to auction offer 1s 652ms

And Accept transport with minimum rate 17s 008ms

Then Check if carrier is assigned to transport 079ms

Hooks

After Hooks.deleteTransportAfterTest() 604ms

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 476ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 097ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 813ms

When If user is login then logout 262ms

And Login as "paa1-carrier@qa.qa-test" 2s 637ms

And Go to auction offer 1s 662ms

And Reject auction offer 15s 828ms

Then Verify that offer has been removed from transport 15s 136ms

Hooks

After Hooks.deleteTransportAfterTest() 664ms

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 853ms

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 775ms

When If user is login then logout 582ms

And Login as "pskza1-carrier@qa.qa-test" 6s 597ms

And Go to auction offer 2s 611ms

And Reject auction offer 15s 787ms

Then Verify that offer has been removed from transport 15s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 651ms

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 596ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 104ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 850ms

When If user is login then logout 274ms

And Login as "paa1-carrier@qa.qa-test" 2s 473ms

And Go to auction offer 1s 603ms

And Offer prize above maximum - "20000" 533ms

Then Verify that is not possible to add offer 836ms

Hooks

After Hooks.deleteTransportAfterTest() 636ms

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 626ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 115ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 776ms

When If user is login then logout 509ms

And Login as "pskza1-carrier@qa.qa-test" 2s 371ms

And Go to auction offer 2s 695ms

And Offer prize above maximum - "20000" 552ms

Then Verify that is not possible to add offer 897ms

Hooks

After Hooks.deleteTransportAfterTest() 621ms

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 444ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 097ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 796ms

And Wait till auction end 1m 58s 016ms

Then Verify that is possible to add auction 146ms

Hooks

After Hooks.deleteTransportAfterTest() 611ms

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 702ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 099ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 874ms

And Wait till auction end 1m 58s 015ms

Then Verify that is possible to add auction 155ms

Hooks

After Hooks.deleteTransportAfterTest() 625ms

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 764ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 193ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 831ms

And Go to auction offer 1s 560ms

When Offer "1000" 513ms

Then Verify that offer with "1000" has been added to auction 3s 081ms

Hooks

After Hooks.deleteTransportAfterTest() 684ms

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 551ms

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 861ms

And Go to auction offer 1s 517ms

When Offer "1000" 495ms

Then Verify that offer with "1000" has been added to auction 3s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 648ms

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 601ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 294ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 774ms

And Go to auction offer 1s 529ms

When Offer "1000" 454ms

And Verify that offer with "1000" has been added to auction 3s 089ms

Then Go to auction offer 1s 543ms

And Revoke current offer 749ms

And Verify that offer has been revoked 32s 937ms

Hooks

After Hooks.deleteTransportAfterTest() 645ms

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) 000ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 626ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 268ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 821ms

And Go to auction offer 1s 552ms

When Offer "1000" 515ms

And Verify that offer with "1000" has been added to auction 3s 095ms

Then Go to auction offer 1s 534ms

And Offer "1500" 494ms

And Verify that offer with "1500" has been added to auction 3s 077ms

Hooks

After Hooks.deleteTransportAfterTest() 640ms

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 674ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 385ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 806ms

And Go to auction offer 1s 540ms

When Offer "1000" 486ms

And Verify that offer with "1000" has been added to auction 3s 071ms

Then Login as "swisskrono-admin" 2s 419ms

And Go to auction details 2s 238ms

And Finish active auction 165ms

And Verify that the transport has no active auction 716ms

Hooks

After Hooks.deleteTransportAfterTest() 648ms

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 "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 806ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 208ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 840ms

And Go to auction offer 1s 517ms

When Offer "1000" 480ms

Then Verify that carrier can see current place in auction depending on the "true" role 871ms

Hooks

After Hooks.deleteTransportAfterTest() 684ms

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 668ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 279ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 795ms

And Go to auction offer 1s 546ms

When Offer "1000" 484ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 066ms

Hooks

After Hooks.deleteTransportAfterTest() 639ms

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 641ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 321ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 798ms

And Go to auction offer 1s 543ms

When Offer "300" 501ms

And Verify that carrier can't add offer to auction 096ms

Hooks

After Hooks.deleteTransportAfterTest() 647ms

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 301ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 099ms

And Show all transport "false" 078ms

When Go to auction form 1s 592ms

Then Verify carrier selection value "false" 126ms

Hooks

After Hooks.deleteTransportAfterTest() 574ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 478ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 306ms

And Show all transport "true" 235ms

When Go to auction form 1s 548ms

Then Verify carrier selection value "true" 136ms

Hooks

After Hooks.deleteTransportAfterTest() 577ms

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 672ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 056ms

When Open transport auction form 416ms

And Select all companies checkbox in transport auction form 177ms

And Unselect company "PAA2" in transport auction form 184ms

And Put transport on auction 15s 491ms

And Open transport auction history 175ms

And Open participants section in transport auction history 141ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 616ms

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 774ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 108ms

When Open transport auction form 551ms

And Select all companies checkbox in transport auction form 163ms

And Unselect company "PSKZA2" in transport auction form 231ms

And Put transport on auction 15s 435ms

And Open transport auction history 210ms

And Open participants section in transport auction history 149ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 668ms

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" 218ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 2s 394ms

And Set transport on auction with "1000" and "1500" by JSON file as "super-admin-varrocrychvald" 3s 003ms

And Add a bid "1500" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 926ms

And Add a bid "1000" to an auction by JSON file as "pvra2-carrier-2" for "super-admin-varrocrychvald" 952ms

When Login as "varrocrychvald-admin" and set token of apiUsername "super-admin-varrocrychvald" 4s 854ms

And Show all transport "true" 235ms

And Open transport auction history 1s 140ms

And Pass transport to "2" carrier in auction history 1s 194ms

Then Verify if "REASON" is visible in pass transport modal 089ms

And Confirm pass transport to carrier in pass transport modal 157ms

And Verify that "REASON" in pass transport modal has validation error 1s 080ms

Hooks

After Hooks.deleteTransportAfterTest() 690ms

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" 229ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 16s 191ms

And Set transport on auction with "100" and "300" by JSON file as "super-admin-varrocrychvald" 2s 768ms

And Add a bid "100" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 966ms

And Add a bid "200" to an auction by JSON file as "pvra2-carrier" for "super-admin-varrocrychvald" 968ms

And Add a bid "300" to an auction by JSON file as "pvra3-carrier" for "super-admin-varrocrychvald" 944ms

When Login as "pvra1-carrier" 4s 072ms

And Check if current position in auction is "1" 620ms

And If user is login then logout 273ms

And Login as "pvra2-carrier" 4s 496ms

And Check if current position in auction is "2" 628ms

And If user is login then logout 262ms

And Login as "pvra3-carrier" 3s 850ms

And Check if current position in auction is "3" 630ms

Hooks

After Hooks.deleteTransportAfterTest() 674ms

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 473ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 055ms

And Open transport auction form 476ms

And Select all companies checkbox in transport auction form 181ms

And Unselect company "PAA2" in transport auction form 183ms

And Put transport on auction 15s 507ms

When If user is login then logout 315ms

And Login as "paa1-carrier@qa.qa-test" 2s 869ms

And Show "TRANSPORT" 243ms

Then Check if transport is "visible" in table of transports 712ms

And If user is login then logout 266ms

And Login as "paa2-carrier@qa.qa-test" 5s 051ms

And Show "TRANSPORT" 230ms

And Check if transport is "not visible" in table of transports 15s 102ms

Hooks

After Hooks.deleteTransportAfterTest() 731ms

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 Get inputs from database "CREATE_UNLOAD" "super-admin-pgf" 020ms

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 5s 479ms

When Go to new transport "UNLOAD" 15s 576ms

And Fill transport form 32s 799ms

And Click "save-transport" save button and wait for form to disappear 30s 223ms

And Set advice window in schedule 2s 461ms

And Check is transport created in schedule and set transport id 2s 689ms

And Go to "TRANSPORT_TABLE" 533ms

And Go to transport details "UNLOAD" 30s 731ms

Then Check are transport values equals 26s 233ms

Hooks

After Hooks.deleteTransportAfterTest() 800ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 018ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 629ms

When Go to new transport "DELIVERY" 628ms

And Fill transport form 13s 427ms

And Click "save-transport" save button and wait for form to disappear 30s 222ms

And Set advice window in schedule 2s 416ms

And Check is transport created in schedule and set transport id 2s 433ms

And Go to "TRANSPORT_TABLE" 538ms

And Go to transport details "DELIVERY" 2s 740ms

Then Check are transport values equals 447ms

Hooks

After Hooks.deleteTransportAfterTest() 773ms

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 Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-adama" 021ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 521ms

When Go to new transport "OWN_COLLECTION" 616ms

And Fill transport form 22s 944ms

And Click "save-transport" save button and wait for form to disappear 30s 239ms

And Set advice window in schedule 2s 410ms

And Check is transport created in schedule and set transport id 2s 458ms

And Go to "TRANSPORT_TABLE" 482ms

And Go to transport details "OWN_COLLECTION" 2s 707ms

Then Check are transport values equals 2s 637ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 018ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 10s 119ms

When Go to new transport "DELIVERY" 726ms

And Fill transport form 46s 461ms

And Click "save-transport" save button and wait for form to disappear 30s 203ms

And Set advice window in schedule 2s 384ms

And Check is transport created in schedule and set transport id 2s 828ms

And Go to "TRANSPORT_TABLE" 565ms

And Go to transport details "DELIVERY" 2s 885ms

Then Check are transport values equals 22s 415ms

Hooks

After Hooks.deleteTransportAfterTest() 888ms

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 Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 022ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 143ms

When Go to new transport "CISTERN_DELIVERY" 769ms

And Fill transport form 48s 542ms

And Click "save-transport" save button and wait for form to disappear 30s 293ms

And Set advice window in schedule 2s 427ms

And Check is transport created in schedule and set transport id 2s 595ms

And Go to "TRANSPORT_TABLE" 497ms

And Go to transport details "CISTERN_DELIVERY" 2s 864ms

Then Check are transport values equals 9s 144ms

Hooks

After Hooks.deleteTransportAfterTest() 868ms

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 Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 020ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 009ms

When Go to new transport "CISTERN_COLLECTION" 688ms

And Fill transport form 34s 458ms

And Click "save-transport" save button and wait for form to disappear 30s 285ms

And Set advice window in schedule 2s 464ms

And Check is transport created in schedule and set transport id 2s 339ms

And Go to "TRANSPORT_TABLE" 444ms

And Go to transport details "CISTERN_COLLECTION" 3s 001ms

Then Check are transport values equals 24s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 873ms

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 Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-hochland" 021ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 165ms

When Go to new transport "OWN_COLLECTION" 708ms

And Fill transport form 39s 431ms

And Click "save-transport" save button and wait for form to disappear 30s 209ms

And Set advice window in schedule 2s 372ms

And Check is transport created in schedule and set transport id 2s 555ms

And Go to "TRANSPORT_TABLE" 475ms

And Go to transport details "OWN_COLLECTION" 2s 808ms

Then Check are transport values equals 22s 148ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

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 Get inputs from database "CREATE_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 019ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 139ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 714ms

And Fill transport form 39s 466ms

And Click "save-transport" save button and wait for form to disappear 30s 176ms

And Set advice window in schedule 2s 400ms

And Check is transport created in schedule and set transport id 2s 643ms

And Go to "TRANSPORT_TABLE" 478ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 642ms

Then Check are transport values equals 6s 957ms

Hooks

After Hooks.deleteTransportAfterTest() 910ms

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 Get inputs from database "CREATE_EXPORT" "super-admin-hochland" 019ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 146ms

When Go to new transport "EXPORT" 817ms

And Fill transport form 48s 005ms

And Click "save-transport" save button and wait for form to disappear 30s 221ms

And Set advice window in schedule 2s 368ms

And Check is transport created in schedule and set transport id 2s 965ms

And Go to "TRANSPORT_TABLE" 433ms

And Go to transport details "EXPORT" 3s 025ms

Then Check are transport values equals 7s 333ms

Hooks

After Hooks.deleteTransportAfterTest() 947ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-skd" 017ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 4s 793ms

When Go to new transport "DELIVERY" 15s 467ms

And Fill transport form 34s 374ms

And Click "save-transport" save button and wait for form to disappear 30s 241ms

And Set advice window in schedule 2s 410ms

And Check is transport created in schedule and set transport id 2s 489ms

And Go to "TRANSPORT_TABLE" 534ms

And Go to transport details "DELIVERY" 30s 645ms

Then Check are transport values equals 39s 077ms

Hooks

After Hooks.deleteTransportAfterTest() 728ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 021ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 904ms

When Go to new transport "DELIVERY" 692ms

And Fill transport form 45s 024ms

And Click "save-transport" save button and wait for form to disappear 30s 265ms

And Set advice window in schedule 2s 412ms

And Check is transport created in schedule and set transport id 2s 568ms

And Go to "TRANSPORT_TABLE" 447ms

And Go to transport details "DELIVERY" 2s 750ms

Then Check are transport values equals 22s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 932ms

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 Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 018ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 560ms

When Go to new transport "LOAD" 664ms

And Fill transport form 45s 077ms

And Click "save-transport" save button and wait for form to disappear 30s 232ms

And Set advice window in schedule 2s 401ms

And Check is transport created in schedule and set transport id 2s 568ms

And Go to "TRANSPORT_TABLE" 552ms

And Go to transport details "LOAD" 2s 747ms

Then Check are transport values equals 22s 034ms

Hooks

After Hooks.deleteTransportAfterTest() 787ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-keeeper" 020ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 883ms

When Go to new transport "UNLOAD" 673ms

And Fill transport form 45s 033ms

And Click "save-transport" save button and wait for form to disappear 30s 192ms

And Set advice window in schedule 2s 408ms

And Check is transport created in schedule and set transport id 2s 729ms

And Go to "TRANSPORT_TABLE" 484ms

And Go to transport details "UNLOAD" 2s 848ms

Then Check are transport values equals 24s 216ms

Hooks

After Hooks.deleteTransportAfterTest() 880ms

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 Get inputs from database "CREATE_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 018ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 612ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 664ms

And Fill transport form 44s 782ms

And Click "save-transport" save button and wait for form to disappear 30s 245ms

And Set advice window in schedule 2s 344ms

And Check is transport created in schedule and set transport id 2s 707ms

And Go to "TRANSPORT_TABLE" 459ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 779ms

Then Check are transport values equals 24s 339ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 018ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-alrec" 021ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 623ms

When Go to new transport "DELIVERY" 651ms

And Fill transport form 28s 718ms

And Click "save-transport" save button and wait for form to disappear 30s 175ms

And Set advice window in schedule 2s 423ms

And Check is transport created in schedule and set transport id 2s 471ms

And Go to "TRANSPORT_TABLE" 453ms

And Go to transport details "DELIVERY" 2s 711ms

Then Check are transport values equals 19s 819ms

Hooks

After Hooks.deleteTransportAfterTest() 717ms

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 Get inputs from database "CREATE_WEIGHING" "super-admin-hochland" 017ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 153ms

When Go to new transport "WEIGHING" 646ms

And Fill transport form 18s 188ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 236ms

And Show all transport "false" 065ms

And Go to "TRANSPORT_TABLE" 423ms

And Go to transport details "WEIGHING" 2s 933ms

And Check are transport values equals 4s 568ms

Hooks

After Hooks.deleteTransportAfterTest() 521ms

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 Get inputs from database "CREATE_TRANSPORT" "super-admin-adama" 018ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 613ms

When Go to new transport "TRANSPORT" 734ms

And Fill transport form 29s 131ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 258ms

And Show all transport "false" 082ms

And Go to "TRANSPORT_TABLE" 427ms

And Go to transport details "TRANSPORT" 2s 915ms

And Check are transport values equals 6s 667ms

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 Get inputs from database "CREATE_CONTAINER" "super-admin-adama" 019ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 603ms

When Go to new transport "CONTAINER" 662ms

And Fill transport form 12s 146ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 232ms

And Show all transport "false" 072ms

And Go to "TRANSPORT_TABLE" 449ms

And Go to transport details "CONTAINER" 2s 896ms

And Check are transport values equals 226ms

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 Get inputs from database "CREATE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 020ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 005ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 697ms

And Fill transport form 14s 289ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 235ms

And Show all transport "false" 077ms

And Go to "TRANSPORT_TABLE" 376ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 963ms

And Check are transport values equals 4s 753ms

Hooks

After Hooks.deleteTransportAfterTest() 523ms

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 Get inputs from database "CREATE_DELIVERY" "super-admin-piast" 020ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 931ms

When Go to new transport "DELIVERY" 637ms

And Fill transport form 24s 815ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 221ms

And Show all transport "false" 080ms

And Go to "TRANSPORT_TABLE" 379ms

And Go to transport details "DELIVERY" 2s 904ms

And Check are transport values equals 17s 809ms

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) 000ms

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-piast" 020ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 719ms

When Go to new transport "LOAD" 744ms

And Fill transport form 28s 603ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 251ms

And Show all transport "false" 077ms

And Go to "TRANSPORT_TABLE" 396ms

And Go to transport details "LOAD" 2s 999ms

And Check are transport values equals 2s 679ms

Hooks

After Hooks.deleteTransportAfterTest() 503ms

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 Get inputs from database "CREATE_LOAD" "super-admin-keeeper" 020ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 725ms

When Go to new transport "LOAD" 608ms

And Fill transport form 27s 226ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 214ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 433ms

And Go to transport details "LOAD" 2s 808ms

And Check are transport values equals 19s 599ms

Hooks

After Hooks.deleteTransportAfterTest() 476ms

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 Get inputs from database "CREATE_CONTAINER" "super-admin-keeeper" 021ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 594ms

When Go to new transport "CONTAINER" 634ms

And Fill transport form 27s 241ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 246ms

And Show all transport "false" 079ms

And Go to "TRANSPORT_TABLE" 459ms

And Go to transport details "CONTAINER" 2s 826ms

And Check are transport values equals 19s 655ms

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 Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 022ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 738ms

When Go to new transport "SMALLS_IMPORT" 734ms

And Fill transport form 40s 144ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 199ms

And Show all transport "false" 075ms

And Go to "TRANSPORT_TABLE" 385ms

And Go to transport details "SMALLS_IMPORT" 2s 921ms

And Check are transport values equals 11s 157ms

Hooks

After Hooks.deleteTransportAfterTest() 636ms

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 Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 021ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 746ms

When Go to new transport "SMALLS_EXPORT" 726ms

And Fill transport form 40s 129ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 269ms

And Show all transport "false" 075ms

And Go to "TRANSPORT_TABLE" 441ms

And Go to transport details "SMALLS_EXPORT" 2s 891ms

And Check are transport values equals 11s 114ms

Hooks

After Hooks.deleteTransportAfterTest() 611ms

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 Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 019ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 654ms

When Go to new transport "TRANSPORT_ORDER" 731ms

And Fill transport form 33s 331ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 230ms

And Show all transport "true" 242ms

And Go to "TRANSPORT_TABLE" 375ms

And Go to transport details "TRANSPORT_ORDER" 2s 889ms

And Check are transport values equals 19s 889ms

Hooks

After Hooks.deleteTransportAfterTest() 535ms

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 Get inputs from database "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 019ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 561ms

When Go to new transport "TRANSPORT" 752ms

And Fill transport form 40s 788ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 273ms

And Show all transport "false" 072ms

And Go to "TRANSPORT_TABLE" 386ms

And Go to transport details "TRANSPORT" 2s 843ms

And Check are transport values equals 4s 567ms

Hooks

After Hooks.deleteTransportAfterTest() 582ms

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 Get inputs from database "CREATE_INBOUND_WITHOUT_WAREHOUSES" "super-admin-alrec" 021ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 446ms

When Go to new transport "INBOUND" 725ms

And Fill transport form 44s 883ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 252ms

And Show all transport "true" 245ms

And Go to "TRANSPORT_TABLE" 378ms

And Go to transport details "INBOUND" 2s 933ms

And Check are transport values equals 2s 878ms

Hooks

After Hooks.deleteTransportAfterTest() 529ms

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 Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 020ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 7s 132ms

When Go to new transport "EXTERNAL_DELIVERY" 694ms

And Fill transport form 59s 795ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 293ms

And Show all transport "false" 075ms

And Go to "TRANSPORT_TABLE" 361ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 923ms

And Check are transport values equals 5s 489ms

Hooks

After Hooks.deleteTransportAfterTest() 535ms

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 Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "dfa1-supplier" 022ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 6s 822ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 542ms

And Fill transport form 52s 707ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 233ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 406ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 893ms

And Check are transport values equals 5s 422ms

Hooks

After Hooks.deleteTransportAfterTest() 586ms

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 404ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 020ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 741ms

And Show all transport "false" 072ms

When Go to transport details "UNLOAD" 30s 812ms

And Fill transport form 36s 176ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 222ms

And Go to transport details "UNLOAD" 30s 760ms

Then Check are transport values equals 6s 939ms

Hooks

After Hooks.deleteTransportAfterTest() 755ms

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 521ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 021ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 116ms

And Show all transport "false" 075ms

When Go to transport details "TRANSPORT" 2s 947ms

And Fill transport form 11s 267ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 247ms

And Go to transport details "TRANSPORT" 2s 907ms

Then Check are transport values equals 4s 390ms

Hooks

After Hooks.deleteTransportAfterTest() 551ms

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 502ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 019ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 859ms

And Show all transport "false" 080ms

When Go to transport details "CONTAINER" 2s 921ms

And Fill transport form 5s 150ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 238ms

And Go to transport details "CONTAINER" 2s 830ms

Then Check are transport values equals 157ms

Hooks

After Hooks.deleteTransportAfterTest() 506ms

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 579ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 873ms

And Show all transport "false" 075ms

When Go to transport details "DELIVERY" 2s 843ms

And Fill transport form 15s 941ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 221ms

And Go to transport details "DELIVERY" 2s 798ms

Then Check are transport values equals 2s 473ms

Hooks

After Hooks.deleteTransportAfterTest() 685ms

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 505ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 021ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 794ms

And Show all transport "false" 075ms

When Go to transport details "OWN_COLLECTION" 2s 770ms

And Fill transport form 26s 549ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 186ms

And Go to transport details "OWN_COLLECTION" 2s 763ms

Then Check are transport values equals 4s 738ms

Hooks

After Hooks.deleteTransportAfterTest() 702ms

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 220ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 142ms

And Show all transport "false" 079ms

When Go to transport details "DELIVERY" 2s 947ms

And Fill transport form 43s 195ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 277ms

And Go to transport details "DELIVERY" 2s 883ms

Then Check are transport values equals 13s 572ms

Hooks

After Hooks.deleteTransportAfterTest() 871ms

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 939ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 020ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 901ms

And Show all transport "false" 080ms

When Go to transport details "OWN_COLLECTION" 2s 939ms

And Fill transport form 43s 461ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 214ms

And Go to transport details "OWN_COLLECTION" 2s 898ms

Then Check are transport values equals 9s 185ms

Hooks

After Hooks.deleteTransportAfterTest() 807ms

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 104ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 020ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 099ms

And Show all transport "false" 076ms

When Go to transport details "EXPORT" 3s 085ms

And Fill transport form 56s 124ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 219ms

And Go to transport details "EXPORT" 2s 964ms

Then Check are transport values equals 11s 431ms

Hooks

After Hooks.deleteTransportAfterTest() 825ms

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 137ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 020ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 955ms

And Show all transport "false" 076ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 969ms

And Fill transport form 39s 897ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 279ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 907ms

Then Check are transport values equals 13s 415ms

Hooks

After Hooks.deleteTransportAfterTest() 576ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 108ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 020ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 726ms

And Show all transport "false" 082ms

When Go to transport details "CISTERN_DELIVERY" 2s 902ms

And Fill transport form 33s 018ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 203ms

And Go to transport details "CISTERN_DELIVERY" 2s 913ms

Then Check are transport values equals 8s 932ms

Hooks

After Hooks.deleteTransportAfterTest() 759ms

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 105ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 019ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 648ms

And Show all transport "false" 075ms

When Go to transport details "CISTERN_COLLECTION" 2s 864ms

And Fill transport form 31s 148ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 233ms

And Go to transport details "CISTERN_COLLECTION" 2s 864ms

Then Check are transport values equals 8s 875ms

Hooks

After Hooks.deleteTransportAfterTest() 773ms

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 028ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 020ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 186ms

And Show all transport "false" 085ms

When Go to transport details "WEIGHING" 2s 906ms

And Fill transport form 16s 406ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 184ms

And Go to transport details "WEIGHING" 2s 781ms

Then Check are transport values equals 4s 508ms

Hooks

After Hooks.deleteTransportAfterTest() 523ms

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 977ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 020ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 789ms

And Show all transport "false" 076ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 280ms

And Fill transport form 41s 829ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 243ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 858ms

Then Check are transport values equals 9s 068ms

Hooks

After Hooks.deleteTransportAfterTest() 805ms

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 624ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 583ms

And Show all transport "false" 074ms

When Go to transport details "DELIVERY" 30s 782ms

And Fill transport form 30s 888ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 237ms

And Go to transport details "DELIVERY" 30s 620ms

Then Check are transport values equals 4s 695ms

Hooks

After Hooks.deleteTransportAfterTest() 759ms

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 673ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 020ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 970ms

And Show all transport "false" 075ms

When Go to transport details "LOAD" 2s 985ms

And Fill transport form 1m 3s 097ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 198ms

And Go to transport details "LOAD" 2s 938ms

Then Check are transport values equals 26s 391ms

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 "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 622ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 957ms

And Show all transport "false" 082ms

When Go to transport details "DELIVERY" 2s 930ms

And Fill transport form 17s 955ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 227ms

And Go to transport details "DELIVERY" 2s 756ms

Then Check are transport values equals 204ms

Hooks

After Hooks.deleteTransportAfterTest() 757ms

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 507ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 021ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 795ms

And Show all transport "false" 075ms

When Go to transport details "LOAD" 2s 823ms

And Fill transport form 34s 129ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 200ms

And Go to transport details "LOAD" 2s 790ms

Then Check are transport values equals 4s 844ms

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 695ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 904ms

And Show all transport "false" 081ms

When Go to transport details "UNLOAD" 2s 941ms

And Fill transport form 44s 956ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 241ms

And Go to transport details "UNLOAD" 2s 758ms

Then Check are transport values equals 9s 123ms

Hooks

After Hooks.deleteTransportAfterTest() 696ms

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 562ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 028ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 900ms

And Show all transport "false" 072ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 969ms

And Fill transport form 42s 871ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 187ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 831ms

Then Check are transport values equals 9s 124ms

Hooks

After Hooks.deleteTransportAfterTest() 787ms

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 691ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 020ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 923ms

And Show all transport "false" 074ms

When Go to transport details "LOAD" 2s 778ms

And Fill transport form 28s 878ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 263ms

And Go to transport details "LOAD" 2s 786ms

Then Check are transport values equals 4s 734ms

Hooks

After Hooks.deleteTransportAfterTest() 509ms

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 639ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 020ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 934ms

And Show all transport "false" 077ms

When Go to transport details "CONTAINER" 2s 808ms

And Fill transport form 28s 585ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 294ms

And Go to transport details "CONTAINER" 2s 764ms

Then Check are transport values equals 4s 670ms

Hooks

After Hooks.deleteTransportAfterTest() 581ms

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 713ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 020ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 084ms

And Show all transport "false" 078ms

When Go to transport details "SMALLS_EXPORT" 2s 925ms

And Fill transport form 36s 579ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 213ms

And Go to transport details "SMALLS_EXPORT" 2s 873ms

Then Check are transport values equals 9s 005ms

Hooks

After Hooks.deleteTransportAfterTest() 587ms

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 515ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 722ms

And Show all transport "true" 255ms

When Go to transport details "DELIVERY" 2s 862ms

And Fill transport form 24s 965ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 211ms

And Go to transport details "DELIVERY" 2s 706ms

Then Check are transport values equals 2s 609ms

Hooks

After Hooks.deleteTransportAfterTest() 714ms

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 643ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 021ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 236ms

And Show all transport "true" 247ms

When Go to transport details "TRANSPORT_ORDER" 2s 902ms

And Fill transport form 29s 645ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 239ms

And Go to transport details "TRANSPORT_ORDER" 2s 866ms

Then Check are transport values equals 2s 732ms

Hooks

After Hooks.deleteTransportAfterTest() 537ms

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 401ms

And Get inputs from database "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 020ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 863ms

And Show all transport "false" 077ms

When Go to transport details "CONTAINER" 2s 852ms

And Fill transport form 11s 264ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 267ms

And Go to transport details "CONTAINER" 2s 775ms

Then Check are transport values equals 4s 407ms

Hooks

After Hooks.deleteTransportAfterTest() 530ms

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 108ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 134ms

And Show all transport "false" 082ms

When Delete transport 21s 408ms

Then Transport not displayed in table of transports 15s 126ms

Hooks

After Hooks.deleteTransportAfterTest() 721ms

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 674ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 009ms

And Show all transport "false" 073ms

When Delete transport 20s 906ms

Then Transport not displayed in table of transports 15s 132ms

Hooks

After Hooks.deleteTransportAfterTest() 524ms

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 485ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 827ms

And Show all transport "false" 079ms

When Delete transport 20s 756ms

Then Transport not displayed in table of transports 15s 090ms

Hooks

After Hooks.deleteTransportAfterTest() 11s 329ms

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 710ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 960ms

And Show all transport "false" 074ms

When Delete transport 18s 268ms

Then Transport not displayed in table of transports 15s 086ms

Hooks

After Hooks.deleteTransportAfterTest() 478ms

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 690ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 171ms

And Show all transport "false" 081ms

When Delete transport 18s 641ms

Then Transport not displayed in table of transports 15s 100ms

Hooks

After Hooks.deleteTransportAfterTest() 544ms

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 718ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 155ms

And Show all transport "false" 085ms

When Delete transport 18s 777ms

Then Transport not displayed in table of transports 15s 125ms

Hooks

After Hooks.deleteTransportAfterTest() 547ms

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 690ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 809ms

And Show all transport "true" 283ms

When Delete transport 19s 505ms

Then Transport not displayed in table of transports 15s 119ms

Hooks

After Hooks.deleteTransportAfterTest() 648ms

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 513ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 214ms

And Show all transport "true" 251ms

When Delete transport 19s 156ms

Then Transport not displayed in table of transports 15s 085ms

Hooks

After Hooks.deleteTransportAfterTest() 541ms

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 427ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 021ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 879ms

And Show all transport "false" 071ms

When Go to transport details "UNLOAD" 30s 801ms

And Fill transport form 36s 254ms

And Click "save-transport" save button 4s 351ms

And Click cancel button in transport form 185ms

And Go to transport details "UNLOAD" 30s 680ms

Then Check are transport values equals 6s 912ms

Hooks

After Hooks.deleteTransportAfterTest() 808ms

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 518ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 020ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 089ms

And Show all transport "false" 078ms

When Go to transport details "TRANSPORT" 2s 970ms

And Fill transport form 11s 261ms

And Click "save-transport" save button 2s 037ms

And Click cancel button in transport form 153ms

And Go to transport details "TRANSPORT" 2s 843ms

Then Check are transport values equals 4s 373ms

Hooks

After Hooks.deleteTransportAfterTest() 544ms

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 586ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 021ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 872ms

And Show all transport "false" 074ms

When Go to transport details "CONTAINER" 2s 815ms

And Fill transport form 5s 183ms

And Click "save-transport" save button 2s 070ms

And Click cancel button in transport form 169ms

And Go to transport details "CONTAINER" 2s 748ms

Then Check are transport values equals 129ms

Hooks

After Hooks.deleteTransportAfterTest() 472ms

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 554ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 719ms

And Show all transport "false" 085ms

When Go to transport details "DELIVERY" 2s 868ms

And Fill transport form 16s 147ms

And Click "save-transport" save button 2s 076ms

And Click cancel button in transport form 207ms

And Go to transport details "DELIVERY" 2s 819ms

Then Check are transport values equals 2s 476ms

Hooks

After Hooks.deleteTransportAfterTest() 681ms

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 536ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 020ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 804ms

And Show all transport "false" 074ms

When Go to transport details "OWN_COLLECTION" 2s 853ms

And Fill transport form 26s 778ms

And Click "save-transport" save button 2s 596ms

And Click cancel button in transport form 197ms

And Go to transport details "OWN_COLLECTION" 2s 759ms

Then Check are transport values equals 4s 715ms

Hooks

After Hooks.deleteTransportAfterTest() 722ms

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 049ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 130ms

And Show all transport "false" 077ms

When Go to transport details "DELIVERY" 2s 958ms

And Fill transport form 43s 145ms

And Click "save-transport" save button 3s 164ms

And Click cancel button in transport form 169ms

And Go to transport details "DELIVERY" 2s 885ms

Then Check are transport values equals 13s 622ms

Hooks

After Hooks.deleteTransportAfterTest() 881ms

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 129ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 021ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 965ms

And Show all transport "false" 081ms

When Go to transport details "OWN_COLLECTION" 2s 923ms

And Fill transport form 43s 418ms

And Click "save-transport" save button 2s 751ms

And Click cancel button in transport form 196ms

And Go to transport details "OWN_COLLECTION" 2s 834ms

Then Check are transport values equals 9s 116ms

Hooks

After Hooks.deleteTransportAfterTest() 822ms

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 109ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 022ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 115ms

And Show all transport "false" 077ms

When Go to transport details "EXPORT" 3s 119ms

And Fill transport form 56s 288ms

And Click "save-transport" save button 2s 761ms

And Click cancel button in transport form 214ms

And Go to transport details "EXPORT" 2s 875ms

Then Check are transport values equals 11s 458ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

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 055ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 020ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 953ms

And Show all transport "false" 079ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 923ms

And Fill transport form 39s 938ms

And Click "save-transport" save button 2s 355ms

And Click cancel button in transport form 197ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 809ms

Then Check are transport values equals 13s 342ms

Hooks

After Hooks.deleteTransportAfterTest() 604ms

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 132ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 020ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 727ms

And Show all transport "false" 073ms

When Go to transport details "CISTERN_DELIVERY" 2s 902ms

And Fill transport form 32s 915ms

And Click "save-transport" save button 2s 588ms

And Click cancel button in transport form 180ms

And Go to transport details "CISTERN_DELIVERY" 2s 839ms

Then Check are transport values equals 8s 950ms

Hooks

After Hooks.deleteTransportAfterTest() 819ms

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" 2s 985ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 022ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 660ms

And Show all transport "false" 075ms

When Go to transport details "CISTERN_COLLECTION" 2s 896ms

And Fill transport form 31s 358ms

And Click "save-transport" save button 2s 073ms

And Click cancel button in transport form 214ms

And Go to transport details "CISTERN_COLLECTION" 2s 817ms

Then Check are transport values equals 8s 864ms

Hooks

After Hooks.deleteTransportAfterTest() 803ms

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" 2s 906ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 020ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 197ms

And Show all transport "false" 082ms

When Go to transport details "WEIGHING" 2s 916ms

And Fill transport form 16s 504ms

And Click "save-transport" save button 2s 078ms

And Click cancel button in transport form 176ms

And Go to transport details "WEIGHING" 2s 743ms

Then Check are transport values equals 4s 529ms

Hooks

After Hooks.deleteTransportAfterTest() 479ms

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" 2s 928ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 021ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 826ms

And Show all transport "false" 074ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 006ms

And Fill transport form 41s 908ms

And Click "save-transport" save button 2s 662ms

And Click cancel button in transport form 193ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 769ms

Then Check are transport values equals 9s 112ms

Hooks

After Hooks.deleteTransportAfterTest() 812ms

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 704ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 604ms

And Show all transport "false" 074ms

When Go to transport details "DELIVERY" 30s 658ms

And Fill transport form 30s 740ms

And Click "save-transport" save button 2s 039ms

And Click cancel button in transport form 185ms

And Go to transport details "DELIVERY" 30s 578ms

Then Check are transport values equals 4s 691ms

Hooks

After Hooks.deleteTransportAfterTest() 739ms

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 590ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 021ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 986ms

And Show all transport "false" 075ms

When Go to transport details "LOAD" 2s 983ms

And Fill transport form 1m 3s 066ms

And Click "save-transport" save button 2s 779ms

And Click cancel button in transport form 193ms

And Go to transport details "LOAD" 2s 749ms

Then Check are transport values equals 26s 377ms

Hooks

After Hooks.deleteTransportAfterTest() 651ms

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 585ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 880ms

And Show all transport "false" 080ms

When Go to transport details "DELIVERY" 2s 911ms

And Fill transport form 17s 967ms

And Click "save-transport" save button 2s 018ms

And Click cancel button in transport form 179ms

And Go to transport details "DELIVERY" 2s 771ms

Then Check are transport values equals 242ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

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 463ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 021ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 877ms

And Show all transport "false" 077ms

When Go to transport details "LOAD" 2s 812ms

And Fill transport form 34s 234ms

And Click "save-transport" save button 4s 304ms

And Click cancel button in transport form 187ms

And Go to transport details "LOAD" 2s 765ms

Then Check are transport values equals 4s 745ms

Hooks

After Hooks.deleteTransportAfterTest() 749ms

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 647ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 867ms

And Show all transport "false" 084ms

When Go to transport details "UNLOAD" 2s 975ms

And Fill transport form 44s 868ms

And Click "save-transport" save button 2s 589ms

And Click cancel button in transport form 170ms

And Go to transport details "UNLOAD" 2s 821ms

Then Check are transport values equals 9s 276ms

Hooks

After Hooks.deleteTransportAfterTest() 861ms

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 519ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 020ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 933ms

And Show all transport "false" 075ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 965ms

And Fill transport form 43s 288ms

And Click "save-transport" save button 2s 603ms

And Click cancel button in transport form 178ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 792ms

Then Check are transport values equals 9s 190ms

Hooks

After Hooks.deleteTransportAfterTest() 834ms

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 646ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 021ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 880ms

And Show all transport "false" 066ms

When Go to transport details "LOAD" 2s 740ms

And Fill transport form 28s 767ms

And Click "save-transport" save button 2s 067ms

And Click cancel button in transport form 168ms

And Go to transport details "LOAD" 2s 730ms

Then Check are transport values equals 4s 628ms

Hooks

After Hooks.deleteTransportAfterTest() 553ms

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 607ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 021ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 946ms

And Show all transport "false" 076ms

When Go to transport details "CONTAINER" 2s 782ms

And Fill transport form 28s 930ms

And Click "save-transport" save button 2s 046ms

And Click cancel button in transport form 181ms

And Go to transport details "CONTAINER" 2s 731ms

Then Check are transport values equals 4s 693ms

Hooks

After Hooks.deleteTransportAfterTest() 524ms

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 822ms

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 020ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 130ms

And Show all transport "false" 082ms

When Go to transport details "SMALLS_IMPORT" 3s 006ms

And Fill transport form 36s 357ms

And Click "save-transport" save button 2s 040ms

And Click cancel button in transport form 241ms

And Go to transport details "SMALLS_IMPORT" 2s 813ms

Then Check are transport values equals 8s 963ms

Hooks

After Hooks.deleteTransportAfterTest() 614ms

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 640ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 020ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 151ms

And Show all transport "false" 083ms

When Go to transport details "SMALLS_EXPORT" 2s 853ms

And Fill transport form 36s 388ms

And Click "save-transport" save button 2s 066ms

And Click cancel button in transport form 186ms

And Go to transport details "SMALLS_EXPORT" 2s 819ms

Then Check are transport values equals 9s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 604ms

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 647ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 824ms

And Show all transport "true" 296ms

When Go to transport details "DELIVERY" 2s 780ms

And Fill transport form 25s 070ms

And Click "save-transport" save button 2s 624ms

And Click cancel button in transport form 195ms

And Go to transport details "DELIVERY" 2s 672ms

Then Check are transport values equals 2s 504ms

Hooks

After Hooks.deleteTransportAfterTest() 716ms

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 555ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 021ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 162ms

And Show all transport "true" 225ms

When Go to transport details "TRANSPORT_ORDER" 2s 870ms

And Fill transport form 29s 462ms

And Click "save-transport" save button 2s 068ms

And Click cancel button in transport form 167ms

And Go to transport details "TRANSPORT_ORDER" 2s 769ms

Then Check are transport values equals 2s 710ms

Hooks

After Hooks.deleteTransportAfterTest() 589ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if firstPossibleStart algorithm works properly when creating transport advice

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 658ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 032ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 1s 307ms

And If user is login then logout 263ms

Then Login as "dka1-supplier" 5s 989ms

And Click button advice in transport table "LOAD" 812ms

And Check if moved to first possible start date in schedule 1s 216ms

Hooks

After Hooks.deleteTransportAfterTest() 540ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 31s 681ms

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" 246ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 001ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 737ms

Then Go to new transport "LOAD" 709ms

And Fill transport form 26s 140ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 240ms

And Go to "COMPANIES_TAB" 1s 029ms

And Go to company "Dostawca Piast Automat 1" details 577ms

And Check if new address with "Adresat" is visible in company details 398ms

And Go to "TRANSPORT_TABLE" 544ms

And Go to transport details "LOAD" 2s 922ms

Hooks

After Hooks.deleteTransportAfterTest() 794ms

After Hooks.deleteAddressAfterTest() 120ms

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 915ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 001ms

When Go to "TRANSPORT_TABLE" 424ms

And Show all transport types 1s 153ms

And Verify that transport has "0" files 080ms

Then Add file to transport by API 1s 571ms

And Verify that transport has "1" files 2s 652ms

Hooks

After Hooks.deleteTransportAfterTest() 620ms

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 456ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 934ms

When Go to "TRANSPORT_TABLE" 366ms

And Show all transport types 1s 146ms

And Verify that transport has "0" files 092ms

Then Add file to transport by API 1s 634ms

And Verify that transport has "1" files 1s 516ms

Hooks

After Hooks.deleteTransportAfterTest() 560ms

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 808ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 142ms

When Go to "TRANSPORT_TABLE" 405ms

And Show all transport types 1s 152ms

And Verify that transport has "0" files 081ms

Then Add file to transport by API 1s 377ms

And Verify that transport has "1" files 468ms

Hooks

After Hooks.deleteTransportAfterTest() 885ms

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 674ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 919ms

When Go to "TRANSPORT_TABLE" 353ms

And Show all transport types 1s 140ms

And Verify that transport has "0" files 086ms

Then Add file to transport by API 1s 479ms

And Verify that transport has "1" files 459ms

Hooks

After Hooks.deleteTransportAfterTest() 542ms

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 458ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 985ms

And Delete transport 18s 095ms

When Go to "ARCHIVE_TAB" 512ms

And Show "DELIVERY" 152ms

And Verify that transport has "0" files 6s 093ms

Then Add file to transport 440ms

And Verify that transport has "1" files 1s 523ms

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 "piast-admin" and set token of apiUsername "super-admin-piast" 2s 711ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 989ms

And Delete transport 18s 596ms

When Go to "ARCHIVE_TAB" 580ms

And Show "LOAD" 231ms

And Verify that transport has "0" files 4s 497ms

Then Add file to transport 430ms

And Verify that transport has "1" files 1s 630ms

Hooks

After Hooks.deleteTransportAfterTest() 505ms

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 045ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 113ms

And Delete transport 21s 628ms

When Go to "ARCHIVE_TAB" 579ms

And Show "DELIVERY" 153ms

And Verify that transport has "0" files 5s 478ms

Then Add file to transport 408ms

And Verify that transport has "1" files 1s 523ms

Hooks

After Hooks.deleteTransportAfterTest() 707ms

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 612ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 964ms

And Delete transport 18s 498ms

When Go to "ARCHIVE_TAB" 512ms

And Show "CONTAINER" 189ms

And Verify that transport has "0" files 3s 466ms

Then Add file to transport 397ms

And Verify that transport has "1" files 1s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 492ms

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" 248ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 922ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 664ms

And Accept transferred transport by Api 716ms

And Login as "paa1-carrier@qa.qa-test" 2s 481ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 785ms

Hooks

After Hooks.deleteTransportAfterTest() 585ms

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 862ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 172ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 881ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 845ms

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" 221ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 106ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 909ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 614ms

And Login as "paa1-carrier@qa.qa-test" 2s 472ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 756ms

Hooks

After Hooks.deleteTransportAfterTest() 574ms

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 596ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 232ms

When Go to "TRANSPORT_TABLE" 419ms

And Show all transport "true" 259ms

Then Verify that transport has "1" CMR file 1s 683ms

Hooks

After Hooks.deleteTransportAfterTest() 594ms

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 499ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 375ms

When Go to "TRANSPORT_TABLE" 414ms

And Show all transport "true" 241ms

Then Verify that transport has "2" CMR file 1s 688ms

Hooks

After Hooks.deleteTransportAfterTest() 591ms

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 321ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 392ms

When Go to "TRANSPORT_TABLE" 418ms

And Show all transport "true" 256ms

Then Verify that "CMR" document can be downloaded 19s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 589ms

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 482ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 477ms

And Show all transport "true" 237ms

And Delete transport 19s 191ms

When Go to "ARCHIVE_TAB" 557ms

And Show "TRANSPORT_ORDER" 156ms

Then Verify that "CMR" document can be downloaded 20s 714ms

Hooks

After Hooks.deleteTransportAfterTest() 581ms

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 053ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 128ms

And Show all transport "false" 081ms

When Find transport pencil button in transports table 1s 782ms

And Click pencil and move transport to next day in schedule 20s 761ms

Then Check if transport is in new location in schedule 2s 285ms

And Check if dates in transport form are correct 4s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 831ms

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 563ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 555ms

And Show all transport "false" 076ms

When Find transport pencil button in transports table 1s 809ms

And Click pencil and move transport to next day in schedule 20s 615ms

Then Check if transport is in new location in schedule 2s 298ms

And Check if dates in transport form are correct 3s 928ms

Hooks

After Hooks.deleteTransportAfterTest() 687ms

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 618ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 888ms

And Show all transport "false" 074ms

When Find transport pencil button in transports table 1s 791ms

And Click pencil and move transport to next day in schedule 21s 567ms

Then Check if transport is in new location in schedule 2s 329ms

And Check if dates in transport form are correct 3s 936ms

Hooks

After Hooks.deleteTransportAfterTest() 794ms

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 733ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 957ms

And Show all transport "false" 077ms

When Find transport pencil button in transports table 1s 793ms

And Click pencil and move transport to next day in schedule 20s 638ms

Then Check if transport is in new location in schedule 2s 274ms

And Check if dates in transport form are correct 3s 979ms

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 711ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 937ms

And Show all transport "false" 085ms

When Find transport pencil button in transports table 1s 802ms

And Click pencil and move transport to next day in schedule 20s 700ms

Then Check if transport is in new location in schedule 2s 262ms

And Check if dates in transport form are correct 3s 947ms

Hooks

After Hooks.deleteTransportAfterTest() 757ms

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 736ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 2s 908ms

And Show all transport "true" 286ms

When Find transport pencil button in transports table 1s 708ms

And Click pencil and move transport to next day in schedule 20s 499ms

Then Check if transport is in new location in schedule 2s 284ms

And Check if dates in transport form are correct 3s 968ms

Hooks

After Hooks.deleteTransportAfterTest() 750ms

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 899ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 022ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 023ms

When Show all transport types 1s 152ms

And Click button advice in transport table "DELIVERY" 247ms

And Set advice window in schedule 3s 365ms

And Fill advice form 13s 099ms

And Click advice save button and wait for advice form to disappear 33s 287ms

And Go to "TRANSPORT_TABLE" 511ms

And Find transport pencil button in transports table 1s 741ms

And Click pencil and move transport to next day in schedule 22s 340ms

Then Check if transport is in new location in schedule 2s 241ms

And Check if dates in transport form are correct 4s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 848ms

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 150ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 112ms

And Show all transport "false" 075ms

When Find transport pencil button in transports table 1s 741ms

And Click pencil and move transport to next day in schedule 21s 224ms

And Move advice window "3" 1s 499ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 975ms

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 603ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 713ms

And Show all transport "false" 077ms

When Find transport pencil button in transports table 1s 779ms

And Click pencil and move transport to next day in schedule 20s 419ms

And Move advice window "3" 1s 617ms

Then Check if advice window is in new location 056ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 304ms

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 590ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 860ms

And Show all transport "false" 077ms

When Find transport pencil button in transports table 1s 778ms

And Click pencil and move transport to next day in schedule 21s 500ms

And Move advice window "3" 1s 677ms

Then Check if advice window is in new location 069ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 750ms

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 556ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 858ms

And Show all transport "false" 073ms

When Find transport pencil button in transports table 1s 827ms

And Click pencil and move transport to next day in schedule 20s 620ms

And Move advice window "3" 1s 500ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 748ms

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 629ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 914ms

And Show all transport "false" 078ms

When Find transport pencil button in transports table 1s 818ms

And Click pencil and move transport to next day in schedule 20s 574ms

And Move advice window "3" 1s 479ms

Then Check if advice window is in new location 063ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 653ms

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 533ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 717ms

And Show all transport "true" 251ms

When Find transport pencil button in transports table 1s 786ms

And Click pencil and move transport to next day in schedule 20s 352ms

And Move advice window "3" 1s 581ms

Then Check if advice window is in new location 063ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 152ms

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 023ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 150ms

And Go to transport details "DELIVERY" 2s 952ms

When Open section: "discrepancy-report-panel" 1s 275ms

Then Verify that no discrepancies found label is visible in discrepancy report section 173ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 730ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 231ms

Hooks

After Hooks.deleteTransportAfterTest() 895ms

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 069ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 101ms

And Go to transport details "DELIVERY" 2s 956ms

And Fill transport form 43s 223ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 263ms

When Go to transport details "DELIVERY" 3s 001ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 696ms

And Click "save-transport" save button 909ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 085ms

And Verify that discrepancy report section "not contains" validation errors 069ms

Hooks

After Hooks.deleteTransportAfterTest() 822ms

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 213ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 183ms

When Go to transport details "DELIVERY" 2s 940ms

Then Verify that discrepancy report section is available 083ms

And Open section: "discrepancy-report-panel" 1s 240ms

And Verify that generate new discrepancy report button is visible 116ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

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 782ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 937ms

When Go to transport details "OWN_COLLECTION" 2s 989ms

Then Verify that discrepancy report section is available 083ms

And Open section: "discrepancy-report-panel" 1s 219ms

And Verify that generate new discrepancy report button is visible 083ms

Hooks

After Hooks.deleteTransportAfterTest() 863ms

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 894ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 798ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 997ms

Then Verify that discrepancy report section is available 072ms

And Open section: "discrepancy-report-panel" 1s 158ms

And Verify that generate new discrepancy report button is visible 074ms

Hooks

After Hooks.deleteTransportAfterTest() 869ms

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 864ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 114ms

When Go to transport details "EXPORT" 3s 070ms

Then Verify that discrepancy report section is available 068ms

And Open section: "discrepancy-report-panel" 1s 143ms

And Verify that generate new discrepancy report button is visible 155ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 106ms

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 280ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 944ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 3s 038ms

Then Verify that discrepancy report section is available 158ms

And Open section: "discrepancy-report-panel" 1s 313ms

And Verify that generate new discrepancy report button is visible 068ms

Hooks

After Hooks.deleteTransportAfterTest() 450ms

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 924ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 650ms

When Go to transport details "CISTERN_DELIVERY" 2s 906ms

Then Verify that discrepancy report section is not available 15s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 738ms

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 232ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 638ms

When Go to transport details "CISTERN_COLLECTION" 2s 915ms

Then Verify that discrepancy report section is not available 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 863ms

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 025ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 213ms

When Go to transport details "WEIGHING" 2s 844ms

Then Verify that discrepancy report section is not available 15s 082ms

Hooks

After Hooks.deleteTransportAfterTest() 605ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if 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 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 068ms

When Go to "TRANSPORT_TABLE" 419ms

And Go to transport details "DELIVERY" 2s 955ms

And Change filled value in details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 860ms

And Change filled value in details "unloaded-stere" "text" "3" "0" 1s 488ms

And Open section: "discrepancy-report-panel" 1s 147ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 019ms

And Fill transport form 43s 081ms

And Fill discrepancy report section without closing the form 22s 368ms

And Generate discrepancy report 19s 901ms

And Download discrepancy report 364ms

Then Verify that discrepancy report file has correct values 16s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 940ms

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 064ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 092ms

When Go to "TRANSPORT_TABLE" 437ms

And Go to transport details "DELIVERY" 2s 997ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 019ms

And Fill transport form 43s 100ms

And Open section: "discrepancy-report-panel" 1s 178ms

And Fill discrepancy report section without closing the form 22s 325ms

And Generate discrepancy report 19s 358ms

And Download discrepancy report 344ms

And Verify that discrepancy report file has correct values 15s 652ms

And Fill edited discrepancy report section 18s 802ms

And Generate edited discrepancy report 4s 048ms

And Download discrepancy report 327ms

Then Verify that discrepancy report file has correct values 15s 598ms

Hooks

After Hooks.deleteTransportAfterTest() 882ms

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 208ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 147ms

When Go to "TRANSPORT_TABLE" 425ms

And Confirm statuses until reach "during-unload" 11s 609ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 744ms

And Change filled value in details "insp.-accord.-with-ins." "select" "NIE" "0" 3s 806ms

And Check if next status is not possible to confirm in status confirmation modal 244ms

Hooks

After Hooks.deleteTransportAfterTest() 961ms

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) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 232ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 327ms

And Get "LOAD" settings from "piast" 152ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 308ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 928ms

And Login as "piast-admin" 5s 532ms

And Go to "TRANSPORT_TABLE" 542ms

When Go to transport details "LOAD" 3s 014ms

And Add step "unload" 402ms

And Change filled value in details "company-step-2" "autocomplete" "DPA2" "0" 7s 182ms

And Change filled value in details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 996ms

Then Click "save-transport-and-close" save button and wait for form to disappear 30s 201ms

And Go to transport details "LOAD" 3s 026ms

And Verify that transport has "3" steps 046ms

Hooks

After Hooks.deleteTransportAfterTest() 532ms

After Hooks.rollbackTransportTypeSettings() 217ms

After Hooks.rollbackAddedActionAuthorities() 277ms

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 394ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 373ms

When Go to "TRANSPORT_TABLE" 420ms

And Go to transport details "SMALLS_IMPORT" 17s 363ms

Then Verify that user can't edit time range for load and unload 15s 076ms

Hooks

After Hooks.deleteTransportAfterTest() 587ms

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-neuca" 217ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 3s 282ms

And Login as "neuca-admin" 2s 147ms

And Go to "TRANSPORT_TABLE" 498ms

And Show all transport types 1s 308ms

When Go to transport details "DELIVERY" 2s 944ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 178ms

Hooks

After Hooks.deleteTransportAfterTest() 895ms

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" 216ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 092ms

And Login as "hochland-admin" 3s 951ms

And Go to "TRANSPORT_TABLE" 390ms

And Show all transport types 1s 177ms

When Go to transport details "EXPORT" 3s 089ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 130ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 051ms

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" 300ms

And Get "DELIVERY" settings from "neuca" 239ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 379ms

And Login as "neuca-admin" 2s 406ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 17s 036ms

When Go to "TRANSPORT_TABLE" 602ms

And Go to transport details "DELIVERY" 3s 010ms

And Set number of pallets in "load" step in transport - "32" 300ms

And Check if number of pallets check message is not visible in transport form 15s 079ms

And Set number of pallets in "load" step in transport - "34" 256ms

Then Check if number of pallets check message is visible in transport form 091ms

Hooks

After Hooks.deleteTransportAfterTest() 835ms

After Hooks.rollbackTransportTypeSettings() 329ms

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" 242ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 341ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 282ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 287ms

And Login as "farmacol-admin" 6s 668ms

And Go to new transport "EXTERNAL_DELIVERY" 677ms

And Add step "unload" 206ms

And Click "save-transport-and-close" save button 869ms

Then Verify that "time-range-from-date-2" has validation error 1s 073ms

Then Verify that "time-range-to-date-2" has validation error 1s 082ms

And Change filled value in details "time-range-from-date-2" "date" "" "0" 3s 762ms

And Click "save-transport-and-close" save button 900ms

And Verify that "time-range-from-date-2" has no validation error 067ms

And Verify that "time-range-to-date-2" has no validation error 070ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.rollbackTransportTypeSettings() 320ms

After Hooks.rollbackAddedActionAuthorities() 269ms

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" 232ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 320ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 943ms

When Login as "piast-admin" 5s 590ms

And Go to transport details "LOAD" 3s 151ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 019ms

And Add step "unload" 354ms

And Fill step data 16s 254ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 020ms

And Add step "load" 214ms

And Fill step data 5s 837ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 306ms

Then Go to transport details "LOAD" 3s 166ms

And Check if "unload" step is added as "3" step in transport form 076ms

And Check if "load" step is added as "4" step in transport form 065ms

Hooks

After Hooks.deleteTransportAfterTest() 559ms

After Hooks.rollbackAddedActionAuthorities() 284ms

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" 222ms

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" 059ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 082ms

When Login as "super-admin-skz" 7s 707ms

And Go to transport details "SMALLS_EXPORT" 2s 924ms

And Check if step is draggable "LOAD" 112ms

And Check if step is not draggable "UNLOAD" 139ms

Hooks

After Hooks.deleteTransportAfterTest() 620ms

After Hooks.rollbackAddedActionAuthorities() 276ms

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" 001ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 546ms

When Go to new transport "SMALLS_IMPORT" 731ms

And Fill transport form 21s 535ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 276ms

And Show all transport "false" 072ms

And Go to transport details "SMALLS_IMPORT" 3s 035ms

And Click create similar button 15s 255ms

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 274ms

And Open similar transport details 551ms

Then Check are transport values equals 2s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 562ms

After Hooks.deleteSimilarTransportAfterTest() 577ms

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" 001ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 8s 106ms

When Go to new transport "DELIVERY" 15s 598ms

And Fill transport form 42s 876ms

And Click "save-transport" save button and wait for form to disappear 30s 214ms

And Set advice window in schedule 2s 398ms

And Check is transport created in schedule and set transport id 3s 378ms

And Go to "TRANSPORT_TABLE" 521ms

And Go to transport details "DELIVERY" 30s 747ms

And Click create similar button 15s 254ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 14s 111ms

And Click "save-transport" save button and wait for form to disappear 30s 210ms

And Set advice window in schedule in "2" days 4s 492ms

And Go to "TRANSPORT_TABLE" 473ms

And Open similar transport details 2s 811ms

Then Check are transport values equals 26s 415ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

After Hooks.deleteSimilarTransportAfterTest() 844ms

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" 001ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 2s 505ms

When Go to new transport "DELIVERY" 15s 683ms

And Fill transport form 42s 907ms

And Click "save-transport" save button and wait for form to disappear 30s 252ms

And Set advice window in schedule 2s 439ms

And Check is transport created in schedule and set transport id 3s 375ms

And Go to "TRANSPORT_TABLE" 533ms

And Go to transport details "DELIVERY" 30s 717ms

And Click create similar button 15s 254ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 13s 984ms

And Click "save-transport" save button and wait for form to disappear 30s 256ms

And Set advice window in schedule in "2" days 4s 567ms

And Go to "TRANSPORT_TABLE" 471ms

And Open similar transport details 2s 804ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 082ms

Hooks

After Hooks.deleteTransportAfterTest() 823ms

After Hooks.deleteSimilarTransportAfterTest() 946ms

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 Get inputs from database "CREATE_SMALLS_IMPORT_FOR_PRINT" "super-admin-skz" 018ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 793ms

When Go to new transport "SMALLS_IMPORT" 764ms

And Fill transport form 36s 397ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 240ms

And Go to transport details "SMALLS_IMPORT" 2s 904ms

And Go to transport print details form 3s 622ms

Then Check are transport values equals 8s 966ms

Hooks

After Hooks.deleteTransportAfterTest() 623ms

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 987ms

And Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 020ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 162ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 907ms

And Go to transport details "SMALLS_IMPORT" 2s 910ms

Then Verify that the transport can be edited 2s 031ms

And Close transport details 15s 199ms

And If user is login then logout 292ms

And Login as "pskza1-carrier@qa.qa-test" 2s 839ms

And Go to transport details "SMALLS_IMPORT" 3s 858ms

And Verify that the transport cannot be edited 46s 992ms

Hooks

After Hooks.deleteTransportAfterTest() 601ms

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 888ms

And Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 021ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 143ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 815ms

And Go to transport details "SMALLS_EXPORT" 2s 847ms

Then Verify that the transport can be edited 1s 931ms

And Close transport details 15s 253ms

And If user is login then logout 766ms

And Login as "pskza1-carrier@qa.qa-test" 2s 469ms

And Go to transport details "SMALLS_EXPORT" 3s 942ms

And Verify that the transport cannot be edited 47s 028ms

Hooks

After Hooks.deleteTransportAfterTest() 710ms

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 828ms

And Get inputs from database "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 018ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 421ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 931ms

And Go to transport details "SMALLS_IMPORT" 2s 963ms

Then Verify that the hidden data in transport are not visible 1s 123ms

And Close transport details 15s 250ms

And If user is login then logout 314ms

And Login as "swisskrono-admin" 2s 947ms

And Go to transport details "SMALLS_IMPORT" 3s 021ms

And Verify that the hidden data in transport are visible 1s 609ms

Hooks

After Hooks.deleteTransportAfterTest() 655ms

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 697ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 019ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 514ms

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 824ms

Then Verify that the hidden data in transport are not visible 1s 107ms

And Close transport details 15s 235ms

And If user is login then logout 304ms

And Login as "swisskrono-admin" 2s 829ms

And Go to transport details "SMALLS_EXPORT" 3s 115ms

And Verify that the hidden data in transport are visible 1s 700ms

Hooks

After Hooks.deleteTransportAfterTest() 635ms

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" 5s 332ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 175ms

When Go to transport details "DELIVERY" 3s 003ms

And Change filled value in details "unloaded-stere" "text" "3" "0" 1s 565ms

And Change filled value in details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 839ms

And Change filled value in details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 837ms

And Fill discrepancy report section without closing the form 22s 252ms

And Click "save-transport" save button 2s 692ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 323ms

And Check if transport details form is disappeared 15s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

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" 228ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 310ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 1s 123ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 3s 218ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 10s 352ms

When Go to "TRANSPORT_TABLE" 508ms

And Go to transport details "DELIVERY" 2s 962ms

And Change filled value in details "transport-description" "text" "opis" "0" 1s 576ms

Then Verify that "transport-description" in transport has value "opis" 072ms

Hooks

After Hooks.deleteTransportAfterTest() 921ms

After Hooks.rollbackAddedActionAuthorities() 248ms

After Hooks.rollbackWarehousesAccess() 810ms

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" 216ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 2s 945ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 341ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 696ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 8s 718ms

When Go to "TRANSPORT_TABLE" 463ms

And Go to transport details "DELIVERY" 2s 895ms

Then Verify that "transport-description" in transport form is disabled 066ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 242ms

After Hooks.rollbackRemovedActionAuthorities() 279ms

After Hooks.rollbackWarehousesAccess() 857ms

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" 215ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 330ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 144ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 075ms

And Show all transport "false" 078ms

When Go to "TRANSPORT_TABLE" 475ms

And Go to transport details "DELIVERY" 2s 934ms

Then Verify that "CARRIER" in transport form is visible 091ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 051ms

After Hooks.rollbackAddedActionAuthorities() 270ms

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" 231ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 350ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 127ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 476ms

And Show all transport "false" 096ms

When Go to "TRANSPORT_TABLE" 470ms

And Go to transport details "TRANSPORT" 3s 035ms

Then Verify that "CARRIER" in transport form is visible 074ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

After Hooks.rollbackAddedActionAuthorities() 251ms

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" 231ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 327ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 292ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 768ms

And Show all transport "true" 264ms

When Go to "TRANSPORT_TABLE" 395ms

And Go to transport details "TRANSPORT_ORDER" 2s 946ms

Then Verify that "CARRIER" in transport form is visible 108ms

Hooks

After Hooks.deleteTransportAfterTest() 588ms

After Hooks.rollbackAddedActionAuthorities() 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-hochland" 236ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 337ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 066ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 049ms

And Show all transport "false" 074ms

When Go to "TRANSPORT_TABLE" 592ms

And Go to transport details "DELIVERY" 3s

Then Verify that "CARRIER" in transport form is not visible 15s 084ms

Hooks

After Hooks.deleteTransportAfterTest() 820ms

After Hooks.rollbackRemovedActionAuthorities() 283ms

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" 229ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 341ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 087ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 781ms

And Show all transport "false" 080ms

When Go to "TRANSPORT_TABLE" 436ms

And Go to transport details "TRANSPORT" 2s 986ms

Then Verify that "CARRIER" in transport form is not visible 15s 075ms

Hooks

After Hooks.deleteTransportAfterTest() 581ms

After Hooks.rollbackRemovedActionAuthorities() 291ms

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" 255ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 332ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 203ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 699ms

And Show all transport "true" 253ms

When Go to "TRANSPORT_TABLE" 366ms

And Go to transport details "TRANSPORT_ORDER" 2s 842ms

Then Verify that "CARRIER" in transport form is not visible 15s 085ms

Hooks

After Hooks.deleteTransportAfterTest() 531ms

After Hooks.rollbackRemovedActionAuthorities() 288ms

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" 256ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 330ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 324ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 133ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 189ms

And Show all transport "false" 082ms

When Go to "TRANSPORT_TABLE" 531ms

And Go to transport details "DELIVERY" 3s 047ms

Then Verify that "CARRIER" in transport form is not disabled 071ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 097ms

After Hooks.rollbackAddedActionAuthorities() 531ms

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" 230ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 329ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 325ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 061ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 931ms

And Show all transport "false" 080ms

When Go to "TRANSPORT_TABLE" 378ms

And Go to transport details "TRANSPORT" 2s 978ms

Then Verify that "CARRIER" in transport form is not disabled 104ms

Hooks

After Hooks.deleteTransportAfterTest() 714ms

After Hooks.rollbackAddedActionAuthorities() 594ms

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" 242ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 318ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 316ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 192ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 422ms

And Show all transport "true" 255ms

When Go to "TRANSPORT_TABLE" 411ms

And Go to transport details "TRANSPORT_ORDER" 2s 910ms

Then Verify that "CARRIER" in transport form is not disabled 100ms

Hooks

After Hooks.deleteTransportAfterTest() 595ms

After Hooks.rollbackAddedActionAuthorities() 552ms

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" 224ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 314ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 328ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 114ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 060ms

And Show all transport "false" 083ms

When Go to "TRANSPORT_TABLE" 516ms

And Go to transport details "DELIVERY" 2s 986ms

Then Verify that "CARRIER" in transport form is disabled 089ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 298ms

After Hooks.rollbackAddedActionAuthorities() 276ms

After Hooks.rollbackRemovedActionAuthorities() 271ms

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" 222ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 323ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 056ms

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 780ms

And Show all transport "false" 083ms

When Go to "TRANSPORT_TABLE" 446ms

And Go to transport details "TRANSPORT" 2s 925ms

Then Verify that "CARRIER" in transport form is disabled 078ms

Hooks

After Hooks.deleteTransportAfterTest() 597ms

After Hooks.rollbackAddedActionAuthorities() 258ms

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" 228ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 318ms

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 132ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 451ms

And Show all transport "true" 257ms

When Go to "TRANSPORT_TABLE" 409ms

And Go to transport details "TRANSPORT_ORDER" 3s 005ms

Then Verify that "CARRIER" in transport form is disabled 104ms

Hooks

After Hooks.deleteTransportAfterTest() 593ms

After Hooks.rollbackAddedActionAuthorities() 258ms

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) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 223ms

And Get custom field settings for "DELIVERY" transport type and "" company 098ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 703ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 329ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 327ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 299ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 592ms

When Find transport in table with status "planned" 3s 803ms

And Confirm statuses until reach "process-ended" 11s 547ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 573ms

And Show "DELIVERY" 175ms

And Go to transport details "DELIVERY" 30s 793ms

And Change filled value in details "transport-description" "text" "opis" "0" 1s 575ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 245ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 30s 672ms

Then Verify that "transport-description" in transport has value "opis" 063ms

Hooks

After Hooks.deleteTransportAfterTest() 637ms

After Hooks.rollbackAllCustomFieldsSettings() 003ms

After Hooks.rollbackAddedActionAuthorities() 271ms

After Hooks.rollbackRemovedActionAuthorities() 540ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 614ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 116ms

When Go to transport details "DELIVERY" 2s 911ms

And Fill transport form 43s 198ms

And Change filled value in details "driver-name" "text" "XXX ZZZ" "0" 1s 710ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 179ms

And Go to new transport "DELIVERY" 715ms

Then Verify that driver "XXX ZZZ" is in list 957ms

Hooks

After Hooks.deleteTransportAfterTest() 806ms

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 919ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 179ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 923ms

And If user is login then logout 725ms

And Login as "pskza1-carrier@qa.qa-test" 2s 522ms

Then Verify that the transport has been transferred 3s 538ms

And Accept or reject "accept" transferred transport 16s 581ms

And Go to transport details "SMALLS_IMPORT" 2s 806ms

And Verify that "transaction-price" in transport form is visible 080ms

And Verify that transaction price field has correct value 093ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 166ms

Hooks

After Hooks.deleteTransportAfterTest() 582ms

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 832ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 129ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 784ms

And If user is login then logout 345ms

And Login as "pskza1-carrier@qa.qa-test" 2s 848ms

Then Verify that the transport has been transferred 3s 752ms

And Accept or reject "accept" transferred transport 16s 556ms

And Go to transport details "SMALLS_EXPORT" 2s 889ms

And Verify that "transaction-price" in transport form is visible 090ms

And Verify that transaction price field has correct value 082ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 203ms

Hooks

After Hooks.deleteTransportAfterTest() 595ms

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" 228ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 107ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 074ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 4s 493ms

And Click button advice in transport table "OWN_COLLECTION" 891ms

And Set advice window in schedule 3s 238ms

And Fill advice form 11s 582ms

And Click advice save button and wait for advice form to disappear 33s 323ms

And Go to "TRANSPORT_TABLE" 485ms

And Find transport in table with status "planned" 3s 715ms

And Confirm statuses until reach "on-the-area" 6s 302ms

And Go to transport details "OWN_COLLECTION" 2s 912ms

And Click create similar button 15s 277ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 991ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 231ms

And Open similar transport details 501ms

Then Check if transport form modal is visible 097ms

Hooks

After Hooks.deleteTransportAfterTest() 783ms

After Hooks.deleteSimilarTransportAfterTest() 543ms

After Hooks.rollbackAllCustomFieldsSettings() 531ms

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" 221ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 116ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 042ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 4s 726ms

And Click button advice in transport table "OWN_COLLECTION" 932ms

And Set advice window in schedule 3s 287ms

And Fill advice form 11s 505ms

And Click advice save button and wait for advice form to disappear 33s 321ms

And Go to "TRANSPORT_TABLE" 496ms

And Find transport in table with status "planned" 3s 691ms

And Confirm statuses until reach "during-load" 11s 471ms

And Go to transport details "OWN_COLLECTION" 2s 916ms

And Click create similar button 15s 273ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 979ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 206ms

And Open similar transport details 514ms

Then Check if transport form modal is visible 095ms

Hooks

After Hooks.deleteTransportAfterTest() 778ms

After Hooks.deleteSimilarTransportAfterTest() 500ms

After Hooks.rollbackAllCustomFieldsSettings() 469ms

View Feature Transport form

@deleteTransportAfterTest @deleteCustomFieldAfterTest @FLAKY-A-7982

Scenario Outline Check if date and time custom field appeared in transport details after creating transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-lisner" 217ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lisner" 001ms

And Create custom field with "CREATE_DELIVERY_DATE_AND_TIME_CFD" by "super-admin-lisner" 3s 036ms

When Login as "lisner-admin-2" and set token of apiUsername "super-admin-lisner" 7s 015ms

And Go to new transport "DELIVERY" 714ms

And Fill transport form 33s 675ms

And Click "save-transport" save button and wait for form to disappear 30s 222ms

And Set advice window in schedule 2s 378ms

And Go to "TRANSPORT_TABLE" 443ms

And Show all transport types 1s 171ms

And Go to transport details "DELIVERY" 2s 758ms

Then Verify that "date-and-time" in transport form is visible 081ms

Hooks

After Hooks.deleteTransportAfterTest() 873ms

After Hooks.deleteCustomFieldAfterTest() 2s 600ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 8s 605ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 142ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 658ms

When Click invoice button 3s 263ms

And Set default invoice currency value 162ms

Then Check that default currency value in invoice form is "EUR" 139ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_IMPORT" and principal alias "swisskrono" 305ms

And Clear all cache 2s 544ms

And Login as "swisskrono-admin" 10s 925ms

And Go to "TRANSPORT_TABLE" 378ms

And Show all transport types 1s 166ms

And Click invoice button 651ms

Then Check that default currency value in invoice form is "USD" 165ms

Hooks

After Hooks.deleteTransportAfterTest() 795ms

After Hooks.rollbackInvoiceCurrency() 2s 462ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 11s 042ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 192ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 651ms

When Click invoice button 3s 488ms

And Set default invoice currency value 173ms

Then Check that default currency value in invoice form is "EUR" 139ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_EXPORT" and principal alias "swisskrono" 194ms

And Clear all cache 2s 149ms

And Login as "swisskrono-admin" 10s 901ms

And Go to "TRANSPORT_TABLE" 434ms

And Show all transport types 1s 183ms

And Click invoice button 832ms

Then Check that default currency value in invoice form is "USD" 157ms

Hooks

After Hooks.deleteTransportAfterTest() 832ms

After Hooks.rollbackInvoiceCurrency() 2s 255ms

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" 6s 436ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 875ms

And Show all transport types 1s 139ms

Then Check if transport number is visible "DELIVERY" 15s 163ms

And Check if transport details is not visible 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 781ms

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 770ms

And Show all transport "false" 083ms

And Go to "TRANSPORT_TABLE" 418ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 139ms

When Click on transport row 158ms

Then Verify if transport row is selected 092ms

Hooks

After Hooks.deleteTransportAfterTest() 984ms

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 542ms

And Show all transport "false" 081ms

And Go to "TRANSPORT_TABLE" 380ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 740ms

When Click on transport row 154ms

Then Verify if transport row is selected 096ms

Hooks

After Hooks.deleteTransportAfterTest() 788ms

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 438ms

And Show all transport "false" 082ms

And Go to "TRANSPORT_TABLE" 498ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 617ms

When Click on transport row 164ms

Then Verify if transport row is selected 080ms

Hooks

After Hooks.deleteTransportAfterTest() 838ms

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 140ms

And Show all transport "false" 079ms

And Go to "TRANSPORT_TABLE" 441ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 789ms

When Click on transport row 153ms

Then Verify if transport row is selected 091ms

Hooks

After Hooks.deleteTransportAfterTest() 889ms

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 707ms

And Show all transport "false" 081ms

And Go to "TRANSPORT_TABLE" 372ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 820ms

When Click on transport row 166ms

Then Verify if transport row is selected 086ms

Hooks

After Hooks.deleteTransportAfterTest() 870ms

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" 6s 164ms

And Show all transport "true" 278ms

And Go to "TRANSPORT_TABLE" 398ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 713ms

When Click on transport row 151ms

Then Verify if transport row is selected 062ms

Hooks

After Hooks.deleteTransportAfterTest() 805ms

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 Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 6s 081ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 516ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 649ms

When Accept or reject "accept" transferred transport 11s 692ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm margin-bottom accept-transaction-button'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.Wp7ONc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e145d6961212f956fc0dcb269d0fc6f2
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at CucumberTests.Transport.CarrierTransportAction.acceptOrRejectTransferredTransport(CarrierTransportAction.java:55)
	at ✽.Accept or reject "accept" transferred transport(file:Features/Atom/Transport/TransportTransfer/RejectTransport.feature:18)

Then Verify that transport is accept or reject "accept" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 569ms

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 Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 752ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 646ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 638ms

When Accept or reject "reject" transferred transport 17s 787ms

Then Verify that transport is accept or reject "reject" 15s 076ms

Hooks

After Hooks.deleteTransportAfterTest() 577ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 9s 414ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 482ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 658ms

When Accept or reject "accept" transferred transport 20s 173ms

Then Verify that transport is accept or reject "accept" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 578ms

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 Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 809ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 324ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 652ms

When Accept or reject "reject" transferred transport 19s 900ms

Then Verify that transport is accept or reject "reject" 15s 067ms

Hooks

After Hooks.deleteTransportAfterTest() 571ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 842ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 308ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 645ms

When Accept or reject "accept" transferred transport 17s 038ms

Then Verify that transport is accept or reject "accept" 068ms

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 Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 722ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 328ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 662ms

When Accept or reject "reject" transferred transport 16s 949ms

Then Verify that transport is accept or reject "reject" 15s 130ms

Hooks

After Hooks.deleteTransportAfterTest() 612ms

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 737ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 111ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 791ms

And If user is login then logout 320ms

And Login as "paa1-carrier@qa.qa-test" 3s 078ms

Then Verify that the transport has been transferred with "true" 1s 814ms

Hooks

After Hooks.deleteTransportAfterTest() 786ms

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) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 545ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 988ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 999ms

And If user is login then logout 304ms

And Login as "paa1-carrier@qa.qa-test" 2s 893ms

Then Verify that the transport has been transferred with "false" 1s 689ms

Hooks

After Hooks.deleteTransportAfterTest() 595ms

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 778ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 152ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 848ms

And If user is login then logout 304ms

And Login as "pskza1-carrier@qa.qa-test" 2s 946ms

Then Verify that the transport has been transferred 3s 455ms

Hooks

After Hooks.deleteTransportAfterTest() 795ms

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 684ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 122ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 779ms

And If user is login then logout 259ms

And Login as "pskza1-carrier@qa.qa-test" 2s 963ms

Then Verify that the transport has been transferred 3s 585ms

Hooks

After Hooks.deleteTransportAfterTest() 791ms

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 623ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 501ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 910ms

And Go to auction offer 1s 682ms

When Offer "1000" 437ms

And Verify that offer with "1000" has been added to auction 3s 075ms

And If user is login then logout 592ms

And Login as "swisskrono-admin" 2s 265ms

Then Go to auction details 2s 179ms

And Pass transport to carrier from auction details 1s 535ms

And If user is login then logout 6s 327ms

And Login as "pskza1-carrier@qa.qa-test" 2s 525ms

And Verify that the transport has been transferred 3s 202ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

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 591ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 597ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 918ms

And Go to auction offer 1s 912ms

When Offer "1000" 443ms

And Verify that offer with "1000" has been added to auction 3s 072ms

And Wait till auction end 1m 52s 014ms

And If user is login then logout 252ms

Then Login as "swisskrono-admin" 3s 173ms

And Go to auction details 2s 286ms

And Pass transport to carrier from auction details 1s 539ms

And If user is login then logout 6s 240ms

And Login as "pskza1-carrier@qa.qa-test" 2s 349ms

And Verify that the transport has been transferred 3s 481ms

Hooks

After Hooks.deleteTransportAfterTest() 843ms

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 828ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 081ms

And Go to "TRANSPORT_TABLE" 503ms

When Open transport transfer modal 1s 713ms

Then Verify that all enabled companies from "swisskrono" are shown in select 383ms

Hooks

After Hooks.deleteTransportAfterTest() 605ms

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" 256ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 837ms

And Login as "adama-admin" 2s 241ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 093ms

And Go to "TRANSPORT_TABLE" 384ms

When Open transport transfer modal 1s 649ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 261ms

Hooks

After Hooks.deleteTransportAfterTest() 616ms

After Hooks.rollbackRejectedSections() 467ms

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 566ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 076ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 35s 338ms

And If user is login then logout 275ms

When Login as "paa1-carrier@qa.qa-test" 5s 136ms

And Verify that the transport has been transferred with "true" 1s 910ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 049ms

Hooks

After Hooks.deleteTransportAfterTest() 605ms

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 518ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 110ms

When Go to "TRANSPORT_TABLE" 501ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 863ms

Then Check if new assortment group is disabled in transport form 074ms

Hooks

After Hooks.deleteTransportAfterTest() 897ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to advice transport after double cancellation.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 484ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 929ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 018ms

When Show all transport types 1s 146ms

And Click button advice in transport table "CONTAINER" 343ms

And Set advice window in schedule 3s 205ms

And Click button cancel in advice form 16s 176ms

And Set advice window in schedule 2s 362ms

And Click button cancel in advice form 16s 087ms

And Set advice window in schedule 2s 344ms

And Fill advice form 21s 932ms

And Click advice save button and wait for advice form to disappear 33s 299ms

And Go to "TRANSPORT_TABLE" 480ms

And Go to transport details "CONTAINER" 2s 896ms

Then Check are advice values equals 5s 083ms

Hooks

After Hooks.deleteTransportAfterTest() 706ms

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) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 730ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 027ms

When Go to new transport "TRANSPORT" 758ms

And Fill transport form 29s 063ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 217ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 748ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 401ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 748ms

And Accept or reject "reject" transferred transport 17s 662ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 522ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 775ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 739ms

And Accept or reject "accept" transferred transport 17s 898ms

Then Verify that transport is accept or reject "accept" 072ms

Hooks

After Hooks.deleteTransportAfterTest() 598ms

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 670ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 019ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 013ms

When Show all transport types 1s 152ms

And Click button advice in transport table "DELIVERY" 299ms

And Set advice window in schedule 3s 392ms

And Click button cancel in advice form 16s 108ms

And Go to "TRANSPORT_TABLE" 491ms

When Go to transport details "DELIVERY" 2s 921ms

And Fill transport form 1m 8s 702ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 258ms

And Go to transport details "DELIVERY" 2s 844ms

Then Check are transport values equals 26s 351ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	4244	9	12	0	0	4265	423	9	432	7h 26m 55s 977ms	Failed

Tag Report