Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.375	10 kwi 2021, 05:29

	Steps	Scenarios	Features
@deleteTransportAfterTest	3469	15	21	0	0	3505	371	15	386	5h 19m 41s 155ms	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.

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 3s 433ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 1s 494ms

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

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

And Set advice window in schedule in the past 2s 879ms

And Fill advice form 16s 432ms

And Click advice save button to check error message 071ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 362ms

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.

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 427ms

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

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

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

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

And Set advice window in schedule in the past 2s 618ms

And Fill advice form 8s 377ms

And Click advice save button to check error message 102ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

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.

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 250ms

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

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

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

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

And Set advice window in schedule in the past 2s 578ms

And Fill advice form 8s 365ms

And Click advice save button to check error message 078ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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.

Steps

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

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

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

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

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

And Set advice window in schedule in the past 2s 402ms

And Fill advice form 13s 150ms

And Click advice save button to check error message 078ms

Then Check if possible advice alert is displayed 023ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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.

Steps

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

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

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

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

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

And Set advice window in schedule in the past 2s 444ms

And Fill advice form 13s 068ms

And Click advice save button to check error message 075ms

Then Check if possible advice alert is displayed 018ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 043ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 49s 463ms

And Go to "TRANSPORT_TABLE" 197ms

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

When Go to transport details "CONTAINER" 4s 439ms

And Fill transport form 4s 681ms

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

And Expand advice panel 098ms

And Edit advice in transport details 12s 402ms

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

And Go to transport details "CONTAINER" 4s 360ms

And Expand advice panel 097ms

Then Check are advice values equals after edition 216ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 216ms

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

And Show all transport types 1s 046ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 41s 680ms

And Go to "TRANSPORT_TABLE" 244ms

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

When Go to transport details "DELIVERY" 4s 431ms

And Fill transport form 1m 2s 089ms

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

And Expand advice panel 095ms

And Edit advice in transport details 6s 596ms

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

And Go to transport details "DELIVERY" 4s 515ms

And Expand advice panel 100ms

Then Check are advice values equals after edition 095ms

Hooks

After Hooks.deleteTransportAfterTest() 188ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 137ms

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

And Show all transport types 1s 046ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-piast" 41s 679ms

And Go to "TRANSPORT_TABLE" 176ms

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

When Go to transport details "LOAD" 4s 663ms

And Fill transport form 56s 935ms

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

And Expand advice panel 117ms

And Edit advice in transport details 6s 565ms

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

And Go to transport details "LOAD" 4s 511ms

And Expand advice panel 097ms

Then Check are advice values equals after edition 085ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 041ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 395ms

And Go to "TRANSPORT_TABLE" 169ms

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

When Go to transport details "LOAD" 4s 383ms

And Fill transport form 24s 600ms

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

And Expand advice panel 110ms

And Edit advice in transport details 18s 502ms

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

And Go to transport details "LOAD" 4s 391ms

And Expand advice panel 116ms

Then Check are advice values equals after edition 6s 303ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 040ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-keeeper" 46s 753ms

And Go to "TRANSPORT_TABLE" 157ms

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

When Go to transport details "CONTAINER" 4s 348ms

And Fill transport form 24s 626ms

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

And Expand advice panel 088ms

And Edit advice in transport details 18s 477ms

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

And Go to transport details "CONTAINER" 4s 361ms

And Expand advice panel 098ms

Then Check are advice values equals after edition 6s 283ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 366ms

And Fill advice form 12s 267ms

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

And Go to "TRANSPORT_TABLE" 160ms

And Go to transport details "CONTAINER" 4s 363ms

Then Check are advice values equals 330ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 6s 419ms

And Fill advice form 11s 828ms

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

And Go to "TRANSPORT_TABLE" 189ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 527ms

Then Check are advice values equals 2s 306ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 169ms

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

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

When Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 573ms

And Fill advice form 8s 288ms

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

And Go to "TRANSPORT_TABLE" 208ms

And Go to transport details "DELIVERY" 4s 516ms

Then Check are advice values equals 176ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 131ms

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

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

When Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 502ms

And Fill advice form 8s 234ms

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

And Go to "TRANSPORT_TABLE" 169ms

And Go to transport details "LOAD" 4s 607ms

Then Check are advice values equals 200ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 403ms

And Fill advice form 13s 098ms

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

And Go to "TRANSPORT_TABLE" 159ms

And Go to transport details "LOAD" 4s 352ms

Then Check are advice values equals 2s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 379ms

And Fill advice form 13s 031ms

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

And Go to "TRANSPORT_TABLE" 159ms

And Go to transport details "CONTAINER" 4s 376ms

Then Check are advice values equals 2s 319ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

Steps

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

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

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

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

And Accept transferred transport by Api 327ms

And Set token of apiUsername "super-admin-adama" 096ms

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 374ms

And Fill advice form 11s 746ms

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

And Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "TRANSPORT" 4s 404ms

Then Check are advice values equals 2s 264ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

Steps

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

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

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

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

And Accept transferred transport by Api 279ms

And Set token of apiUsername "super-admin-skz" 094ms

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

When Show all transport types 1s 033ms

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

And Set advice window in schedule 2s 664ms

And Fill advice form 14s 400ms

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

And Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "SMALLS_IMPORT" 4s 458ms

Then Check are advice values equals 2s 301ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

Steps

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

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

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

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

And Accept transferred transport by Api 106ms

And Set token of apiUsername "super-admin-skz" 093ms

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 622ms

And Fill advice form 14s 451ms

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

And Go to "TRANSPORT_TABLE" 171ms

And Go to transport details "SMALLS_EXPORT" 4s 472ms

Then Check are advice values equals 2s 290ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 091ms

And Set token of apiUsername "super-admin-adama" 096ms

When Show all transport types 1s 042ms

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

And Set week view 1s 487ms

And Show yesterday 1s 067ms

Then Check if advice restriction blockade windows are visible 023ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 111ms

And Set token of apiUsername "super-admin-skz" 101ms

When Show all transport types 1s 043ms

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

And Set week view 2s 033ms

And Show yesterday 1s 127ms

Then Check if advice restriction blockade windows are visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 110ms

And Set token of apiUsername "super-admin-skz" 122ms

When Show all transport types 1s 036ms

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

And Set week view 2s 043ms

And Show yesterday 1s 110ms

Then Check if advice restriction blockade windows are visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 461ms

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

And Show all transport "false" 025ms

And Click on time window date 1s 281ms

And Select view "DAYS_4" 2s 060ms

And Move advice window "3" 1s 310ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 953ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 646ms

And Show all transport "false" 015ms

And Click on time window date 15s 723ms

And Select view "DAYS_4" 2s 074ms

And Move advice window "3" 1s 443ms

Then Check if advice window is in new location 116ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 309ms

And Show all transport "false" 011ms

And Click on time window date 15s 579ms

And Select view "DAYS_4" 2s 055ms

And Move advice window "3" 1s 370ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 050ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 298ms

And Show all transport "false" 018ms

And Click on time window date 1s 402ms

And Select view "DAYS_4" 2s 059ms

And Move advice window "3" 1s 334ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 308ms

And Show all transport "false" 016ms

And Click on time window date 1s 279ms

And Select view "DAYS_4" 2s 061ms

And Move advice window "3" 1s 282ms

Then Check if advice window is in new location 020ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 996ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 309ms

And Show all transport "true" 066ms

And Click on time window date 1s 334ms

And Select view "DAYS_4" 2s 054ms

And Move advice window "3" 1s 314ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 026ms

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

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

When Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 521ms

And Fill advice form 8s 359ms

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

And Go to "TRANSPORT_TABLE" 235ms

And Click on time window date 1s 400ms

And Select view "DAYS_4" 2s 046ms

And Move advice window "3" 1s 392ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 391ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 223ms

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

And Go to "TRANSPORT_TABLE" 120ms

And Show all transport types 1s 028ms

And Click on time window date 1s 291ms

And Scroll to time window "adviceWindow" 036ms

And Set time window height "80" "adviceWindow" 2s 380ms

Then Check height of the time window after expanding by "80" in "adviceWindow" 022ms

Error message

java.lang.AssertionError: Okno nie zmieniło swojego rozmiaru
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Schedule.ResizeTimeWindowTest.checkHeightOfTimeWindowAfterExpandingByIn(ResizeTimeWindowTest.java:35)
	at ✽.Check height of the time window after expanding by "80" in "adviceWindow"(file:Features/Atom/Advice/AdviceTransport.feature:187)

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 936ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 264ms

And Go to "TRANSPORT_TABLE" 105ms

And Show all transport types 1s 038ms

And Click on time window date 1s 376ms

And Scroll to time window "adviceWindow" 031ms

And Set time window height "120" "adviceWindow" 2s 390ms

Then Check height of the time window after expanding by "120" in "adviceWindow" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 979ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 317ms

And Go to "TRANSPORT_TABLE" 121ms

And Show all transport types 1s 032ms

And Click on time window date 1s 317ms

And Scroll to time window "adviceWindow" 028ms

And Set time window height "48" "adviceWindow" 2s 374ms

Then Check height of the time window after expanding by "48" in "adviceWindow" 024ms

Error message

java.lang.AssertionError: Okno nie zmieniło swojego rozmiaru
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Schedule.ResizeTimeWindowTest.checkHeightOfTimeWindowAfterExpandingByIn(ResizeTimeWindowTest.java:35)
	at ✽.Check height of the time window after expanding by "48" in "adviceWindow"(file:Features/Atom/Advice/AdviceTransport.feature:187)

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 900ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 356ms

And Go to "TRANSPORT_TABLE" 281ms

And Show all transport types 15s 041ms

And Click on time window date 15s 794ms

And Scroll to time window "adviceWindow" 036ms

And Set time window height "40" "adviceWindow" 2s 413ms

Then Check height of the time window after expanding by "40" in "adviceWindow" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 142ms

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 591ms

And Fill advice form 8s 247ms

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

And Go to "TRANSPORT_TABLE" 209ms

And Click on time window date 1s 408ms

And Set time window height "120" "adviceWindow" 2s 390ms

Then Check height of the time window after expanding by "120" in "adviceWindow" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 389ms

And Go to "WAREHOUSE_TAB" 821ms

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

When Go to new transport "DELIVERY" 354ms

And Fill transport form 39s 373ms

And Click "save-transport" save button and wait for form to disappear 15s 631ms

And Click previous page button in browser 021ms

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

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

Steps

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 397ms

And Go to "WAREHOUSE_TAB" 777ms

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

When Go to new transport "DELIVERY" 311ms

And Fill transport form 39s 437ms

And Click "save-transport" save button and wait for form to disappear 15s 597ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_TRANSPORT_WITHOUT_WAREHOUSES" by JSON file as "super-admin-adama" 1s 196ms

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

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

When Show all transport types 1s 050ms

And Click button advice in transport table "TRANSPORT" 1s 009ms

And Fill advice form 11s 524ms

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

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

And Open statuses popup 106ms

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

Hooks

After Hooks.deleteTransportAfterTest() 049ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 196ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 669ms

And Login as "farmacol-admin" 982ms

And Go to "WAREHOUSE_TAB" 630ms

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

And Set week view 2s 258ms

And Move cursor over time window element 377ms

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 34s 297ms

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

When Click "save-transport" save button and wait for form to disappear 15s 610ms

And Set advice window in schedule 2s 142ms

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

Then Go to "OWN_COMPANY_TAB" 222ms

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

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

And Login as "daa1-supplier-3" and set token of apiUsername "super-admin-alrec" 1s 787ms

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

And Fill transport form 16s 236ms

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

When Click "save-transport" save button and wait for form to disappear 15s 585ms

And Set advice window in schedule 2s 128ms

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

Then Go to "OWN_COMPANY_TAB" 240ms

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 3s 131ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 256ms

When Go to "TRANSPORT_TABLE" 111ms

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

And Show all transport types 1s 043ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 1s 118ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 256ms

When Go to "TRANSPORT_TABLE" 150ms

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

And Show all transport types 1s 045ms

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-admin" 1s 172ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 1s 277ms

When Go to "TRANSPORT_TABLE" 127ms

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

And Show all transport types 1s 047ms

Then Verify that created transport is "false" in transport table 1m 18s 210ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-admin" 1s 312ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 1s 263ms

When Go to "TRANSPORT_TABLE" 132ms

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

And Show all transport types 1s 050ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 1s 120ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 303ms

And Delete created transport by API 116ms

When Go to "ARCHIVE_TAB" 214ms

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

And Show "SMALLS_IMPORT" 087ms

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 1s 270ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 270ms

And Delete created transport by API 100ms

When Go to "ARCHIVE_TAB" 212ms

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

And Show "SMALLS_IMPORT" 079ms

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

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-admin" 1s 226ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 1s 241ms

And Delete created transport by API 083ms

When Go to "ARCHIVE_TAB" 238ms

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

And Show "SMALLS_IMPORT" 085ms

Then Verify that created transport is "false" in transport table 1m 32s 152ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-admin" 1s 275ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 1s 276ms

And Delete created transport by API 085ms

When Go to "ARCHIVE_TAB" 222ms

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

And Show "SMALLS_IMPORT" 081ms

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

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_TRANSPORT_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 1s 251ms

When Login as "alrec-admin" 1s 023ms

And Go to "TRANSPORT_TABLE" 126ms

And Show all transport "true" 071ms

And Select transportType "TRANSPORT_ORDER" 1s 131ms

Then Check if load and unload time filters work properly "LOAD_TIME_WINDOW" 36s 656ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

And Login as "neuca-admin" 2s 712ms

And Go to "TRANSPORT_TABLE" 234ms

Then Verify that created transport is "false" in transport table 1m 32s 162ms

And Toggle transport table days limit filter 091ms

And Verify that created transport is "true" in transport table 15s 083ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 112ms

And Go to auction form 1s 322ms

And Select contractors group "Kraj" 090ms

Then Verify that carrier "PSKZA1" is selected 029ms

Hooks

After Hooks.removeContractorsGroup() 071ms

After Hooks.deleteTransportAfterTest() 090ms

View Feature Grouping of carriers

@deleteTransportAfterTest

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 129ms

And Go to auction form 1s 202ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Grouping of carriers

@deleteTransportAfterTest

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 118ms

And Go to auction form 1s 207ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 012ms

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

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

When Go to transport details "TRANSPORT" 4s 436ms

And Expand index panel 102ms

And Click add index button 128ms

And Fill index form 10s 568ms

And Click ok button in index form 15s 131ms

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

And Go to transport details "TRANSPORT" 4s 435ms

And Expand index panel 122ms

Then Check are transport values equals 092ms

Hooks

After Hooks.deleteProductAfterTest() 079ms

After Hooks.deleteTransportAfterTest() 108ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 172ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 246ms

And Show all transport "true" 080ms

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

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

When Go to transport details "TRANSPORT_ORDER" 4s 463ms

And Expand index panel 103ms

And Click add index button 128ms

And Fill index form 7s 512ms

And Click ok button in index form 15s 097ms

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

And Go to transport details "TRANSPORT_ORDER" 4s 387ms

And Expand index panel 122ms

Then Check are transport values equals 2s 143ms

Hooks

After Hooks.deleteProductAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Steps

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

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

And Show all transport "false" 016ms

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

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

When Go to transport details "TRANSPORT" 4s 459ms

And Add index to transport 25s 955ms

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

When Go to transport details "TRANSPORT" 4s 456ms

And Expand index panel 113ms

And Click delete index button 062ms

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

And Go to transport details "TRANSPORT" 4s 350ms

And Expand index panel 096ms

Then Verify that transport has no indexes 15s 020ms

Hooks

After Hooks.deleteProductAfterTest() 036ms

After Hooks.deleteTransportAfterTest() 105ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 257ms

And Show all transport "true" 087ms

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

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

When Go to transport details "TRANSPORT_ORDER" 4s 469ms

And Add index to transport 22s 920ms

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

When Go to transport details "TRANSPORT_ORDER" 4s 420ms

And Expand index panel 126ms

And Click delete index button 064ms

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

And Go to transport details "TRANSPORT_ORDER" 4s 334ms

And Expand index panel 099ms

Then Verify that transport has no indexes 15s 058ms

Hooks

After Hooks.deleteProductAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 100ms

View Feature Index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 2s 561ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 197ms

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

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

And Go to transport details "OWN_COLLECTION" 4s 438ms

And Add index to transport 24s 561ms

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

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 362ms

When Click on index details icon 137ms

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

Hooks

After Hooks.deleteProductAfterTest() 045ms

After Hooks.deleteTransportAfterTest() 115ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 405ms

And Fill advice form 11s 844ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 7s 773ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 212ms

After Hooks.deleteTransportAfterTest() 118ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 206ms

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 644ms

And Fill advice form 8s 446ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 19s 392ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 152ms

After Hooks.deleteTransportAfterTest() 082ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

And Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 419ms

And Fill advice form 13s 196ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 251ms

After Hooks.deleteTransportAfterTest() 121ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Show all transport types 1s 042ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 45s 154ms

And Go to "TRANSPORT_TABLE" 204ms

And Go to transport details "CONTAINER" 4s 444ms

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

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

And Fill transport form 4s 727ms

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

And Expand advice panel 118ms

And Edit advice in transport details 12s 461ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 37s 257ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 182ms

After Hooks.deleteTransportAfterTest() 111ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Show all transport types 1s 047ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 41s 880ms

And Go to "TRANSPORT_TABLE" 217ms

And Go to transport details "DELIVERY" 4s 534ms

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

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

And Fill transport form 1m 2s 630ms

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

And Expand advice panel 105ms

And Edit advice in transport details 6s 652ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 1m 1s 928ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 220ms

After Hooks.deleteTransportAfterTest() 162ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Show all transport types 1s 047ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 530ms

And Go to "TRANSPORT_TABLE" 202ms

And Go to transport details "LOAD" 4s 430ms

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

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

And Fill transport form 24s 802ms

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

And Expand advice panel 105ms

And Edit advice in transport details 18s 682ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 50s 897ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 266ms

After Hooks.deleteTransportAfterTest() 131ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after status confirmation

Steps

Given Set token of apiUsername "super-admin-skd" 099ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wjazd na teren zakładu" 43s 682ms

Then Check if user got a mail 000ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wyjazd" 55s 386ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 209ms

After Hooks.deleteTransportAfterTest() 124ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Steps

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

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

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

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

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

And Wait "120" seconds 2m

When Get mail "apolloautomattest@gmail.com" message from mail account with "Weryfikacja danych awizacji" 6s 984ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 235ms

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 007ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nowa aukcja" 25s 282ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 200ms

After Hooks.deleteTransportAfterTest() 097ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Steps

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

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 13s 343ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 210ms

After Hooks.deleteTransportAfterTest() 085ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Steps

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

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

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

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

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

And Wait till auction end 1m 58s 023ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Dodano nową ofertę" 7s 344ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 253ms

After Hooks.deleteTransportAfterTest() 075ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Steps

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

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

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

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

And Wait till auction end 1m 58s 022ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 206ms

After Hooks.deleteTransportAfterTest() 097ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Steps

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

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Oferta przelicytowana" 25s 504ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 172ms

After Hooks.deleteTransportAfterTest() 100ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Steps

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 2m 29s 294ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 260ms

After Hooks.deleteTransportAfterTest() 089ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Steps

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 13s 009ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 195ms

After Hooks.deleteTransportAfterTest() 084ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Steps

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

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

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

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

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <422>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApiWith(AuctionTransport.java:69)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes(file:Features/Atom/Mail/AuctionMail.feature:103)

And Wait "90" seconds 000ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zakończenie aukcji" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 182ms

After Hooks.deleteTransportAfterTest() 093ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 290ms

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

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

And Go to "TRANSPORT_TABLE" 143ms

And Go to transport details "DELIVERY" 4s 696ms

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

And Fill transport form 35s 977ms

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

And Fill discrepancy report section 35s 834ms

And Go to transport details "DELIVERY" 4s 571ms

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

And Generate discrepancy report 18s 844ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Utworzono protokół niezgodności" 7s 082ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 345ms

After Hooks.deleteTransportAfterTest() 102ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 789ms

And Select warehouse "Serownia" 1s 388ms

And Set week view 1s 110ms

And Show yesterday 1s 063ms

And Move window into the past 301ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "spóźnił się na" 56s 846ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 286ms

After Hooks.rollbackAddedAuthorities() 047ms

After Hooks.deleteTransportAfterTest() 113ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica import" 1m 2s 750ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 251ms

After Hooks.deleteTransportAfterTest() 060ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica eksport" 1m 7s 309ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 252ms

After Hooks.deleteTransportAfterTest() 074ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.WlZsks}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 5ed07908611229654e6c0bce3e9f1a79
	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:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"(file:Features/Atom/Mail/TransportTransferMail.feature:8)

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 176ms

After Hooks.deleteTransportAfterTest() 074ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.WlZsks}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 5ed07908611229654e6c0bce3e9f1a79
	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:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"(file:Features/Atom/Mail/TransportTransferMail.feature:20)

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zostało przekazane nowe zlecenie" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 181ms

After Hooks.deleteTransportAfterTest() 075ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 13s 708ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.WlZsks}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 5ed07908611229654e6c0bce3e9f1a79
	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:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:43)
	at ✽.Transfer transport to carrier "Przewoźnik SKZ Automat 1"(file:Features/Atom/Mail/TransportTransferMail.feature:32)

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 330ms

After Hooks.deleteTransportAfterTest() 076ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Steps

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

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

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

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

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

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

Then If user is login then logout 110ms

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

And Go to auction details 1s 158ms

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 37s 313ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 422ms

After Hooks.deleteTransportAfterTest() 115ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Steps

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

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

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

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nowe zapytanie ofertowe" 12s 764ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 286ms

After Hooks.deleteTransportAfterTest() 070ms

View Feature Pallet limit

@deleteTransportAfterTest

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

Steps

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

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 140ms

When Go to new transport "DELIVERY" 15s 373ms

And Fill transport form 41s 117ms

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

And Click "save-transport" save button and wait for form to disappear 15s 834ms

And Set advice window in schedule 2s 189ms

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

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

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 067ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 442ms

And Go to "TRANSPORT_TABLE" 239ms

And Show all transport "false" 008ms

And Go to transport details "DELIVERY" 32s 531ms

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

And Click "save-transport" save button 718ms

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

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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]

Steps

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 069ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 280ms

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

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

And Go to "TRANSPORT_TABLE" 211ms

And Click button advice in transport table "LOAD_PL" 081ms

And Set advice window in schedule 2s 778ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 15s 374ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

After Hooks.deleteModeOfTransportationAfterTest() 074ms

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]

Steps

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

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

And Set status of MOT to "DISABLED" 059ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 249ms

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

When Login as "super-admin-bausch" 1s 152ms

And Go to "TRANSPORT_TABLE" 231ms

And Click button advice in transport table "LOAD_PL" 110ms

And Set advice window in schedule 2s 824ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 15s 395ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.deleteModeOfTransportationAfterTest() 078ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "ACCEPTED" 073ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 192ms

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

When Login as "super-admin-bausch" 1s 158ms

And Go to "TRANSPORT_TABLE" 218ms

And Click button advice in transport table "LOAD_PL" 101ms

And Set advice window in schedule 2s 769ms

Then Check if "AAAA0000" MOT can be selected in advice form 407ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.deleteModeOfTransportationAfterTest() 071ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "UPDATED" 059ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 265ms

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

When Login as "super-admin-bausch" 1s 157ms

And Go to "TRANSPORT_TABLE" 218ms

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

And Set advice window in schedule 2s 728ms

Then Check if "AAAA0000" MOT can be selected in advice form 329ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.deleteModeOfTransportationAfterTest() 066ms

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]

Steps

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

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

And Set status of MOT to "REJECTED" 053ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 301ms

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

When Login as "super-admin-bausch" 1s 109ms

And Go to "TRANSPORT_TABLE" 219ms

And Click button advice in transport table "LOAD_PL" 121ms

And Set advice window in schedule 2s 738ms

Then Check if "AAAA0000" MOT is visible in advice form 373ms

And Check if "AAAA0000" MOT cannot be selected in advice form 115ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.deleteModeOfTransportationAfterTest() 077ms

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]

Steps

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

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

And Set status of MOT to "BLOCKED" 072ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 245ms

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

When Login as "super-admin-bausch" 1s 121ms

And Go to "TRANSPORT_TABLE" 199ms

And Click button advice in transport table "LOAD_PL" 109ms

And Set advice window in schedule 2s 723ms

Then Check if "AAAA0000" MOT is visible in advice form 366ms

And Check if "AAAA0000" MOT cannot be selected in advice form 106ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.deleteModeOfTransportationAfterTest() 099ms

View Feature SK Api - Statuses confirmation

@deleteTransportAfterTest

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

Steps

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

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

And Add transport by SKApi in "MGW" 177ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 18s 130ms

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

And Set advice window in schedule 2s 594ms

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

And Fill advice form 14s 719ms

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

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

And Confirm statuses until reach "left-the-factory" through SKAPI 5m 13s 860ms

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

Hooks

After Hooks.deleteTransportAfterTest() 135ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 54s 360ms

And Go to "TRANSPORT_TABLE" 131ms

And Go to transport details "TRANSPORT_ORDER" 4s 479ms

Then Check are transport values equals 382ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 002ms

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "CONTAINER" created in transport table and set transport id 51s 409ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "CONTAINER" 4s 466ms

Then Check are transport values equals 389ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 003ms

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

When Add transport by SKApi in "MGW" 002ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 54s 480ms

And Go to "TRANSPORT_TABLE" 137ms

And Go to transport details "OWN_COLLECTION" 4s 472ms

Then Check are transport values equals 416ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 343ms

And Go to "TRANSPORT_TABLE" 131ms

And Go to transport details "TRANSPORT_ORDER" 4s 435ms

Then Check are transport values equals 427ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 003ms

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "CONTAINER" created in transport table and set transport id 54s 970ms

And Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "CONTAINER" 4s 478ms

Then Check are transport values equals 395ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 002ms

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 54s 493ms

And Go to "TRANSPORT_TABLE" 124ms

And Go to transport details "OWN_COLLECTION" 4s 479ms

Then Check are transport values equals 397ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

Steps

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

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

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 902ms

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

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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

Steps

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

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

When Add transport by SKApi in "" 003ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1m 324ms

And Go to "TRANSPORT_TABLE" 147ms

And Go to transport details "TRANSPORT_ORDER" 4s 484ms

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 54s 419ms

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

And Set advice window in schedule 2s 693ms

And Fill advice form 14s 789ms

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

And Go to "TRANSPORT_TABLE" 223ms

And Go to transport details "CONTAINER" 4s 535ms

Then Check are advice values equals 2s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 1m 3s 541ms

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

And Set advice window in schedule 2s 601ms

And Fill advice form 14s 727ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

Then Check are advice values equals 2s 341ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1m 915ms

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

And Set advice window in schedule 2s 567ms

And Fill advice form 14s 668ms

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

And Go to "TRANSPORT_TABLE" 229ms

And Go to transport details "TRANSPORT_ORDER" 4s 477ms

Then Check are advice values equals 2s 361ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 414ms

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

And Set advice window in schedule 2s 539ms

And Fill advice form 14s 792ms

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

And Go to "TRANSPORT_TABLE" 217ms

Then Check advice data in SK API database "OWN_COLLECTION" 3s 186ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 9s 358ms

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

And Set advice window in schedule 2s 672ms

And Fill advice form 14s 813ms

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

And Go to "TRANSPORT_TABLE" 208ms

Then Check advice data in SK API database "CONTAINER" 1s 110ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 835ms

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

And Set advice window in schedule 2s 543ms

And Fill advice form 14s 684ms

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

And Go to "TRANSPORT_TABLE" 246ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 3s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 9s 355ms

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

And Set advice window in schedule in the past 2s 593ms

And Fill advice form 14s 791ms

And Click advice save button to check error message 083ms

Then Check if possible advice alert is displayed 018ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 40s 117ms

And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 48s 228ms

And Go to "TRANSPORT_TABLE" 209ms

When Go to transport details "OWN_COLLECTION" 4s 465ms

And Expand advice panel 111ms

And Edit advice in transport details 14s 107ms

And Fill arrival date field 2s 307ms

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

Then Check advice data in database after edition "OWN_COLLECTION" 037ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 33s 449ms

And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 48s 247ms

And Go to "TRANSPORT_TABLE" 196ms

When Go to transport details "CONTAINER" 4s 489ms

And Expand advice panel 117ms

And Edit advice in transport details 14s 138ms

And Fill arrival date field 2s 308ms

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

Then Check advice data in database after edition "CONTAINER" 040ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 33s 359ms

And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 48s 268ms

And Go to "TRANSPORT_TABLE" 264ms

When Go to transport details "TRANSPORT_ORDER" 4s 456ms

And Expand advice panel 110ms

And Edit advice in transport details 14s 111ms

And Fill arrival date field 2s 304ms

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

Then Check advice data in database after edition "TRANSPORT_ORDER" 035ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 042ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 039ms

When Go to "WAREHOUSE_TAB" 757ms

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

And Select view "DAYS_2" 2s 086ms

Then Check if gray window is in the schedule 2s 023ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 269ms

And Select view "DAYS_2" 2s 046ms

And Check if gray window is in the schedule 2s 016ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 164ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 042ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 036ms

When Go to "WAREHOUSE_TAB" 763ms

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

And Select view "DAYS_2" 2s 090ms

Then Check if gray window is in the schedule 2s 023ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 270ms

And Select view "DAYS_2" 2s 062ms

And Check if gray window is in the schedule 2s 015ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 147ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

Given Login as "pha1-carrier@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 328ms

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 040ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 034ms

When Go to "WAREHOUSE_TAB" 804ms

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

And Select view "DAYS_2" 2s 091ms

Then Check if gray window is in the schedule 2s 026ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 270ms

And Select view "DAYS_2" 2s 060ms

And Check if gray window is in the schedule 2s 016ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 140ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

And Create "CREATE_GRAY_WINDOW_MGW" window by JSON file for test as "super-admin-skz" 034ms

And Create "CREATE_GRAY_WINDOW_HRL" window by JSON file for test as "super-admin-skz" 033ms

When Go to "WAREHOUSE_TAB" 436ms

And Select warehouse "MGW" 1s 183ms

And Select view "DAYS_2" 2s 078ms

Then Check if gray window is in the schedule 2s 026ms

And Select warehouse "HRL" 1s 393ms

And Select view "DAYS_2" 2s 056ms

And Check if gray window is in the schedule 2s 016ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 146ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 418ms

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

When Find transport in table with status "advice-added" 3s 234ms

And Confirm statuses until reach "process-ended" 28s 130ms

Then Check if transport has "process-ended" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 412ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 546ms

When Find transport in table with status "planned" 17s 257ms

And Confirm statuses until reach "process-ended" 21s 670ms

Then Check if transport has "process-ended" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 341ms

When Find transport in table with status "planned" 3s 224ms

And Confirm statuses until reach "process-ended" 21s 561ms

Then Check if transport has "process-ended" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 287ms

When Find transport in table with status "planned" 17s 213ms

And Confirm statuses until reach "departed" 24s 351ms

Then Check if transport has "departed" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 123ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 320ms

When Find transport in table with status "created" 3s 213ms

And Confirm statuses until reach "process-ended" 21s 526ms

Then Check if transport has "process-ended" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 092ms

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

When Find transport in table with status "created" 3s 228ms

And Confirm statuses until reach "process-ended" 29s 751ms

Then Check if transport has "process-ended" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 324ms

When Find transport in table with status "planned" 3s 218ms

And Confirm statuses until reach "process-ended" 26s 926ms

Then Check if transport has "process-ended" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 350ms

When Find transport in table with status "planned" 3s 232ms

And Confirm statuses until reach "process-ended" 27s 083ms

Then Check if transport has "process-ended" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

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

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

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

When Accept or reject "accept" transferred transport 2s 446ms

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

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

And Set advice window in schedule 2s 599ms

And Fill advice form 14s 695ms

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

And Check if window is "silver" 2s 031ms

And Go to "TRANSPORT_TABLE" 219ms

Then Check if transport has "process-ended" 228ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

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

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

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

When Accept or reject "accept" transferred transport 18s 134ms

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

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

And Set advice window in schedule 2s 662ms

And Fill advice form 14s 689ms

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

And Check if window is "silver" 2s 035ms

And Go to "TRANSPORT_TABLE" 212ms

Then Check if transport has "process-ended" 295ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if it is not possible to edit advice after reach specific status

Steps

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

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_ADVICE" "CHECKPOINT_BASED" "ARRIVAL" 206ms

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

When Login as "hochland-admin" 2s 758ms

And Find transport in table with status "advice-added" 3s 309ms

And Confirm statuses until reach "arrived" 3s 840ms

And Go to transport details "DELIVERY" 4s 689ms

Then Check if it is not possible to edit advice 201ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 088ms

After Hooks.deleteTransportAfterTest() 115ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check is transport color changed after confirm status

Steps

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

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

When Find transport in table with status "advice-added" 3s 219ms

And Check if transport row is "blue" 3s 081ms

And Confirm statuses until reach "arrived" 3s 843ms

And Check if transport row is "green" 3s 073ms

And Confirm statuses until reach "during-unload" 3s 764ms

Then Check if transport row is "orange" 3s 091ms

And Confirm statuses until reach "unloaded" 3s 788ms

Then Check if transport row is "darkgoldenrod" 3s 076ms

And Confirm statuses until reach "process-ended" 4s 284ms

Then Check if transport row is "silver" 3s 074ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

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

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

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

And Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 590ms

And Fill advice form 8s 445ms

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

And Go to "TRANSPORT_TABLE" 246ms

And Find transport in table with status "advice-added" 3s 204ms

And Confirm statuses until reach "left-the-area" 17s 510ms

Then Check if next status is not possible to confirm 104ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 212ms

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

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

And Show all transport types 1s 052ms

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

And Set advice window in schedule 2s 564ms

And Fill advice form 8s 449ms

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

And Go to "TRANSPORT_TABLE" 185ms

And Find transport in table with status "advice-added" 3s 240ms

And Confirm statuses until reach "left-the-area" 17s 539ms

Then Check if next status is not possible to confirm 109ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

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

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

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

And Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 583ms

And Fill advice form 8s 450ms

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

And Go to "TRANSPORT_TABLE" 234ms

And Find transport in table with status "advice-added" 3s 207ms

When Add file to transport by API 533ms

And Confirm statuses until reach "process-ended" 35s 216ms

Then Check if transport has "process-ended" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 208ms

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

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

And Show all transport types 1s 051ms

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

And Set advice window in schedule 2s 571ms

And Fill advice form 8s 398ms

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

And Go to "TRANSPORT_TABLE" 217ms

And Find transport in table with status "advice-added" 3s 234ms

When Add file to transport by API 324ms

And Confirm statuses until reach "process-ended" 35s 268ms

Then Check if transport has "process-ended" 029ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm status by guard without confirming earlier statuses

Steps

Given Set token of apiUsername "super-admin-skd" 097ms

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

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

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

And Login as "swiss-krono-delivery-guard" 2s 149ms

And Go to "TRANSPORT_TABLE" 186ms

When Confirm "Departure" status in transport row 3s 082ms

Then Verify that "Departure" has been confirmed 032ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is possible to confirm status with given confirmation date [A-7159]

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 461ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 240ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 670ms

And Login as "bausch-admin" 1s 158ms

And Go to "TRANSPORT_TABLE" 224ms

And Find transport in table with status "advice-added" 3s 236ms

When Confirm statuses until reach "on-the-way" 9s 379ms

And Open statuses popup 068ms

And Toggle status date confirmation checkbox 15s 043ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-field-name='toggle-confirmation-date']"}
  (Session info: headless chrome=89.0.4389.114)
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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.WlZsks}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 5ed07908611229654e6c0bce3e9f1a79
*** Element info: {Using=xpath, value=//div[@data-field-name='toggle-confirmation-date']}
	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:306)
	at CucumberTests.StatusTests.ConfirmStatuses.toggleStatusDateConfirmationCheckbox(ConfirmStatuses.java:228)
	at ✽.Toggle status date confirmation checkbox(file:Features/Atom/Statuses/ConfirmStatuses.feature:280)

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.deleteModeOfTransportationAfterTest() 103ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 305ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 242ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 719ms

And Login as "bausch-admin" 1s 161ms

And Go to "TRANSPORT_TABLE" 226ms

And Find transport in table with status "advice-added" 3s 219ms

When Confirm statuses until reach "on-the-way" 9s 357ms

And Open statuses popup 062ms

And Toggle status date confirmation checkbox 15s 058ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-field-name='toggle-confirmation-date']"}
  (Session info: headless chrome=89.0.4389.114)
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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.WlZsks}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 5ed07908611229654e6c0bce3e9f1a79
*** Element info: {Using=xpath, value=//div[@data-field-name='toggle-confirmation-date']}
	at sun.reflect.GeneratedConstructorAccessor210.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:306)
	at CucumberTests.StatusTests.ConfirmStatuses.toggleStatusDateConfirmationCheckbox(ConfirmStatuses.java:228)
	at ✽.Toggle status date confirmation checkbox(file:Features/Atom/Statuses/ConfirmStatuses.feature:299)

And Change status execution date to "1" days from today 000ms

Then Verify that status cannot be confirmed 000ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.deleteModeOfTransportationAfterTest() 069ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 292ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 191ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 707ms

And Login as "bausch-admin" 1s 107ms

And Go to "TRANSPORT_TABLE" 214ms

And Find transport in table with status "advice-added" 3s 242ms

When Confirm statuses until reach "on-the-way" 9s 397ms

And Open statuses popup 068ms

And Toggle status date confirmation checkbox 15s 055ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-field-name='toggle-confirmation-date']"}
  (Session info: headless chrome=89.0.4389.114)
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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.WlZsks}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 5ed07908611229654e6c0bce3e9f1a79
*** Element info: {Using=xpath, value=//div[@data-field-name='toggle-confirmation-date']}
	at sun.reflect.GeneratedConstructorAccessor210.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:306)
	at CucumberTests.StatusTests.ConfirmStatuses.toggleStatusDateConfirmationCheckbox(ConfirmStatuses.java:228)
	at ✽.Toggle status date confirmation checkbox(file:Features/Atom/Statuses/ConfirmStatuses.feature:299)

And Change status execution date to "-1" days from today 000ms

Then Verify that status cannot be confirmed 000ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.deleteModeOfTransportationAfterTest() 067ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackTaskChanges

Scenario Outline Confirmed statuses of existing orders should not be deleted - even after editing the order [A-6874]

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 197ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 691ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 202ms

When Login as "farmacol-admin" 2s 537ms

And Go to "TRANSPORT_TABLE" 230ms

And Confirm statuses until reach "during-unload" 9s 430ms

And Set actual confirmed transport status list 1s 378ms

And Disable task by API 204ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 465ms

And Edit transport hours and recalculate statuses 16s 386ms

Then Verify that all confirmed statuses are still on transport status list 173ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

After Hooks.rollbackTaskChanges() 048ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to reject status by guard in transport table

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 109ms

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

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

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

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

When Reject status: Book of disinfection 079ms

And Check if reject date is visible 318ms

Then If user is login then logout 083ms

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

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

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 26s 657ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 182ms

After Hooks.deleteTransportAfterTest() 074ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status twice and reject date is changing

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 1s 959ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 288ms

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

When Reject status: Book of disinfection 082ms

And Check if reject date is visible 154ms

And Get rejection date 031ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 063ms

Then Check if reject date has changed 1s 091ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in transport form

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 128ms

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

And Go to transport details "LOAD" 4s 350ms

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

When Reject status: Book of disinfection 087ms

Then Check if reject date is visible 158ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in statuses popup

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 005ms

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

And Open statuses popup 097ms

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

When Reject status: Book of disinfection 070ms

Then Open statuses popup 050ms

And Check if reject date is visible 085ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 259ms

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

And Confirm to the last status by API 230ms

When Find statuses for transport in table 2s 026ms

And Revoke statuses until reach "advice-added" 6s 837ms

Then Check if transport has "advice-added" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 356ms

And Confirm to the last status by API 226ms

When Find statuses for transport in table 1s 720ms

And Revoke statuses until reach "planned" 6s 718ms

Then Check if transport has "planned" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after created transport without advice, transport has checkpoints only from "preparation" section

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 141ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 179ms

When Find transport in table with status "new" 3s 193ms

And Open statuses popup 085ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 060ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after added advice, checkpoints are generated from "steps" section

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 047ms

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 002ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 179ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 122ms

And Set advice window in schedule 2s 682ms

And Fill advice form 12s 195ms

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

And Go to "TRANSPORT_TABLE" 229ms

When Find transport in table with status "advice-added" 3s 204ms

And Open statuses popup 088ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 073ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 188ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 608ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 026ms

When Login as "farmacol-admin" 1s 037ms

And Go to "TRANSPORT_TABLE" 215ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 7s 139ms

And Disable task by API 057ms

And Find transport pencil button in transports table 1s 269ms

And Click pencil and move transport to next day in schedule 18s 298ms

And Go to "TRANSPORT_TABLE" 256ms

Then Verify that "START_OF_UNLOADING" is not visible 151ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.rollbackTaskChanges() 048ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 397ms

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

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

When Go to "WAREHOUSE_TAB" 785ms

And Select warehouse "Serownia" 1s 386ms

And Set week view 1s 107ms

And Show yesterday 1s 081ms

And Move window into the past 301ms

Then Check if window is "red" 2s 027ms

Hooks

After Hooks.rollbackAddedAuthorities() 043ms

After Hooks.deleteTransportAfterTest() 143ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 039ms

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 051ms

When Go to "WAREHOUSE_TAB" 320ms

And Select warehouse "Magazyn - Nowa Sól" 2s 158ms

And Set week view 1s 191ms

And Show yesterday 1s 057ms

And Move window into the past 420ms

Then Check if window is "red" 2s 025ms

Hooks

After Hooks.rollbackAddedAuthorities() 049ms

After Hooks.deleteTransportAfterTest() 118ms

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 194ms

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 046ms

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 563ms

And Fill advice form 8s 388ms

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

And Select warehouse "Magazyn Hala A" 1s 177ms

And Set week view 2s 110ms

And Show yesterday 1s 182ms

And Move window into the past 577ms

Then Check if window is "red" 2s 060ms

Hooks

After Hooks.rollbackAddedAuthorities() 051ms

After Hooks.deleteTransportAfterTest() 129ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if time window resize with restriction to algorithm settings

Steps

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

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 002ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 469ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 424ms

When Go to "WAREHOUSE_TAB" 808ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 777ms

And Set week view 1s 110ms

And Check if time window length is correct after "CREATE" 017ms

And Change number of pallets in transport 50s 880ms

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

And Check if time window length is correct after "EDIT" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set in transport form

Steps

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

And Get "UNLOAD" settings from "keeeper" 028ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 130ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 110ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 391ms

When Go to "WAREHOUSE_TAB" 355ms

And Select warehouse "Magazyn Surowców" 1s 186ms

And Set week view 1s 104ms

Then Check if time window has proper "60" 021ms

Hooks

After Hooks.rollbackTransportTypeSettings() 072ms

After Hooks.clearAlgorithmSettings() 182ms

After Hooks.deleteTransportAfterTest() 111ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

Steps

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

And Get "UNLOAD" settings from "keeeper" 031ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 101ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 061ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 345ms

When Go to "WAREHOUSE_TAB" 328ms

And Select warehouse "Magazyn Surowców" 1s 149ms

And Set week view 1s 110ms

Then Check if time window has proper "60" 035ms

Hooks

After Hooks.rollbackTransportTypeSettings() 072ms

After Hooks.clearAlgorithmSettings() 115ms

After Hooks.deleteTransportAfterTest() 100ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

Steps

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

And Get "LOAD" settings from "keeeper" 026ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 129ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 070ms

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

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

And Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 407ms

And Fill advice form 13s 235ms

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

Then Check if time window has proper "30" 026ms

Hooks

After Hooks.rollbackTransportTypeSettings() 095ms

After Hooks.clearAlgorithmSettings() 095ms

After Hooks.deleteTransportAfterTest() 090ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

Steps

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

And Get "CONTAINER" settings from "keeeper" 027ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 106ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "20;false" 067ms

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

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

And Show all transport types 1s 050ms

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

And Set advice window in schedule 2s 419ms

And Fill advice form 13s 225ms

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

Then Check if time window has proper "60" 030ms

Hooks

After Hooks.rollbackTransportTypeSettings() 069ms

After Hooks.clearAlgorithmSettings() 103ms

After Hooks.deleteTransportAfterTest() 107ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings

Scenario Outline Check if supplier can change time window size by change number of pallets

Steps

Given Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 694ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 167ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 092ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 350ms

And Set token of apiUsername "super-admin-hochland" 096ms

When Go to transport details "DELIVERY" 32s 718ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 359ms

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

And Go to "WAREHOUSE_TAB" 800ms

And Select warehouse "Serownia" 1s 382ms

And Set week view 1s 097ms

Then Check if time window has proper "60" 027ms

Hooks

After Hooks.clearAlgorithmSettings() 205ms

After Hooks.deleteTransportAfterTest() 106ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Steps

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

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 054ms

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

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 591ms

And Check if time window counter value equals "1" 071ms

And Select view "DAYS_2" 2s 091ms

And Move advice window "2" 1s 359ms

And Select view "DAY" 2s 085ms

Then Check if time window counter value equals "0" 076ms

And Delete created transport by API 104ms

And Check if time window counter value equals "0" 053ms

And Click in free spot in schedule page to create gray window 193ms

And Check if time window counter value equals "0" 054ms

And Click in free spot in schedule page to create dedicated window 052ms

And Check if time window counter value equals "0" 053ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 123ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 109ms

When Go to new transport "DELIVERY" 282ms

And Fill transport form 11s 479ms

And Click "save-transport" save button and wait for form to disappear 15s 604ms

And Set advice window in schedule 2s 182ms

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

And Go to "TRANSPORT_TABLE" 265ms

When Click on time window date 1s 356ms

And Open transport form when in schedule 1s 171ms

Then Check are transport values equals 154ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 415ms

When Go to new transport "DELIVERY" 333ms

And Fill transport form 38s 907ms

And Click "save-transport" save button and wait for form to disappear 15s 588ms

And Set advice window in schedule 2s 172ms

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

And Go to "TRANSPORT_TABLE" 281ms

When Click on time window date 1s 296ms

And Open transport form when in schedule 1s 347ms

Then Check are transport values equals 19s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 562ms

When Go to new transport "CISTERN_DELIVERY" 375ms

And Fill transport form 35s 004ms

And Click "save-transport" save button and wait for form to disappear 15s 917ms

And Set advice window in schedule 2s 219ms

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

And Go to "TRANSPORT_TABLE" 199ms

When Click on time window date 1s 398ms

And Open transport form when in schedule 1s 199ms

Then Check are transport values equals 21s 414ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 444ms

When Go to new transport "CISTERN_COLLECTION" 326ms

And Fill transport form 28s 397ms

And Click "save-transport" save button and wait for form to disappear 15s 856ms

And Set advice window in schedule 2s 204ms

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

And Go to "TRANSPORT_TABLE" 207ms

When Click on time window date 1s 452ms

And Open transport form when in schedule 1s 191ms

Then Check are transport values equals 21s 367ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 512ms

When Go to new transport "DELIVERY" 286ms

And Fill transport form 38s 080ms

And Click "save-transport" save button and wait for form to disappear 15s 597ms

And Set advice window in schedule 2s 167ms

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

And Go to "TRANSPORT_TABLE" 194ms

When Click on time window date 1s 350ms

And Open transport form when in schedule 1s 162ms

Then Check are transport values equals 19s 339ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 002ms

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

When Go to new transport "LOAD" 301ms

And Fill transport form 38s 054ms

And Click "save-transport" save button and wait for form to disappear 15s 655ms

And Set advice window in schedule 2s 181ms

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

And Go to "TRANSPORT_TABLE" 231ms

When Click on time window date 1s 325ms

And Open transport form when in schedule 1s 173ms

Then Check are transport values equals 19s 337ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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

Steps

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

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 095ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 053ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 095ms

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

And Login as "farmacol-admin" 2s 412ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 696ms

And Go to "TRANSPORT_TABLE" 315ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 471ms

And Add step "unload" 112ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 463ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 372ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 360ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 323ms

Then Click "save-transport" save button 171ms

And Set advice window in schedule in "2" days 4s 934ms

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

And Go to "TRANSPORT_TABLE" 259ms

And Check if transport has "2" time windows 015ms

Hooks

After Hooks.rollbackTransportTypeSettings() 062ms

After Hooks.rollbackAddedActionAuthorities() 060ms

After Hooks.deleteTransportAfterTest() 125ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 038ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 067ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 208ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 146ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 024ms

And Go to "TRANSPORT_TABLE" 321ms

And Get checkpoint colors for transport 005ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 42s 658ms

Hooks

After Hooks.rollbackTransportTypeSettings() 122ms

After Hooks.deleteTransportAfterTest() 147ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 038ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 062ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 247ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 114ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 984ms

And Go to "TRANSPORT_TABLE" 310ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 42s 602ms

Hooks

After Hooks.rollbackTransportTypeSettings() 089ms

After Hooks.deleteTransportAfterTest() 141ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in schedule

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 035ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 069ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 248ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 094ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 979ms

And Get checkpoint colors for transport 005ms

And Go to "TRANSPORT_TABLE" 310ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 5s 448ms

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.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:118)
	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.rollbackTransportTypeSettings() 138ms

After Hooks.deleteTransportAfterTest() 130ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in schedule

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 037ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 068ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 207ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 165ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 041ms

And Get checkpoint colors for transport 005ms

And Go to "TRANSPORT_TABLE" 318ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 32s 012ms

Hooks

After Hooks.rollbackTransportTypeSettings() 080ms

After Hooks.deleteTransportAfterTest() 139ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if window is active after using "create similar" on that window [A-7009]

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 222ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 625ms

And Login as "super-admin-farmacol" 2s 480ms

And Show all transport types 1s 157ms

And Click on time window date 1s 639ms

Then Open transport form when in schedule 1s 295ms

And Click create similar button 15s 147ms

And Click cancel button in transport form 104ms

And Open transport form when in schedule 1s 158ms

Then Check if transport form modal is visible 042ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 025ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 002ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 025ms

And Set proper delay time to move order to archive after task timeout 044ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 363ms

And Go to "WAREHOUSE_TAB" 632ms

And Change warehouse in schedule to: "Katowice" 1s 100ms

And Wait "60" seconds 1m

And Verify that transport window is grey 036ms

And Verify that transport is in archive 1s 160ms

Then Restore transport from archive 1s 096ms

And Verify that transport has been successfully restored 15s 278ms

Hooks

After Hooks.rollbackSettings() 037ms

After Hooks.deleteTransportAfterTest() 099ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings

Scenario Outline Check if confirming transport status removed it to the archive

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 1s 134ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 185ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 034ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 003ms

When Go to "TRANSPORT_TABLE" 142ms

And Click button advice in transport table "OWN_COLLECTION" 2s 014ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 277ms

And Go to "TRANSPORT_TABLE" 210ms

And Find transport in table with status "planned-magazyn-tychy" 3s 248ms

And Confirm statuses until reach "process-ended" 24s 350ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 256ms

And Show "OWN_COLLECTION" 071ms

And Verify that created transport is "true" in transport table 15s 043ms

Hooks

After Hooks.rollbackSettings() 041ms

After Hooks.deleteTransportAfterTest() 090ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Steps

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

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

When Fill auction form 15s 453ms

Then Verify that the auction has been added to transport 058ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Steps

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

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

When Fill auction form 15s 404ms

Then Verify that the auction has been added to transport 049ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept auction offer with minimum rate

Steps

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

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

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

When If user is login then logout 132ms

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

And Go to auction offer 1s 210ms

And Accept transport with minimum rate 15s 621ms

Then Check if carrier is assigned to transport 022ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Steps

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

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

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

When If user is login then logout 114ms

And Login as "paa1-carrier@qa.qa-test" 1s 126ms

And Go to auction offer 1s 293ms

And Reject auction offer 15s 603ms

Then Verify that offer has been removed from transport 15s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Steps

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

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

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

When If user is login then logout 110ms

And Login as "pskza1-carrier@qa.qa-test" 1s 187ms

And Go to auction offer 1s 205ms

And Reject auction offer 15s 629ms

Then Verify that offer has been removed from transport 15s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Steps

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

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

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

When If user is login then logout 108ms

And Login as "paa1-carrier@qa.qa-test" 1s 172ms

And Go to auction offer 1s 307ms

And Offer prize above maximum - "20000" 142ms

Then Verify that is not possible to add offer 157ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Steps

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

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

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

When If user is login then logout 096ms

And Login as "pskza1-carrier@qa.qa-test" 1s 058ms

And Go to auction offer 1s 208ms

And Offer prize above maximum - "20000" 144ms

Then Verify that is not possible to add offer 090ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

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

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

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

And Wait till auction end 1m 58s 018ms

Then Verify that is possible to add auction 053ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

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

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

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

And Wait till auction end 1m 58s 017ms

Then Verify that is possible to add auction 055ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Steps

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

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

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

And Go to auction offer 1s 211ms

When Offer "1000" 151ms

Then Verify that offer with "1000" has been added to auction 3s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Steps

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

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

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

And Go to auction offer 1s 205ms

When Offer "1000" 135ms

Then Verify that offer with "1000" has been added to auction 3s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke an offer

Steps

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

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

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

And Go to auction offer 1s 200ms

When Offer "1000" 139ms

And Verify that offer with "1000" has been added to auction 3s 036ms

Then Go to auction offer 1s 179ms

And Revoke current offer 572ms

And Verify that offer has been revoked 30s 609ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to offer more than last price

Steps

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

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

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

And Go to auction offer 1s 170ms

When Offer "1000" 126ms

And Verify that offer with "1000" has been added to auction 3s 035ms

Then Go to auction offer 1s 172ms

And Offer "1500" 113ms

And Verify that offer with "1500" has been added to auction 3s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to finish active auction

Steps

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

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

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

And Go to auction offer 1s 197ms

When Offer "1000" 123ms

And Verify that offer with "1000" has been added to auction 3s 036ms

Then Login as "swisskrono-admin" 1s 061ms

And Go to auction details 1s 188ms

And Finish active auction 058ms

And Verify that the transport has no active auction 162ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

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

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

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

And Go to auction offer 1s 212ms

When Offer "1000" 145ms

Then Verify that carrier can see current place in auction depending on the "true" role 145ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

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

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

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

And Go to auction offer 1s 209ms

When Offer "1000" 143ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to add offer below min price

Steps

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

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

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

And Go to auction offer 1s 218ms

When Offer "300" 142ms

And Verify that carrier can't add offer to auction 031ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Steps

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

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

And Show all transport "false" 013ms

When Go to auction form 1s 226ms

Then Verify carrier selection value "false" 043ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 024ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 255ms

And Show all transport "true" 073ms

When Go to auction form 1s 215ms

Then Verify carrier selection value "true" 041ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Steps

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

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

When Open transport auction form 168ms

And Select all companies checkbox in transport auction form 054ms

And Unselect company "PAA2" in transport auction form 067ms

And Put transport on auction 15s 216ms

And Open transport auction history 103ms

And Open participants section in transport auction history 053ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 021ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Steps

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

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

When Open transport auction form 181ms

And Select all companies checkbox in transport auction form 057ms

And Unselect company "PSKZA2" in transport auction form 069ms

And Put transport on auction 15s 217ms

And Open transport auction history 085ms

And Open participants section in transport auction history 060ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_UNLOAD" "super-admin-pgf" 002ms

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 092ms

When Go to new transport "UNLOAD" 15s 255ms

And Fill transport form 24s 638ms

And Click "save-transport" save button and wait for form to disappear 15s 915ms

And Set advice window in schedule 2s 197ms

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

And Go to "TRANSPORT_TABLE" 198ms

And Go to transport details "UNLOAD" 32s 450ms

Then Check are transport values equals 21s 416ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 003ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 133ms

When Go to new transport "DELIVERY" 296ms

And Fill transport form 11s 466ms

And Click "save-transport" save button and wait for form to disappear 15s 636ms

And Set advice window in schedule 2s 177ms

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

And Go to "TRANSPORT_TABLE" 251ms

And Go to transport details "DELIVERY" 4s 366ms

Then Check are transport values equals 144ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 136ms

When Go to new transport "OWN_COLLECTION" 306ms

And Fill transport form 17s 995ms

And Click "save-transport" save button and wait for form to disappear 15s 601ms

And Set advice window in schedule 2s 186ms

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

And Go to "TRANSPORT_TABLE" 184ms

And Go to transport details "OWN_COLLECTION" 4s 347ms

Then Check are transport values equals 176ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 421ms

When Go to new transport "DELIVERY" 365ms

And Fill transport form 39s 007ms

And Click "save-transport" save button and wait for form to disappear 15s 607ms

And Set advice window in schedule 2s 157ms

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

And Go to "TRANSPORT_TABLE" 262ms

And Go to transport details "DELIVERY" 4s 642ms

Then Check are transport values equals 19s 406ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 390ms

When Go to new transport "CISTERN_DELIVERY" 366ms

And Fill transport form 34s 998ms

And Click "save-transport" save button and wait for form to disappear 15s 902ms

And Set advice window in schedule 2s 198ms

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

And Go to "TRANSPORT_TABLE" 212ms

And Go to transport details "CISTERN_DELIVERY" 4s 395ms

Then Check are transport values equals 21s 405ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 457ms

When Go to new transport "CISTERN_COLLECTION" 368ms

And Fill transport form 28s 498ms

And Click "save-transport" save button and wait for form to disappear 15s 905ms

And Set advice window in schedule 2s 243ms

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

And Go to "TRANSPORT_TABLE" 211ms

And Go to transport details "CISTERN_COLLECTION" 4s 391ms

Then Check are transport values equals 21s 418ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 424ms

When Go to new transport "OWN_COLLECTION" 346ms

And Fill transport form 32s 852ms

And Click "save-transport" save button and wait for form to disappear 15s 679ms

And Set advice window in schedule 2s 173ms

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

And Go to "TRANSPORT_TABLE" 202ms

And Go to transport details "OWN_COLLECTION" 4s 568ms

Then Check are transport values equals 19s 346ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 481ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 395ms

And Fill transport form 32s 864ms

And Click "save-transport" save button and wait for form to disappear 15s 702ms

And Set advice window in schedule 2s 184ms

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

And Go to "TRANSPORT_TABLE" 180ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 473ms

Then Check are transport values equals 4s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_EXPORT" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 386ms

When Go to new transport "EXPORT" 391ms

And Fill transport form 40s 682ms

And Click "save-transport" save button and wait for form to disappear 15s 621ms

And Set advice window in schedule 2s 156ms

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

And Go to "TRANSPORT_TABLE" 211ms

And Go to transport details "EXPORT" 5s 465ms

Then Check are transport values equals 4s 383ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-skd" 002ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 152ms

When Go to new transport "DELIVERY" 15s 271ms

And Fill transport form 28s 475ms

And Click "save-transport" save button and wait for form to disappear 15s 626ms

And Set advice window in schedule 2s 162ms

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

And Go to "TRANSPORT_TABLE" 223ms

And Go to transport details "DELIVERY" 32s 356ms

Then Check are transport values equals 36s 405ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 002ms

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

When Go to new transport "DELIVERY" 312ms

And Fill transport form 38s 105ms

And Click "save-transport" save button and wait for form to disappear 15s 641ms

And Set advice window in schedule 2s 161ms

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

And Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "DELIVERY" 4s 311ms

Then Check are transport values equals 19s 303ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 002ms

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

When Go to new transport "LOAD" 300ms

And Fill transport form 38s 074ms

And Click "save-transport" save button and wait for form to disappear 15s 645ms

And Set advice window in schedule 2s 176ms

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

And Go to "TRANSPORT_TABLE" 245ms

And Go to transport details "LOAD" 4s 310ms

Then Check are transport values equals 19s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-keeeper" 003ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 259ms

When Go to new transport "UNLOAD" 313ms

And Fill transport form 37s 704ms

And Click "save-transport" save button and wait for form to disappear 15s 601ms

And Set advice window in schedule 2s 176ms

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

And Go to "TRANSPORT_TABLE" 209ms

And Go to transport details "UNLOAD" 4s 384ms

Then Check are transport values equals 21s 395ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 003ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 160ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 345ms

And Fill transport form 37s 723ms

And Click "save-transport" save button and wait for form to disappear 15s 618ms

And Set advice window in schedule 2s 149ms

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

And Go to "TRANSPORT_TABLE" 201ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 373ms

Then Check are transport values equals 21s 428ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 131ms

When Go to new transport "DELIVERY" 313ms

And Fill transport form 22s 949ms

And Click "save-transport" save button and wait for form to disappear 15s 618ms

And Set advice window in schedule 2s 171ms

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

And Go to "TRANSPORT_TABLE" 198ms

And Go to transport details "DELIVERY" 4s 338ms

Then Check are transport values equals 17s 299ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_WEIGHING" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 445ms

When Go to new transport "WEIGHING" 326ms

And Fill transport form 13s 569ms

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

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 160ms

And Go to transport details "WEIGHING" 4s 432ms

And Check are transport values equals 2s 183ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 156ms

When Go to new transport "TRANSPORT" 386ms

And Fill transport form 26s 831ms

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

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 139ms

And Go to transport details "TRANSPORT" 4s 467ms

And Check are transport values equals 6s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 153ms

When Go to new transport "CONTAINER" 324ms

And Fill transport form 11s 219ms

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

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 136ms

And Go to transport details "CONTAINER" 4s 370ms

And Check are transport values equals 079ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 447ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 326ms

And Fill transport form 12s 984ms

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

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 142ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 620ms

And Check are transport values equals 4s 203ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-piast" 002ms

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

When Go to new transport "DELIVERY" 307ms

And Fill transport form 22s 584ms

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

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 132ms

And Go to transport details "DELIVERY" 4s 541ms

And Check are transport values equals 17s 182ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-piast" 002ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 211ms

When Go to new transport "LOAD" 380ms

And Fill transport form 26s 395ms

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

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 158ms

And Go to transport details "LOAD" 4s 654ms

And Check are transport values equals 2s 160ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 125ms

When Go to new transport "LOAD" 287ms

And Fill transport form 24s 731ms

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

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 150ms

And Go to transport details "LOAD" 4s 396ms

And Check are transport values equals 19s 227ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 130ms

When Go to new transport "CONTAINER" 313ms

And Fill transport form 24s 670ms

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

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 131ms

And Go to transport details "CONTAINER" 4s 360ms

And Check are transport values equals 19s 235ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 002ms

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

When Go to new transport "SMALLS_IMPORT" 411ms

And Fill transport form 36s 562ms

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

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 145ms

And Go to transport details "SMALLS_IMPORT" 4s 456ms

And Check are transport values equals 10s 422ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 002ms

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

When Go to new transport "SMALLS_EXPORT" 402ms

And Fill transport form 36s 461ms

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

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 150ms

And Go to transport details "SMALLS_EXPORT" 4s 424ms

And Check are transport values equals 10s 428ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 118ms

When Go to new transport "TRANSPORT_ORDER" 411ms

And Fill transport form 30s 111ms

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

And Show all transport "true" 090ms

And Go to "TRANSPORT_TABLE" 134ms

And Go to transport details "TRANSPORT_ORDER" 4s 409ms

And Check are transport values equals 19s 359ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 172ms

When Go to new transport "TRANSPORT" 369ms

And Fill transport form 37s 762ms

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

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "TRANSPORT" 4s 432ms

And Check are transport values equals 4s 243ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_INBOUND_WITHOUT_WAREHOUSES" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 107ms

When Go to new transport "INBOUND" 365ms

And Fill transport form 41s 110ms

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

And Show all transport "true" 100ms

And Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "INBOUND" 4s 497ms

And Check are transport values equals 2s 271ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 001ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 224ms

When Go to new transport "EXTERNAL_DELIVERY" 330ms

And Fill transport form 53s 931ms

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

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 142ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 391ms

And Check are transport values equals 4s 503ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "dfa1-supplier" 003ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 2s 591ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 249ms

And Fill transport form 47s 314ms

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

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 159ms

And Go to transport details "EXTERNAL_DELIVERY" 32s 382ms

And Check are transport values equals 4s 486ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 077ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 621ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 32s 515ms

And Fill transport form 30s 517ms

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

And Go to transport details "UNLOAD" 32s 366ms

Then Check are transport values equals 4s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

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

And Show all transport "false" 011ms

When Go to transport details "TRANSPORT" 4s 446ms

And Fill transport form 10s 320ms

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

And Go to transport details "TRANSPORT" 4s 496ms

Then Check are transport values equals 4s 150ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

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

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

And Show all transport "false" 012ms

When Go to transport details "CONTAINER" 4s 382ms

And Fill transport form 4s 710ms

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

And Go to transport details "CONTAINER" 4s 365ms

Then Check are transport values equals 043ms

Hooks

After Hooks.deleteTransportAfterTest() 056ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 300ms

And Show all transport "false" 012ms

When Go to transport details "DELIVERY" 4s 376ms

And Fill transport form 11s 623ms

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

And Go to transport details "DELIVERY" 4s 340ms

Then Check are transport values equals 128ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 305ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 360ms

And Fill transport form 21s 619ms

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

And Go to transport details "OWN_COLLECTION" 4s 331ms

Then Check are transport values equals 2s 235ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 455ms

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

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

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 766ms

And Fill transport form 36s 088ms

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

And Go to transport details "DELIVERY" 4s 433ms

Then Check are transport values equals 10s 584ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 413ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 361ms

And Show all transport "false" 023ms

When Go to transport details "OWN_COLLECTION" 4s 676ms

And Fill transport form 36s 676ms

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

And Go to transport details "OWN_COLLECTION" 4s 444ms

Then Check are transport values equals 6s 391ms

Hooks

After Hooks.deleteTransportAfterTest() 160ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 475ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 432ms

And Show all transport "false" 010ms

When Go to transport details "EXPORT" 5s 621ms

And Fill transport form 48s 155ms

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

And Go to transport details "EXPORT" 4s 457ms

Then Check are transport values equals 8s 537ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 421ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

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

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 695ms

And Fill transport form 36s 149ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 451ms

Then Check are transport values equals 12s 526ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 482ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 348ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 528ms

And Fill transport form 27s 354ms

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

And Go to transport details "CISTERN_DELIVERY" 4s 375ms

Then Check are transport values equals 6s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 430ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 343ms

And Show all transport "false" 011ms

When Go to transport details "CISTERN_COLLECTION" 4s 470ms

And Fill transport form 26s 011ms

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

And Go to transport details "CISTERN_COLLECTION" 4s 370ms

Then Check are transport values equals 6s 299ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 432ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 226ms

And Show all transport "false" 010ms

When Go to transport details "WEIGHING" 4s 378ms

And Fill transport form 12s 377ms

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

And Go to transport details "WEIGHING" 4s 297ms

Then Check are transport values equals 2s 160ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 429ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 335ms

And Show all transport "false" 012ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 558ms

And Fill transport form 35s 326ms

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

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 424ms

Then Check are transport values equals 6s 397ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 240ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 32s 370ms

And Fill transport form 25s 766ms

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

And Go to transport details "DELIVERY" 32s 325ms

Then Check are transport values equals 2s 202ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 231ms

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

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

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 712ms

And Fill transport form 57s 473ms

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

And Go to transport details "LOAD" 4s 479ms

Then Check are transport values equals 24s 832ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 125ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 346ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 379ms

And Fill transport form 16s 496ms

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

And Go to transport details "DELIVERY" 4s 348ms

Then Check are transport values equals 082ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 094ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 002ms

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

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 377ms

And Fill transport form 28s 252ms

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

And Go to transport details "LOAD" 4s 314ms

Then Check are transport values equals 2s 240ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 373ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 4s 435ms

And Fill transport form 37s 972ms

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

And Go to transport details "UNLOAD" 4s 418ms

Then Check are transport values equals 6s 403ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 353ms

And Show all transport "false" 011ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 418ms

And Fill transport form 36s 410ms

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

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 380ms

Then Check are transport values equals 6s 403ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

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

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

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 383ms

And Fill transport form 24s 773ms

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

And Go to transport details "LOAD" 4s 361ms

Then Check are transport values equals 4s 226ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

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

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

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 399ms

And Fill transport form 24s 768ms

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

And Go to transport details "CONTAINER" 4s 336ms

Then Check are transport values equals 4s 202ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 002ms

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

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 500ms

And Fill transport form 33s 057ms

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

And Go to transport details "SMALLS_EXPORT" 4s 424ms

Then Check are transport values equals 8s 345ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 178ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 304ms

And Show all transport "true" 066ms

When Go to transport details "DELIVERY" 4s 337ms

And Fill transport form 19s 654ms

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

And Go to transport details "DELIVERY" 4s 372ms

Then Check are transport values equals 166ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 097ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 307ms

And Show all transport "true" 081ms

When Go to transport details "TRANSPORT_ORDER" 4s 445ms

And Fill transport form 26s 845ms

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

And Go to transport details "TRANSPORT_ORDER" 4s 378ms

Then Check are transport values equals 2s 258ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 191ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 371ms

And Fill transport form 8s 919ms

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

And Go to transport details "CONTAINER" 4s 401ms

Then Check are transport values equals 4s 123ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 429ms

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

And Show all transport "false" 010ms

When Delete transport 17s 875ms

Then Transport not displayed in table of transports 15s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 265ms

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

And Show all transport "false" 010ms

When Delete transport 17s 217ms

Then Transport not displayed in table of transports 15s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 123ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 351ms

And Show all transport "false" 011ms

When Delete transport 17s 546ms

Then Transport not displayed in table of transports 15s 072ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

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

And Show all transport "false" 012ms

When Delete transport 17s 050ms

Then Transport not displayed in table of transports 15s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

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

And Show all transport "false" 007ms

When Delete transport 17s 691ms

Then Transport not displayed in table of transports 15s 061ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

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

And Show all transport "false" 011ms

When Delete transport 17s 707ms

Then Transport not displayed in table of transports 15s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 176ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 329ms

And Show all transport "true" 078ms

When Delete transport 19s 152ms

Then Transport not displayed in table of transports 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 164ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 240ms

And Show all transport "true" 079ms

When Delete transport 17s 135ms

Then Transport not displayed in table of transports 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 135ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 612ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 32s 550ms

And Fill transport form 30s 553ms

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

And Click cancel button in transport form 065ms

And Go to transport details "UNLOAD" 32s 396ms

Then Check are transport values equals 4s 295ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

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

And Show all transport "false" 010ms

When Go to transport details "TRANSPORT" 4s 501ms

And Fill transport form 10s 321ms

And Click "save-transport" save button 738ms

And Click cancel button in transport form 071ms

And Go to transport details "TRANSPORT" 4s 336ms

Then Check are transport values equals 4s 149ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

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

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

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 390ms

And Fill transport form 4s 739ms

And Click "save-transport" save button 705ms

And Click cancel button in transport form 066ms

And Go to transport details "CONTAINER" 4s 287ms

Then Check are transport values equals 045ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 293ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 349ms

And Fill transport form 11s 634ms

And Click "save-transport" save button 701ms

And Click cancel button in transport form 082ms

And Go to transport details "DELIVERY" 4s 284ms

Then Check are transport values equals 133ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 291ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 361ms

And Fill transport form 21s 745ms

And Click "save-transport" save button 702ms

And Click cancel button in transport form 084ms

And Go to transport details "OWN_COLLECTION" 4s 334ms

Then Check are transport values equals 2s 217ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 487ms

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

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

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 739ms

And Fill transport form 36s 042ms

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

And Click cancel button in transport form 087ms

And Go to transport details "DELIVERY" 4s 427ms

Then Check are transport values equals 10s 565ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 436ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 360ms

And Show all transport "false" 009ms

When Go to transport details "OWN_COLLECTION" 4s 703ms

And Fill transport form 36s 744ms

And Click "save-transport" save button 897ms

And Click cancel button in transport form 084ms

And Go to transport details "OWN_COLLECTION" 4s 371ms

Then Check are transport values equals 6s 364ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 474ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 363ms

And Show all transport "false" 010ms

When Go to transport details "EXPORT" 5s 670ms

And Fill transport form 48s 124ms

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

And Click cancel button in transport form 095ms

And Go to transport details "EXPORT" 4s 432ms

Then Check are transport values equals 8s 507ms

Hooks

After Hooks.deleteTransportAfterTest() 153ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 478ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

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

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 706ms

And Fill transport form 36s 199ms

And Click "save-transport" save button 937ms

And Click cancel button in transport form 076ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 404ms

Then Check are transport values equals 12s 490ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 497ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 345ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 516ms

And Fill transport form 27s 301ms

And Click "save-transport" save button 773ms

And Click cancel button in transport form 088ms

And Go to transport details "CISTERN_DELIVERY" 4s 374ms

Then Check are transport values equals 6s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 418ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 322ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_COLLECTION" 4s 440ms

And Fill transport form 25s 931ms

And Click "save-transport" save button 780ms

And Click cancel button in transport form 077ms

And Go to transport details "CISTERN_COLLECTION" 4s 388ms

Then Check are transport values equals 6s 260ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 480ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 261ms

And Show all transport "false" 010ms

When Go to transport details "WEIGHING" 4s 416ms

And Fill transport form 12s 401ms

And Click "save-transport" save button 688ms

And Click cancel button in transport form 073ms

And Go to transport details "WEIGHING" 4s 318ms

Then Check are transport values equals 2s 164ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 367ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 365ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 562ms

And Fill transport form 35s 355ms

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

And Click cancel button in transport form 097ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 393ms

Then Check are transport values equals 6s 358ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 313ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 32s 440ms

And Fill transport form 25s 702ms

And Click "save-transport" save button 717ms

And Click cancel button in transport form 097ms

And Go to transport details "DELIVERY" 32s 347ms

Then Check are transport values equals 2s 218ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 219ms

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

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

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 586ms

And Fill transport form 57s 479ms

And Click "save-transport" save button 962ms

And Click cancel button in transport form 077ms

And Go to transport details "LOAD" 4s 393ms

Then Check are transport values equals 24s 837ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 158ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 353ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 369ms

And Fill transport form 16s 499ms

And Click "save-transport" save button 727ms

And Click cancel button in transport form 080ms

And Go to transport details "DELIVERY" 4s 306ms

Then Check are transport values equals 078ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 066ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 002ms

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

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 328ms

And Fill transport form 28s 236ms

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

And Click cancel button in transport form 069ms

And Go to transport details "LOAD" 4s 338ms

Then Check are transport values equals 2s 241ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 381ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 4s 449ms

And Fill transport form 37s 924ms

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

And Click cancel button in transport form 095ms

And Go to transport details "UNLOAD" 4s 353ms

Then Check are transport values equals 6s 406ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 379ms

And Show all transport "false" 010ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 454ms

And Fill transport form 36s 371ms

And Click "save-transport" save button 791ms

And Click cancel button in transport form 085ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 323ms

Then Check are transport values equals 6s 370ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

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

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

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 393ms

And Fill transport form 24s 763ms

And Click "save-transport" save button 728ms

And Click cancel button in transport form 072ms

And Go to transport details "LOAD" 4s 315ms

Then Check are transport values equals 4s 209ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

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

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

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 368ms

And Fill transport form 24s 801ms

And Click "save-transport" save button 718ms

And Click cancel button in transport form 078ms

And Go to transport details "CONTAINER" 4s 330ms

Then Check are transport values equals 4s 196ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 001ms

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

And Show all transport "false" 010ms

When Go to transport details "SMALLS_IMPORT" 4s 516ms

And Fill transport form 33s 082ms

And Click "save-transport" save button 728ms

And Click cancel button in transport form 077ms

And Go to transport details "SMALLS_IMPORT" 4s 378ms

Then Check are transport values equals 8s 378ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 001ms

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

And Show all transport "false" 005ms

When Go to transport details "SMALLS_EXPORT" 4s 532ms

And Fill transport form 33s 128ms

And Click "save-transport" save button 729ms

And Click cancel button in transport form 069ms

And Go to transport details "SMALLS_EXPORT" 4s 360ms

Then Check are transport values equals 8s 397ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 183ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 328ms

And Show all transport "true" 085ms

When Go to transport details "DELIVERY" 4s 348ms

And Fill transport form 19s 668ms

And Click "save-transport" save button 707ms

And Click cancel button in transport form 091ms

And Go to transport details "DELIVERY" 4s 273ms

Then Check are transport values equals 180ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 220ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 284ms

And Show all transport "true" 081ms

When Go to transport details "TRANSPORT_ORDER" 4s 438ms

And Fill transport form 26s 836ms

And Click "save-transport" save button 739ms

And Click cancel button in transport form 088ms

And Go to transport details "TRANSPORT_ORDER" 4s 347ms

Then Check are transport values equals 2s 248ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if firstPossibleStart algorithm works properly when creating transport advice

Steps

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

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

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 277ms

And If user is login then logout 109ms

Then Login as "dka1-supplier" 1s 181ms

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

And Check if moved to first possible start date in schedule 384ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 455ms

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to create transport with new address [A-7158]

Steps

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

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 007ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 296ms

Then Go to new transport "LOAD" 365ms

And Fill transport form 23s 535ms

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

And Go to "COMPANIES_TAB" 394ms

And Go to company "Dostawca Piast Automat 1" details 063ms

And Check if new address with "Adresat" is visible in company details 118ms

And Go to "TRANSPORT_TABLE" 218ms

And Go to transport details "LOAD" 4s 686ms

Hooks

After Hooks.deleteAddressAfterTest() 056ms

After Hooks.deleteTransportAfterTest() 089ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to add new address in existing transport [A-7158]

Steps

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

When Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 182ms

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

Then Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 174ms

And Go to transport details "LOAD" 4s 806ms

And Fill transport form 12s 134ms

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

And Go to "COMPANIES_TAB" 386ms

And Go to company "Dostawca Piast Automat 1" details 073ms

And Check if new address with "Adresat" is visible in company details 110ms

Error message

java.lang.AssertionError: Firma nie posiada nowego adresu!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Company.EditCompanyTest.checkIfNewAddressWithIsVisibleInCompanyDetails(EditCompanyTest.java:114)
	at ✽.Check if new address with "Adresat" is visible in company details(file:Features/Atom/Transport/CrudTransport.feature:211)

Hooks

After Hooks.deleteAddressAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 061ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 280ms

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

When Go to "TRANSPORT_TABLE" 132ms

And Show all transport types 1s 043ms

And Verify that transport has "0" files 039ms

Then Add file to transport by API 372ms

And Verify that transport has "1" files 630ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 107ms

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

When Go to "TRANSPORT_TABLE" 136ms

And Show all transport types 1s 045ms

And Verify that transport has "0" files 034ms

Then Add file to transport by API 205ms

And Verify that transport has "1" files 549ms

Hooks

After Hooks.deleteTransportAfterTest() 049ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 271ms

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

When Go to "TRANSPORT_TABLE" 121ms

And Show all transport types 1s 039ms

And Verify that transport has "0" files 040ms

Then Add file to transport by API 220ms

And Verify that transport has "1" files 372ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

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

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

When Go to "TRANSPORT_TABLE" 129ms

And Show all transport types 1s 047ms

And Verify that transport has "0" files 039ms

Then Add file to transport by API 217ms

And Verify that transport has "1" files 928ms

Hooks

After Hooks.deleteTransportAfterTest() 054ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 120ms

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

And Delete transport 17s 209ms

When Go to "ARCHIVE_TAB" 254ms

And Show "DELIVERY" 062ms

And Verify that transport has "0" files 644ms

Then Add file to transport 148ms

And Verify that transport has "1" files 365ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 173ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 220ms

And Delete transport 17s 344ms

When Go to "ARCHIVE_TAB" 220ms

And Show "LOAD" 093ms

And Verify that transport has "0" files 1s 163ms

Then Add file to transport 145ms

And Verify that transport has "1" files 376ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 349ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 395ms

And Delete transport 17s 869ms

When Go to "ARCHIVE_TAB" 258ms

And Show "DELIVERY" 047ms

And Verify that transport has "0" files 970ms

Then Add file to transport 158ms

And Verify that transport has "1" files 371ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 158ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 203ms

And Delete transport 17s 541ms

When Go to "ARCHIVE_TAB" 265ms

And Show "CONTAINER" 082ms

And Verify that transport has "0" files 1s 016ms

Then Add file to transport 159ms

And Verify that transport has "1" files 333ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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

Steps

Given Set token of apiUsername "super-admin-adama" 091ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 226ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 125ms

And Set token of apiUsername "paa1-carrier@qa.qa-test" 098ms

And Accept transferred transport by Api 161ms

And Login as "paa1-carrier@qa.qa-test" 1s 026ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 229ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 122ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 205ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 117ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 851ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after winning the auction

Steps

Given Set token of apiUsername "super-admin-adama" 096ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 208ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 161ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 336ms

And Login as "paa1-carrier@qa.qa-test" 1s 049ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR documents are added to transport after creation

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 175ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 247ms

When Go to "TRANSPORT_TABLE" 140ms

And Show all transport "true" 076ms

Then Verify that transport has "1" CMR file 1s 180ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR documents are added to transport after creation

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 055ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 254ms

When Go to "TRANSPORT_TABLE" 109ms

And Show all transport "true" 066ms

Then Verify that transport has "2" CMR file 1s 184ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 042ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 262ms

When Go to "TRANSPORT_TABLE" 129ms

And Show all transport "true" 073ms

Then Verify that "CMR" document can be downloaded 17s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 061ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded in archive

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 128ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 246ms

And Show all transport "true" 069ms

And Delete transport 17s 180ms

When Go to "ARCHIVE_TAB" 253ms

And Show "TRANSPORT_ORDER" 049ms

Then Verify that "CMR" document can be downloaded 16s 836ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Transport files

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline The link to the delivery document appears after confirming the respective status [A-6905]

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 2s 576ms

And Create default accepted mode of transportation by API with "pba1-carrier" 475ms

And If user is login then logout 109ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 345ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 235ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 116ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 009ms

And Click button advice in transport table "LOAD_PL" 1s 837ms

And Set advice window in schedule 2s 803ms

And Fill advice form 9s 279ms

And Click advice save button and wait for advice form to disappear 30s 852ms

And Find transport in table with status "advice-added" 3s 371ms

When Confirm statuses until reach "on-the-way" 9s 344ms

Then Verify that "delivery_document" document can be downloaded 16s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.deleteModeOfTransportationAfterTest() 074ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 382ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 388ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 249ms

And Click pencil and move transport to next day in schedule 16s 404ms

Then Check if transport is in new location in schedule 2s 119ms

And Check if dates in transport form are correct 3s 481ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 150ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 342ms

And Show all transport "false" 011ms

When Find transport pencil button in transports table 1s 252ms

And Click pencil and move transport to next day in schedule 16s 779ms

Then Check if transport is in new location in schedule 2s 139ms

And Check if dates in transport form are correct 3s 315ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 107ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 305ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 214ms

And Click pencil and move transport to next day in schedule 16s 867ms

Then Check if transport is in new location in schedule 2s 131ms

And Check if dates in transport form are correct 3s 355ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 169ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 386ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 261ms

And Click pencil and move transport to next day in schedule 16s 360ms

Then Check if transport is in new location in schedule 2s 122ms

And Check if dates in transport form are correct 3s 342ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 097ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 330ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 293ms

And Click pencil and move transport to next day in schedule 16s 356ms

Then Check if transport is in new location in schedule 2s 108ms

And Check if dates in transport form are correct 3s 381ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 146ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 395ms

And Show all transport "true" 079ms

When Find transport pencil button in transports table 1s 258ms

And Click pencil and move transport to next day in schedule 16s 475ms

Then Check if transport is in new location in schedule 2s 137ms

And Check if dates in transport form are correct 3s 423ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 208ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 204ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 046ms

And Click button advice in transport table "DELIVERY" 134ms

And Set advice window in schedule 2s 558ms

And Fill advice form 8s 400ms

And Click advice save button and wait for advice form to disappear 30s 734ms

And Go to "TRANSPORT_TABLE" 237ms

And Find transport pencil button in transports table 1s 241ms

And Click pencil and move transport to next day in schedule 17s 558ms

Then Check if transport is in new location in schedule 2s 129ms

And Check if dates in transport form are correct 3s 471ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 417ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 398ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 244ms

And Click pencil and move transport to next day in schedule 16s 316ms

And Move advice window "3" 1s 325ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 132ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 357ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 255ms

And Click pencil and move transport to next day in schedule 16s 701ms

And Move advice window "3" 1s 380ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 038ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 274ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 241ms

And Click pencil and move transport to next day in schedule 16s 786ms

And Move advice window "3" 1s 420ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 172ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 335ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 270ms

And Click pencil and move transport to next day in schedule 16s 336ms

And Move advice window "3" 1s 333ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 184ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 352ms

And Show all transport "false" 008ms

When Find transport pencil button in transports table 1s 228ms

And Click pencil and move transport to next day in schedule 16s 375ms

And Move advice window "3" 1s 331ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 168ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 307ms

And Show all transport "true" 080ms

When Find transport pencil button in transports table 1s 244ms

And Click pencil and move transport to next day in schedule 16s 458ms

And Move advice window "3" 1s 370ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report custom fields are visible in proper section

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 444ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 415ms

And Go to transport details "DELIVERY" 4s 759ms

When Open section: "discrepancy-report-panel" 1s 076ms

Then Verify that no discrepancies found label is visible in discrepancy report section 072ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 449ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 118ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section will open with validation errors

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 302ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 410ms

And Go to transport details "DELIVERY" 4s 749ms

And Fill transport form 35s 977ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 175ms

When Go to transport details "DELIVERY" 4s 463ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 455ms

And Click "save-transport" save button 728ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 033ms

And Verify that discrepancy report section contains validation errors 019ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 424ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 392ms

When Go to transport details "DELIVERY" 4s 744ms

Then Verify that discrepancy report section is available 042ms

And Open section: "discrepancy-report-panel" 1s 069ms

And Verify that generate new discrepancy report button is visible 038ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 291ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 330ms

When Go to transport details "OWN_COLLECTION" 4s 673ms

Then Verify that discrepancy report section is available 042ms

And Open section: "discrepancy-report-panel" 1s 063ms

And Verify that generate new discrepancy report button is visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 418ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 388ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 546ms

Then Verify that discrepancy report section is available 032ms

And Open section: "discrepancy-report-panel" 1s 055ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 262ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 382ms

When Go to transport details "EXPORT" 5s 049ms

Then Verify that discrepancy report section is available 034ms

And Open section: "discrepancy-report-panel" 1s 065ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 352ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 156ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 681ms

Then Verify that discrepancy report section is available 033ms

And Open section: "discrepancy-report-panel" 1s 063ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 266ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 299ms

When Go to transport details "CISTERN_DELIVERY" 4s 450ms

Then Verify that discrepancy report section is not available 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 532ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 339ms

When Go to transport details "CISTERN_COLLECTION" 4s 467ms

Then Verify that discrepancy report section is not available 15s 024ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 396ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 226ms

When Go to transport details "WEIGHING" 4s 413ms

Then Verify that discrepancy report section is not available 15s 055ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report is properly generated

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 469ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 415ms

When Go to "TRANSPORT_TABLE" 137ms

And Go to transport details "DELIVERY" 4s 754ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 548ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 326ms

And Open section: "discrepancy-report-panel" 1s 071ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 36s 039ms

And Fill discrepancy report section without closing the form 19s 675ms

And Generate discrepancy report 16s 747ms

And Download discrepancy report 158ms

Then Verify that discrepancy report file has correct values 15s 137ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/40_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:250)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 130ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if edited discrepancy report is properly generated

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 411ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 392ms

When Go to "TRANSPORT_TABLE" 156ms

And Go to transport details "DELIVERY" 4s 728ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 36s 104ms

And Open section: "discrepancy-report-panel" 1s 072ms

And Fill discrepancy report section without closing the form 19s 677ms

And Generate discrepancy report 16s 250ms

And Download discrepancy report 145ms

And Verify that discrepancy report file has correct values 15s 121ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/41_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:250)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:93)

And Fill edited discrepancy report section 000ms

And Generate edited discrepancy report 000ms

And Download discrepancy report 000ms

Then Verify that discrepancy report file has correct values 000ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if added step is saved with transport

Steps

Given Set token of apiUsername "super-admin-piast" 088ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 053ms

And Get "LOAD" settings from "piast" 030ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 080ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 180ms

And Login as "piast-admin" 1s 857ms

And Go to "TRANSPORT_TABLE" 200ms

When Go to transport details "LOAD" 4s 706ms

And Add step "unload" 120ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 522ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 510ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 597ms

And Go to transport details "LOAD" 4s 638ms

And Verify that transport has "3" steps 024ms

Hooks

After Hooks.rollbackTransportTypeSettings() 067ms

After Hooks.rollbackAddedActionAuthorities() 049ms

After Hooks.deleteTransportAfterTest() 085ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if supplier can't edit time range for load and unload step

Steps

Given Login as "pskza1-carrier-2@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 149ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 225ms

When Go to "TRANSPORT_TABLE" 157ms

And Go to transport details "SMALLS_IMPORT" 17s 122ms

Then Verify that user can't edit time range for load and unload 15s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Steps

Given Set token of apiUsername "super-admin-neuca" 093ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 412ms

And Login as "neuca-admin" 918ms

And Go to "TRANSPORT_TABLE" 197ms

And Show all transport types 15s 051ms

When Go to transport details "DELIVERY" 32s 549ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 073ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Steps

Given Set token of apiUsername "super-admin-hochland" 093ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 386ms

And Login as "hochland-admin" 1s 496ms

And Go to "TRANSPORT_TABLE" 140ms

And Show all transport types 1s 053ms

When Go to transport details "EXPORT" 5s 647ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 067ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

Steps

Given Set token of apiUsername "super-admin-neuca" 094ms

And Get "DELIVERY" settings from "neuca" 041ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 104ms

And Login as "neuca-admin" 920ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 367ms

When Go to "TRANSPORT_TABLE" 245ms

And Go to transport details "DELIVERY" 32s 456ms

And Set number of pallets in "load" step in transport - "32" 130ms

And Check if number of pallets check message is not visible in transport form 15s 032ms

And Set number of pallets in "load" step in transport - "34" 124ms

Then Check if number of pallets check message is visible in transport form 043ms

Hooks

After Hooks.rollbackTransportTypeSettings() 099ms

After Hooks.deleteTransportAfterTest() 103ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if time range fields are required in new warehouse step

Steps

Given Set token of apiUsername "super-admin-farmacol" 088ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 056ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 049ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 073ms

And Login as "farmacol-admin" 2s 309ms

And Go to new transport "EXTERNAL_DELIVERY" 291ms

And Add step "unload" 090ms

And Click "save-transport-and-close" save button 696ms

Then Verify that "time-range-from-date-2" has validation error 1s 029ms

Then Verify that "time-range-to-date-2" has validation error 1s 030ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 323ms

And Click "save-transport-and-close" save button 708ms

And Verify that "time-range-from-date-2" has no validation error 018ms

And Verify that "time-range-to-date-2" has no validation error 017ms

Hooks

After Hooks.rollbackTransportTypeSettings() 069ms

After Hooks.rollbackAddedActionAuthorities() 044ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if new step is added in proper column in transport form

Steps

Given Set token of apiUsername "super-admin-piast" 094ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 058ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 222ms

When Login as "piast-admin" 2s 025ms

And Go to transport details "LOAD" 4s 826ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 124ms

And Fill step data 15s 036ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 125ms

And Fill step data 5s 497ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 615ms

Then Go to transport details "LOAD" 4s 574ms

And Check if "unload" step is added as "3" step in transport form 044ms

And Check if "load" step is added as "4" step in transport form 033ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 054ms

After Hooks.deleteTransportAfterTest() 058ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackRemovedActionAuthorities

Scenario Outline Check if step is draggable according to authority @A-6865

Steps

Given Set token of apiUsername "super-admin-skz" 093ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 052ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 008ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 202ms

When Login as "super-admin-skz" 2s 249ms

And Go to transport details "SMALLS_EXPORT" 4s 508ms

And Check if step is draggable "LOAD" 030ms

And Check if step is not draggable "UNLOAD" 024ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 053ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 084ms

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

Steps

Given Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 003ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 162ms

When Go to new transport "SMALLS_IMPORT" 385ms

And Fill transport form 19s 847ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 646ms

And Show all transport "false" 010ms

And Go to transport details "SMALLS_IMPORT" 4s 433ms

And Click create similar button 15s 199ms

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 15s 626ms

And Open similar transport details 253ms

Then Check are transport values equals 2s 129ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 089ms

After Hooks.deleteTransportAfterTest() 078ms

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

Steps

Given Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 005ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 014ms

When Go to new transport "TRANSPORT_ORDER" 418ms

And Fill transport form 23s 923ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 662ms

And Show all transport "true" 094ms

And Go to transport details "TRANSPORT_ORDER" 4s 432ms

And Click create similar button 15s 206ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT_ORDER" by "super-admin-alrec" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Open similar transport details 260ms

Then Check are transport values equals 2s 170ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 109ms

After Hooks.deleteTransportAfterTest() 082ms

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

Steps

Given Set "transport" inputs from JSON file "CREATE_TRANSPORT" "super-admin-adama" 003ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 122ms

When Go to new transport "TRANSPORT" 397ms

And Fill transport form 26s 770ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 607ms

And Show all transport "false" 011ms

And Go to transport details "TRANSPORT" 4s 448ms

And Click create similar button 15s 202ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT" by "super-admin-adama" 1s 357ms

And Click "save-transport-and-close" save button and wait for form to disappear 10s 143ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@type='submit' and @data-field-name='save-transport-and-close'] (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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.WlZsks}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 5ed07908611229654e6c0bce3e9f1a79
	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:198)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/Transport/TransportForm/TransportForm.feature:14)

And Open similar transport details 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 096ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 005ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 2s 633ms

When Go to new transport "DELIVERY" 15s 317ms

And Fill transport form 36s 042ms

And Click "save-transport" save button and wait for form to disappear 15s 748ms

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 805ms

And Go to "TRANSPORT_TABLE" 222ms

And Go to transport details "DELIVERY" 32s 384ms

And Click create similar button 15s 175ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 527ms

And Click "save-transport" save button and wait for form to disappear 15s 627ms

And Set advice window in schedule in "2" days 4s 226ms

And Go to "TRANSPORT_TABLE" 201ms

And Open similar transport details 553ms

Then Check are transport values equals 23s 462ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 158ms

After Hooks.deleteTransportAfterTest() 125ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-adama" 005ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 150ms

When Go to new transport "DELIVERY" 309ms

And Fill transport form 15s 563ms

And Click "save-transport" save button and wait for form to disappear 15s 598ms

And Set advice window in schedule 2s 174ms

And Check is transport created in schedule and set transport id 498ms

And Go to "TRANSPORT_TABLE" 246ms

And Go to transport details "DELIVERY" 4s 342ms

And Click create similar button 15s 189ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "super-admin-adama" 10s 892ms

And Click "save-transport" save button and wait for form to disappear 15s 604ms

And Set advice window in schedule in "2" days 4s 191ms

And Go to "TRANSPORT_TABLE" 171ms

And Open similar transport details 366ms

Then Check are transport values equals 199ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 082ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct carrier

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" 1s 064ms

When Go to new transport "DELIVERY" 15s 269ms

And Fill transport form 35s 946ms

And Click "save-transport" save button and wait for form to disappear 15s 612ms

And Set advice window in schedule 2s 156ms

And Check is transport created in schedule and set transport id 717ms

And Go to "TRANSPORT_TABLE" 210ms

And Go to transport details "DELIVERY" 32s 371ms

And Click create similar button 15s 189ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 533ms

And Click "save-transport" save button and wait for form to disappear 15s 600ms

And Set advice window in schedule in "2" days 4s 236ms

And Go to "TRANSPORT_TABLE" 221ms

And Open similar transport details 530ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 018ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 104ms

After Hooks.deleteTransportAfterTest() 111ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible to show transport details print form

Steps

Given Get inputs from database "CREATE_SMALLS_IMPORT_FOR_PRINT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 230ms

When Go to new transport "SMALLS_IMPORT" 417ms

And Fill transport form 33s 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 609ms

And Go to transport details "SMALLS_IMPORT" 4s 418ms

And Go to transport print details form 3s 107ms

Then Check are transport values equals 8s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 404ms

And Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 002ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 238ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 146ms

And Go to transport details "SMALLS_IMPORT" 4s 485ms

Then Verify that the transport can be edited 1s 325ms

And Close transport details 15s 163ms

And If user is login then logout 123ms

And Login as "pskza1-carrier@qa.qa-test" 1s 223ms

And Go to transport details "SMALLS_IMPORT" 4s 493ms

And Verify that the transport cannot be edited 46s 356ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 282ms

And Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 248ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 110ms

And Go to transport details "SMALLS_EXPORT" 4s 511ms

Then Verify that the transport can be edited 1s 326ms

And Close transport details 15s 109ms

And If user is login then logout 118ms

And Login as "pskza1-carrier@qa.qa-test" 1s 257ms

And Go to transport details "SMALLS_EXPORT" 4s 475ms

And Verify that the transport cannot be edited 46s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 144ms

And Get inputs from database "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 003ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 293ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 118ms

And Go to transport details "SMALLS_IMPORT" 4s 455ms

Then Verify that the hidden data in transport are not visible 1s 051ms

And Close transport details 15s 123ms

And If user is login then logout 106ms

And Login as "swisskrono-admin" 1s 408ms

And Go to transport details "SMALLS_IMPORT" 4s 516ms

And Verify that the hidden data in transport are visible 1s 264ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 098ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 221ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 099ms

And Go to transport details "SMALLS_EXPORT" 4s 466ms

Then Verify that the hidden data in transport are not visible 1s 043ms

And Close transport details 15s 117ms

And If user is login then logout 111ms

And Login as "swisskrono-admin" 1s 604ms

And Go to transport details "SMALLS_EXPORT" 4s 533ms

And Verify that the hidden data in transport are visible 1s 249ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 440ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 434ms

When Go to transport details "DELIVERY" 4s 735ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 323ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 523ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 501ms

And Fill discrepancy report section without closing the form 19s 626ms

And Click "save-transport" save button 1s 229ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 582ms

And Check if transport details form is disappeared 15s 010ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can add description to transport

Steps

Given Set token of apiUsername "super-admin-hochland" 090ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 049ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 242ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 396ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 3s 644ms

When Go to "TRANSPORT_TABLE" 208ms

And Go to transport details "DELIVERY" 4s 693ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 334ms

Then Verify that "transport-description" in transport has value "opis" 026ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 059ms

After Hooks.rollbackWarehousesAccess() 128ms

After Hooks.deleteTransportAfterTest() 105ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can't add description to transport

Steps

Given Set token of apiUsername "super-admin-hochland" 094ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 358ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 069ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 123ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 650ms

When Go to "TRANSPORT_TABLE" 170ms

And Go to transport details "DELIVERY" 4s 666ms

Then Verify that "transport-description" in transport form is disabled 030ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 064ms

After Hooks.rollbackWarehousesAccess() 154ms

After Hooks.deleteTransportAfterTest() 098ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 093ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 364ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 848ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 203ms

And Go to transport details "DELIVERY" 4s 710ms

Then Verify that "CARRIER" in transport form is visible 042ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 049ms

After Hooks.deleteTransportAfterTest() 099ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 091ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 067ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 240ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 886ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 180ms

And Go to transport details "TRANSPORT" 4s 484ms

Then Verify that "CARRIER" in transport form is visible 036ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 057ms

After Hooks.deleteTransportAfterTest() 074ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 092ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 060ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 247ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 909ms

And Show all transport "true" 064ms

When Go to "TRANSPORT_TABLE" 110ms

And Go to transport details "TRANSPORT_ORDER" 4s 435ms

Then Verify that "CARRIER" in transport form is visible 037ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 050ms

After Hooks.deleteTransportAfterTest() 079ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 089ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 363ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 488ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 187ms

And Go to transport details "DELIVERY" 4s 699ms

Then Verify that "CARRIER" in transport form is not visible 15s 057ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 066ms

After Hooks.deleteTransportAfterTest() 100ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 092ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 165ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 880ms

And Show all transport "false" 006ms

When Go to "TRANSPORT_TABLE" 239ms

And Go to transport details "TRANSPORT" 4s 490ms

Then Verify that "CARRIER" in transport form is not visible 15s 024ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 059ms

After Hooks.deleteTransportAfterTest() 080ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 093ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 240ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 969ms

And Show all transport "true" 069ms

When Go to "TRANSPORT_TABLE" 114ms

And Go to transport details "TRANSPORT_ORDER" 4s 468ms

Then Verify that "CARRIER" in transport form is not visible 15s 008ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 053ms

After Hooks.deleteTransportAfterTest() 070ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 105ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 054ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 041ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 330ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 484ms

And Show all transport "false" 006ms

When Go to "TRANSPORT_TABLE" 205ms

And Go to transport details "DELIVERY" 4s 748ms

Then Verify that "CARRIER" in transport form is not disabled 030ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 108ms

After Hooks.deleteTransportAfterTest() 122ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 092ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 206ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 808ms

And Show all transport "false" 006ms

When Go to "TRANSPORT_TABLE" 167ms

And Go to transport details "TRANSPORT" 4s 488ms

Then Verify that "CARRIER" in transport form is not disabled 027ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 097ms

After Hooks.deleteTransportAfterTest() 078ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 093ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 058ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 048ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 214ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 792ms

And Show all transport "true" 066ms

When Go to "TRANSPORT_TABLE" 100ms

And Go to transport details "TRANSPORT_ORDER" 4s 463ms

Then Verify that "CARRIER" in transport form is not disabled 026ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 091ms

After Hooks.deleteTransportAfterTest() 062ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 089ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 044ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 048ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 359ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 340ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 231ms

And Go to transport details "DELIVERY" 4s 712ms

Then Verify that "CARRIER" in transport form is disabled 029ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 058ms

After Hooks.rollbackRemovedActionAuthorities() 059ms

After Hooks.deleteTransportAfterTest() 111ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 092ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 009ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 227ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 059ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 181ms

And Go to transport details "TRANSPORT" 4s 476ms

Then Verify that "CARRIER" in transport form is disabled 029ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 047ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 064ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 091ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 058ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 005ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 184ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 840ms

And Show all transport "true" 063ms

When Go to "TRANSPORT_TABLE" 099ms

And Go to transport details "TRANSPORT_ORDER" 4s 463ms

Then Verify that "CARRIER" in transport form is disabled 030ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 054ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 076ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can add description to archived transport

Steps

Given Set token of apiUsername "super-admin-adama" 096ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 229ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 058ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 055ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 060ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 736ms

When Find transport in table with status "planned" 3s 339ms

And Confirm statuses until reach "process-ended" 21s 568ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 272ms

And Show "DELIVERY" 082ms

And Go to transport details "DELIVERY" 32s 422ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 355ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 623ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 307ms

Then Verify that "transport-description" in transport has value "opis" 029ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 058ms

After Hooks.rollbackRemovedActionAuthorities() 106ms

After Hooks.deleteTransportAfterTest() 079ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 209ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 419ms

When Go to transport details "DELIVERY" 4s 578ms

And Fill transport form 36s 046ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 384ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 155ms

And Go to new transport "DELIVERY" 315ms

Then Verify that driver "XXX ZZZ" is in list 642ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 240ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 264ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 196ms

And If user is login then logout 108ms

And Login as "pskza1-carrier@qa.qa-test" 1s 192ms

Then Verify that the transport has been transferred 1s 143ms

And Accept or reject "accept" transferred transport 15s 765ms

And Go to transport details "SMALLS_IMPORT" 4s 506ms

And Verify that "transaction-price" in transport form is visible 041ms

And Verify that transaction price field has correct value 020ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 041ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 278ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 285ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 213ms

And If user is login then logout 106ms

And Login as "pskza1-carrier@qa.qa-test" 1s 171ms

Then Verify that the transport has been transferred 1s 122ms

And Accept or reject "accept" transferred transport 15s 783ms

And Go to transport details "SMALLS_EXPORT" 4s 544ms

And Verify that "transaction-price" in transport form is visible 044ms

And Verify that transaction price field has correct value 039ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport details button is not shown

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 1s 816ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 301ms

And Show all transport types 1s 050ms

Then Check if transport number is visible "DELIVERY" 15s 067ms

And Check if transport details is not visible 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 785ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 112ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 423ms

When Click on transport row 079ms

Then Verify if transport row is selected 038ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 883ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 174ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 331ms

When Click on transport row 1s 745ms

Then Verify if transport row is selected 018ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 763ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 101ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 300ms

When Click on transport row 062ms

Then Verify if transport row is selected 032ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 795ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 107ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 297ms

When Click on transport row 063ms

Then Verify if transport row is selected 020ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 920ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 105ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 304ms

When Click on transport row 063ms

Then Verify if transport row is selected 019ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 832ms

And Show all transport "true" 073ms

And Go to "TRANSPORT_TABLE" 119ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 307ms

When Click on transport row 058ms

Then Verify if transport row is selected 028ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 14s 048ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 220ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 080ms

When Accept or reject "accept" transferred transport 17s 677ms

Then Verify that transport is accept or reject "accept" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 140ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 067ms

When Accept or reject "reject" transferred transport 17s 650ms

Then Verify that transport is accept or reject "reject" 15s 071ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 284ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 195ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 067ms

When Accept or reject "accept" transferred transport 18s 080ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 037ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 236ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 076ms

When Accept or reject "reject" transferred transport 17s 956ms

Then Verify that transport is accept or reject "reject" 15s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 155ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 232ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 074ms

When Accept or reject "accept" transferred transport 18s 063ms

Then Verify that transport is accept or reject "accept" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 134ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 231ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 075ms

When Accept or reject "reject" transferred transport 18s 048ms

Then Verify that transport is accept or reject "reject" 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 123ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 208ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 188ms

And If user is login then logout 094ms

And Login as "paa1-carrier@qa.qa-test" 1s 198ms

Then Verify that the transport has been transferred with "true" 1s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 038ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 273ms

And If user is login then logout 120ms

And Login as "paa1-carrier@qa.qa-test" 1s 224ms

Then Verify that the transport has been transferred with "false" 1s 186ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 966ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 216ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 202ms

And If user is login then logout 098ms

And Login as "pskza1-carrier@qa.qa-test" 1s 155ms

Then Verify that the transport has been transferred 1s 115ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 355ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 187ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 186ms

And If user is login then logout 126ms

And Login as "pskza1-carrier@qa.qa-test" 1s 225ms

Then Verify that the transport has been transferred 1s 137ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier during auction

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 034ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 209ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 140ms

And Go to auction offer 1s 201ms

When Offer "1000" 139ms

And Verify that offer with "1000" has been added to auction 3s 040ms

And If user is login then logout 078ms

And Login as "swisskrono-admin" 1s 227ms

Then Go to auction details 1s 203ms

And Pass transport to carrier from auction details 1s 266ms

And If user is login then logout 612ms

And Login as "pskza1-carrier@qa.qa-test" 1s 184ms

And Verify that the transport has been transferred 1s 139ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier when auction is finished

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 053ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 222ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 098ms

And Go to auction offer 1s 197ms

When Offer "1000" 142ms

And Verify that offer with "1000" has been added to auction 3s 044ms

And Wait till auction end 1m 54s 017ms

And If user is login then logout 131ms

Then Login as "swisskrono-admin" 1s 515ms

And Go to auction details 1s 209ms

And Pass transport to carrier from auction details 1s 257ms

And If user is login then logout 412ms

And Login as "pskza1-carrier@qa.qa-test" 1s 175ms

And Verify that the transport has been transferred 1s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if enabled carriers are shown in transport transfer select

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 143ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 242ms

And Go to "TRANSPORT_TABLE" 129ms

When Open transport transfer modal 1s 239ms

Then Verify that all enabled companies from "swisskrono" are shown in select 128ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest @rollbackRejectedSections

Scenario Outline Check if blocked carriers are shown as disabled in transport transfer select

Steps

Given Set token of apiUsername "super-admin-adama" 099ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 400ms

And Login as "adama-admin" 974ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 229ms

And Go to "TRANSPORT_TABLE" 115ms

When Open transport transfer modal 1s 258ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 099ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackRejectedSections() 101ms

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]

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 014ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 227ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 173ms

And If user is login then logout 100ms

When Login as "paa1-carrier@qa.qa-test" 2s 822ms

And Verify that the transport has been transferred with "true" 1s 189ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 034ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Assortment Group

@deleteTransportAfterTest

Scenario Outline Check if assortment group select is disabled when transport is during edition

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 072ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 367ms

When Go to "TRANSPORT_TABLE" 123ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 351ms

Then Check if new assortment group is disabled in transport form 031ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to advice transport after double cancellation.

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 042ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 185ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 003ms

When Show all transport types 1s 047ms

And Click button advice in transport table "CONTAINER" 124ms

And Set advice window in schedule 2s 378ms

And Click button cancel in advice form 15s 337ms

And Set advice window in schedule 2s 164ms

And Click button cancel in advice form 15s 307ms

And Set advice window in schedule 2s 132ms

And Fill advice form 15s 973ms

And Click advice save button and wait for advice form to disappear 30s 672ms

And Go to "TRANSPORT_TABLE" 161ms

And Go to transport details "CONTAINER" 4s 418ms

Then Check are advice values equals 2s 387ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer and retransfer transport to carrier

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 168ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 002ms

When Go to new transport "TRANSPORT" 443ms

And Fill transport form 26s 817ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 640ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 203ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 114ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 119ms

And Accept or reject "reject" transferred transport 15s 827ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 138ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 277ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 023ms

And Accept or reject "accept" transferred transport 15s 886ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

Scenario Outline Check if possible to edit transport after advice cancellation.

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 097ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 002ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 194ms

When Show all transport types 1s 039ms

And Click button advice in transport table "DELIVERY" 126ms

And Set advice window in schedule 2s 641ms

And Click button cancel in advice form 15s 389ms

And Go to "TRANSPORT_TABLE" 223ms

When Go to transport details "DELIVERY" 4s 518ms

And Fill transport form 1m 2s 447ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 637ms

And Go to transport details "DELIVERY" 4s 417ms

Then Check are transport values equals 099ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu CARRIER są niepoprawne, wartość na stronie: Przewoźnik Piast Automat 1 wartość poprawna: Przewoźnik Piast Automat 2 expected:<...oźnik Piast Automat [2]> but was:<...oźnik Piast Automat [1]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:122)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:261)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Scenario/TransportTransfer.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 079ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3469	15	21	0	0	3505	371	15	386	5h 19m 41s 155ms	Failed

Tag Report