Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	master.299	05 lut 2021, 14:43

	Steps	Scenarios	Features
@deleteTransportAfterTest	3304	56	144	0	0	3504	324	56	380	5h 8m 15s 242ms	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" 4s 093ms

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

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

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

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

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

And Fill advice form 16s 297ms

And Click advice save button to check error message 092ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 414ms

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

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

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

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

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

And Fill advice form 8s 495ms

And Click advice save button to check error message 094ms

Then Check if possible advice alert is displayed 021ms

Hooks

After Hooks.deleteTransportAfterTest() 159ms

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

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

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

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

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

And Fill advice form 8s 546ms

And Click advice save button to check error message 104ms

Then Check if possible advice alert is displayed 028ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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

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

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

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

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

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

And Fill advice form 13s 356ms

And Click advice save button to check error message 098ms

Then Check if possible advice alert is displayed 027ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

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

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

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

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

And Fill advice form 13s 350ms

And Click advice save button to check error message 085ms

Then Check if possible advice alert is displayed 025ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 165ms

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

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

And Fill transport form 4s 748ms

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

And Expand advice panel 115ms

And Edit advice in transport details 12s 554ms

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

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

And Expand advice panel 115ms

Then Check are advice values equals after edition 253ms

Hooks

After Hooks.deleteTransportAfterTest() 154ms

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

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

And Show all transport types 1s 047ms

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

And Go to "TRANSPORT_TABLE" 231ms

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

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

And Fill transport form 1m 2s 709ms

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

And Expand advice panel 088ms

And Edit advice in transport details 6s 744ms

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

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

And Expand advice panel 113ms

Then Check are advice values equals after edition 109ms

Hooks

After Hooks.deleteTransportAfterTest() 180ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 185ms

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

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

And Fill transport form 57s 710ms

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

And Expand advice panel 122ms

And Edit advice in transport details 6s 701ms

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

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

And Expand advice panel 104ms

Then Check are advice values equals after edition 109ms

Hooks

After Hooks.deleteTransportAfterTest() 199ms

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

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

And Show all transport types 1s 047ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

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

And Fill transport form 24s 794ms

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

And Expand advice panel 114ms

And Edit advice in transport details 18s 688ms

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

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

And Expand advice panel 114ms

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

Hooks

After Hooks.deleteTransportAfterTest() 173ms

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

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 177ms

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

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

And Fill transport form 24s 763ms

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

And Expand advice panel 118ms

And Edit advice in transport details 18s 634ms

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

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

And Expand advice panel 111ms

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

Hooks

After Hooks.deleteTransportAfterTest() 164ms

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

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

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

When Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 389ms

And Fill advice form 12s 533ms

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

And Go to "TRANSPORT_TABLE" 159ms

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

Then Check are advice values equals 344ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

When Show all transport types 1s 049ms

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

And Set advice window in schedule 6s 440ms

And Fill advice form 11s 941ms

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

And Go to "TRANSPORT_TABLE" 176ms

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

Then Check are advice values equals 2s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 165ms

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

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 617ms

And Fill advice form 8s 445ms

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

And Go to "TRANSPORT_TABLE" 213ms

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

Then Check are advice values equals 231ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 612ms

And Fill advice form 8s 458ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

Then Check are advice values equals 249ms

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

Steps

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

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 410ms

And Fill advice form 13s 240ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

Then Check are advice values equals 2s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

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

When Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 434ms

And Fill advice form 13s 220ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

Then Check are advice values equals 2s 320ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-neuca" 004ms

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

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

And Fill transport form 37s 676ms

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

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

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

Then Set advice window in schedule 2s 279ms

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

And Go to "TRANSPORT_TABLE" 208ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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

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

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

And Accept transferred transport by Api 501ms

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

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 389ms

And Fill advice form 11s 902ms

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

And Go to "TRANSPORT_TABLE" 228ms

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

Then Check are advice values equals 2s 297ms

Hooks

After Hooks.deleteTransportAfterTest() 171ms

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

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

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

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

And Accept transferred transport by Api 139ms

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

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

When Show all transport types 1s 056ms

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

And Set advice window in schedule 2s 624ms

And Fill advice form 14s 757ms

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

And Go to "TRANSPORT_TABLE" 189ms

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

Then Check are advice values equals 2s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 166ms

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

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

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

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

And Accept transferred transport by Api 116ms

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

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 649ms

And Fill advice form 14s 700ms

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

And Go to "TRANSPORT_TABLE" 181ms

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

Then Check are advice values equals 2s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

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

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

And Accept transferred transport by Api 111ms

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

When Show all transport types 1s 039ms

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

And Set week view 1s 549ms

And Show yesterday 1s 102ms

Then Check if advice restriction blockade windows are visible 020ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

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

And Accept transferred transport by Api 101ms

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

When Show all transport types 1s 038ms

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

And Set week view 2s 095ms

And Show yesterday 1s 114ms

Then Check if advice restriction blockade windows are visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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

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

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

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

And Accept transferred transport by Api 109ms

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

When Show all transport types 1s 042ms

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

And Set week view 2s 112ms

And Show yesterday 1s 107ms

Then Check if advice restriction blockade windows are visible 028ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

And Show all transport "false" 036ms

And Click on time window date 1s 288ms

And Select view "DAYS_4" 2s 054ms

And Move advice window "3" 1s 335ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 160ms

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

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

And Show all transport "false" 015ms

And Click on time window date 15s 801ms

And Select view "DAYS_4" 2s 071ms

And Move advice window "3" 1s 470ms

Then Check if advice window is in new location 030ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

And Show all transport "false" 018ms

And Click on time window date 15s 486ms

And Select view "DAYS_4" 2s 066ms

And Move advice window "3" 1s 410ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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

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

And Show all transport "false" 021ms

And Click on time window date 1s 448ms

And Select view "DAYS_4" 2s 060ms

And Move advice window "3" 1s 422ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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

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

And Show all transport "false" 017ms

And Click on time window date 1s 305ms

And Select view "DAYS_4" 2s 065ms

And Move advice window "3" 1s 312ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

And Show all transport "true" 088ms

And Click on time window date 1s 350ms

And Select view "DAYS_4" 2s 064ms

And Move advice window "3" 1s 342ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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

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

And Get "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 015ms

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 557ms

And Fill advice form 8s 485ms

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

And Go to "TRANSPORT_TABLE" 226ms

And Click on time window date 1s 411ms

And Select view "DAYS_4" 2s 056ms

And Move advice window "3" 1s 431ms

Then Check if advice window is in new location 032ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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

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

And Go to "TRANSPORT_TABLE" 087ms

And Show all transport types 1s 050ms

And Click on time window date 1s 304ms

And Scroll to time window "adviceWindow" 052ms

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

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

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:186)

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

And Go to "TRANSPORT_TABLE" 128ms

And Show all transport types 1s 045ms

And Click on time window date 1s 417ms

And Scroll to time window "adviceWindow" 045ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

And Go to "TRANSPORT_TABLE" 100ms

And Show all transport types 1s 043ms

And Click on time window date 1s 331ms

And Scroll to time window "adviceWindow" 048ms

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

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

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:186)

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

And Go to "TRANSPORT_TABLE" 228ms

And Show all transport types 15s 033ms

And Click on time window date 15s 809ms

And Scroll to time window "adviceWindow" 047ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 150ms

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

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

When Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 540ms

And Fill advice form 8s 432ms

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

And Go to "TRANSPORT_TABLE" 229ms

And Click on time window date 1s 425ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

And Go to "WAREHOUSE_TAB" 750ms

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

When Go to new transport "DELIVERY" 387ms

And Fill transport form 41s 668ms

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

And Click previous page button in browser 025ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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

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

And Go to "WAREHOUSE_TAB" 773ms

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

When Go to new transport "DELIVERY" 386ms

And Fill transport form 41s 636ms

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

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

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

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

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

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

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

When Show all transport types 1s 043ms

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

And Fill advice form 11s 656ms

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

When Find transport in table with status "no-advice-undefined" 1s 201ms

And Open statuses popup 098ms

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" 15s 028ms

Error message

org.junit.ComparisonFailure: Lista statusów jest niepoprawna expected:<[Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfTransportHasCheckpointsFromListInGroup(ConfirmStatuses.java:103)
	at ✽.Check if transport has checkpoints from list "Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta" in "1"(file:Features/Atom/Advice/AdviceTransport.feature:255)

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_DELIVERY_CONTRACTOR" "super-admin-neuca" 003ms

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

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

And Fill transport form 31s 084ms

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

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

And Set advice window in schedule 2s 223ms

And Check is transport created in schedule and set transport id 1s 134ms

Then Go to "OWN_COMPANY_TAB" 294ms

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_DELIVERY_SUPPLIER" "super-admin-alrec" 003ms

And Login as "daa1-supplier" and set token of apiUsername "super-admin-alrec" 31s 306ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: Nie udalo sie poprawnie zalogowac daa1-supplier (tried for 20 second(s) with 500 MILLISECONDS interval)
	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.checkElementIsVisible(BasePage.java:166)
	at Pages.LoginPage.loginAs(LoginPage.java:39)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:98)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:68)
	at ✽.Login as "daa1-supplier" and set token of apiUsername "super-admin-alrec"(file:Features/Atom/Companies/CompanyResources.feature:6)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //a[text()='Logout'] | //a[text()='Wyloguj']
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-128-generic', java.version: '1.8.0_201'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:166)
	at Pages.LoginPage.loginAs(LoginPage.java:39)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:98)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:68)
	at sun.reflect.GeneratedMethodAccessor207.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

And Go to new transport "DELIVERY" 000ms

And Fill transport form 000ms

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

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

And Set advice window in schedule 000ms

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

Then Go to "OWN_COMPANY_TAB" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 003ms

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

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

When Go to "TRANSPORT_TABLE" 115ms

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

And Show all transport types 1s 049ms

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

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

When Go to "TRANSPORT_TABLE" 107ms

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

And Show all transport types 1s 052ms

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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

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

When Go to "TRANSPORT_TABLE" 104ms

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

And Show all transport types 1s 045ms

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

When Go to "TRANSPORT_TABLE" 126ms

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

And Show all transport types 1s 046ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

And Delete created transport by API 090ms

When Go to "ARCHIVE_TAB" 200ms

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

And Show "SMALLS_IMPORT" 069ms

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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

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

And Delete created transport by API 090ms

When Go to "ARCHIVE_TAB" 194ms

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

And Show "SMALLS_IMPORT" 087ms

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

And Delete created transport by API 083ms

When Go to "ARCHIVE_TAB" 203ms

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

And Show "SMALLS_IMPORT" 075ms

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

Hooks

After Hooks.deleteTransportAfterTest() 154ms

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

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

And Delete created transport by API 111ms

When Go to "ARCHIVE_TAB" 198ms

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

And Show "SMALLS_IMPORT" 073ms

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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

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

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

And Go to "TRANSPORT_TABLE" 116ms

And Show all transport "true" 080ms

And Select transportType "TRANSPORT_ORDER" 1s 129ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

And Login as "neuca-admin" 3s 091ms

And Go to "TRANSPORT_TABLE" 211ms

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

And Toggle transport table days limit filter 088ms

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

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

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

When Go to "TRANSPORT_TABLE" 107ms

And Go to auction form 1s 342ms

And Select contractors group "Kraj" 082ms

Then Verify that carrier "PSKZA1" is selected 023ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.removeContractorsGroup() 053ms

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

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

When Go to "TRANSPORT_TABLE" 085ms

And Go to auction form 1s 209ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

When Go to "TRANSPORT_TABLE" 106ms

And Go to auction form 1s 221ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

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

And Show all transport "false" 017ms

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

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

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

And Expand index panel 119ms

And Click add index button 135ms

And Fill index form 10s 574ms

And Click ok button in index form 15s 137ms

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

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

And Expand index panel 120ms

Then Check are transport values equals 093ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.deleteProductAfterTest() 076ms

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

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

And Show all transport "true" 086ms

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

And Expand index panel 102ms

And Click add index button 032ms

Error message

org.openqa.selenium.ElementNotInteractableException: element not interactable: element has zero size
  (Session info: headless chrome=88.0.4324.146)
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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:83)
	at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openqa.selenium.support.pagefactory.internal.LocatingElementHandler.invoke(LocatingElementHandler.java:51)
	at com.sun.proxy.$Proxy24.click(Unknown Source)
	at CucumberTests.Index.IndexTest.clickAddIndexButton(IndexTest.java:42)
	at ✽.Click add index button(file:Features/Atom/Index/CrudIndex.feature:12)

And Fill index form 000ms

And Click ok button in index form 000ms

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

And Go to transport details "TRANSPORT_ORDER" 000ms

And Expand index panel 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.deleteProductAfterTest() 000ms

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

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

And Show all transport "false" 016ms

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

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

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

And Add index to transport 25s 971ms

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

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

And Expand index panel 117ms

And Click delete index button 064ms

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

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

And Expand index panel 101ms

Then Verify that transport has no indexes 15s 020ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.deleteProductAfterTest() 035ms

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

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

And Show all transport "true" 070ms

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

And Add index to transport 153ms

Error message

org.openqa.selenium.ElementNotInteractableException: element not interactable: element has zero size
  (Session info: headless chrome=88.0.4324.146)
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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:83)
	at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openqa.selenium.support.pagefactory.internal.LocatingElementHandler.invoke(LocatingElementHandler.java:51)
	at com.sun.proxy.$Proxy24.click(Unknown Source)
	at CucumberTests.Index.IndexTest.clickAddIndexButton(IndexTest.java:42)
	at CucumberTests.Index.IndexTest.addIndexToTransport(IndexTest.java:78)
	at ✽.Add index to transport(file:Features/Atom/Index/CrudIndex.feature:40)

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

When Go to transport details "TRANSPORT_ORDER" 000ms

And Expand index panel 000ms

And Click delete index button 000ms

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

And Go to transport details "TRANSPORT_ORDER" 000ms

And Expand index panel 000ms

Then Verify that transport has no indexes 000ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.deleteProductAfterTest() 000ms

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

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

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

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

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

And Add index to transport 24s 595ms

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

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

When Click on index details icon 100ms

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.deleteProductAfterTest() 035ms

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

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

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 474ms

And Fill advice form 11s 874ms

And Click advice save button and wait for advice form to disappear 31s 285ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 154ms

After Hooks.cleanUserDetailsAfterTest() 156ms

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

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 595ms

And Fill advice form 8s 475ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.cleanUserDetailsAfterTest() 175ms

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

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

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

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

And Set advice window in schedule 2s 398ms

And Fill advice form 13s 270ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.cleanUserDetailsAfterTest() 233ms

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

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

And Show all transport types 1s 035ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 30s 045ms

And Go to "TRANSPORT_TABLE" 168ms

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

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

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

And Fill transport form 4s 713ms

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

And Expand advice panel 112ms

And Edit advice in transport details 12s 430ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 135ms

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

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 224ms

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

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

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

And Fill transport form 1m 2s 527ms

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

And Expand advice panel 114ms

And Edit advice in transport details 6s 614ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

After Hooks.cleanUserDetailsAfterTest() 184ms

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

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

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

And Show all transport types 1s 048ms

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

And Go to "TRANSPORT_TABLE" 176ms

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

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

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

And Fill transport form 24s 749ms

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

And Expand advice panel 122ms

And Edit advice in transport details 18s 678ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 169ms

After Hooks.cleanUserDetailsAfterTest() 225ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wyjazd" 1m 2s 045ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 306ms

After Hooks.cleanUserDetailsAfterTest() 244ms

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

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

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

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

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

And Wait "120" seconds 2m 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 248ms

After Hooks.cleanUserDetailsAfterTest() 311ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 016ms

View Feature Advice Mail

@deleteTransportAfterTest @deleteUserAfterTest

Scenario Outline Check if mail was not sent to creator if user is not enabled

Steps

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

And Create and accept invitation by JSON file as "super-admin-skd" for "apolloautomattest@gmail.com" "CREATE_SQUARE_MANAGER_INVITATION" 1s 246ms

And Get invited user account data "apolloautomattest@gmail.com" 2s 678ms

And Prepare disabled user "test-1" details with all notifications and "apolloautomattest@gmail.com" by JSON file 001ms

Error message

java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:120)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getLongResult(ApolloSelectDbService.java:110)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findIdBy(ApolloSelectDbService.java:22)
	at CucumberTests.User.EditUserTest.prepareUserDetailsWithAllNotifications(EditUserTest.java:97)
	at CucumberTests.User.EditUserTest.prepareDisabledUserDetailsWithAllNotificationsAndByJSONFile(EditUserTest.java:93)
	at ✽.Prepare disabled user "test-1" details with all notifications and "apolloautomattest@gmail.com" by JSON file(file:Features/Atom/Mail/AdviceMail.feature:80)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 000ms

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

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

Then Check if user did not get an mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.deleteUserAfterTest() 156ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 188ms

After Hooks.cleanUserDetailsAfterTest() 210ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.cleanUserDetailsAfterTest() 482ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Steps

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

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

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

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

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

And Wait till auction end 1m 58s 031ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Dodano nową ofertę" 3m 21s 792ms

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: 
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:33)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AuctionMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 185ms

After Hooks.cleanUserDetailsAfterTest() 365ms

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

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

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

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

And Wait till auction end 1m 58s 021ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 176ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.cleanUserDetailsAfterTest() 200ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.cleanUserDetailsAfterTest() 170ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.cleanUserDetailsAfterTest() 186ms

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

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

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

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

And Wait "90" seconds 1m 30s

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 184ms

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

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

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

And Go to "TRANSPORT_TABLE" 100ms

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

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

And Fill transport form 36s 107ms

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

And Fill discrepancy report section 35s 853ms

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

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

And Generate discrepancy report 18s 794ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

After Hooks.cleanUserDetailsAfterTest() 356ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 782ms

And Select warehouse "Serownia" 1s 392ms

And Set week view 1s 101ms

And Show yesterday 1s 069ms

And Move window into the past 304ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "spóźnił się na" 3m 13s 126ms

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: 
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:33)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 199ms

After Hooks.cleanUserDetailsAfterTest() 343ms

After Hooks.rollbackAddedAuthorities() 058ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica import" 13s 242ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.cleanUserDetailsAfterTest() 233ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.cleanUserDetailsAfterTest() 258ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 185ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.cleanUserDetailsAfterTest() 200ms

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

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

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

And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 188ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.cleanUserDetailsAfterTest() 240ms

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

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

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

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

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

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

Then If user is login then logout 108ms

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

And Go to auction details 1s 205ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

After Hooks.cleanUserDetailsAfterTest() 272ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.cleanUserDetailsAfterTest() 261ms

View Feature Pallet limit

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-neuca" 003ms

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

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

And Fill transport form 37s 470ms

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

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

And Set advice window in schedule 2s 230ms

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

Hooks

After Hooks.deleteTransportAfterTest() 002ms

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

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

And Go to "TRANSPORT_TABLE" 220ms

And Show all transport "false" 008ms

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

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

And Click "save-transport" save button 711ms

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

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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

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

And Add transport by SKApi in "MGW" 257ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 45s 122ms

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

And Set advice window in schedule 2s 608ms

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

And Fill advice form 14s 847ms

And Click advice save button and wait for advice form to disappear 31s 284ms

And Find transport in table with status "planned" 1s 317ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 283ms

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" and set token of apiUsername "super-admin-skz" 1s 286ms

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 120ms

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

Then Check are transport values equals 415ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

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

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 086ms

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

Then Check are transport values equals 402ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" and set token of apiUsername "super-admin-skz" 1s 212ms

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 55s 030ms

And Go to "TRANSPORT_TABLE" 111ms

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

Then Check are transport values equals 401ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

When Add transport by SKApi in "HRL" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 48s 911ms

And Go to "TRANSPORT_TABLE" 105ms

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

Then Check are transport values equals 399ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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-10" and set token of apiUsername "super-admin-skz" 1s 221ms

When Add transport by SKApi in "HRL" 003ms

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

And Go to "TRANSPORT_TABLE" 106ms

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

Then Check are transport values equals 409ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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-10" and set token of apiUsername "super-admin-skz" 1s 208ms

When Add transport by SKApi in "HRL" 004ms

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

And Go to "TRANSPORT_TABLE" 093ms

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

Then Check are transport values equals 344ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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

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

And Set another client name "Pepsi" 001ms

When Add transport by SKApi in "MGW" 003ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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

When Add transport by SKApi in "" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 57s 336ms

And Go to "TRANSPORT_TABLE" 114ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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

And Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id 54s 436ms

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

And Set advice window in schedule 2s 761ms

And Fill advice form 14s 853ms

And Click advice save button and wait for advice form to disappear 31s 289ms

And Go to "TRANSPORT_TABLE" 196ms

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

Then Check are advice values equals 2s 341ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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 "CREATE_ADVICE" "super-admin-skz" 001ms

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

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

And Set advice window in schedule 2s 596ms

And Fill advice form 14s 758ms

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

And Go to "TRANSPORT_TABLE" 173ms

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

Then Check are advice values equals 2s 341ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

And Add transport by SKApi in "MGW" 004ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 141ms

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

And Set advice window in schedule 2s 528ms

And Fill advice form 14s 793ms

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

And Go to "TRANSPORT_TABLE" 232ms

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

Then Check are advice values equals 2s 343ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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 "CREATE_ADVICE" "super-admin-skz" 001ms

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

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

And Set advice window in schedule 2s 488ms

And Fill advice form 14s 765ms

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

And Go to "TRANSPORT_TABLE" 157ms

Then Check advice data in SK API database "OWN_COLLECTION" 4s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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

And Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id 6s 313ms

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

And Set advice window in schedule 2s 492ms

And Fill advice form 14s 718ms

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

And Go to "TRANSPORT_TABLE" 166ms

Then Check advice data in SK API database "CONTAINER" 3s 100ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id 6s 827ms

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

And Set advice window in schedule 2s 511ms

And Fill advice form 14s 814ms

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

And Go to "TRANSPORT_TABLE" 211ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 4s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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 6s 317ms

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

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

And Fill advice form 14s 782ms

And Click advice save button to check error message 086ms

Then Check if possible advice alert is displayed 023ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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 42s 488ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

And Expand advice panel 110ms

And Edit advice in transport details 14s 114ms

And Fill arrival date field 2s 283ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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

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

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

And Go to "TRANSPORT_TABLE" 167ms

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

And Expand advice panel 113ms

And Edit advice in transport details 14s 122ms

And Fill arrival date field 2s 286ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 30s 866ms

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

And Go to "TRANSPORT_TABLE" 236ms

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

And Expand advice panel 109ms

And Edit advice in transport details 14s 107ms

And Fill arrival date field 2s 304ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature sms

@deleteTransportAfterTest

Scenario Outline Check if sms was sent to driver after confirm status

Steps

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

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

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

And Set driver phone number "48" "789440109" 453ms

When Find transport in table with status "created" 1s 206ms

And Confirm statuses until reach "driver-called" 10s 272ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "driver-called"(file:Features/Atom/SMS/sms.feature:11)

And Wait "20" seconds 000ms

Then Check if sms was sent to driver after confirm status "logintegra-imperial-test" "Argetnigol.7890" "Kierowco, prosimy o podjazd pod rampe numer" 000ms

And Wait "10" seconds 000ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 796ms

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

And Select view "DAYS_2" 2s 090ms

Then Check if gray window is in the schedule 2s

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

And Select view "DAYS_2" 2s 055ms

And Check if gray window is in the schedule 2s

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 190ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 748ms

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

And Select view "DAYS_2" 2s 066ms

Then Check if gray window is in the schedule 2s

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

And Select view "DAYS_2" 2s 059ms

And Check if gray window is in the schedule 2s

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 184ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 730ms

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

And Select view "DAYS_2" 2s 081ms

Then Check if gray window is in the schedule 2s

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

And Select view "DAYS_2" 2s 055ms

And Check if gray window is in the schedule 2s

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 159ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 448ms

And Select warehouse "MGW" 1s 198ms

And Select view "DAYS_2" 2s 080ms

Then Check if gray window is in the schedule 2s

And Select warehouse "HRL" 1s 391ms

And Select view "DAYS_2" 2s 056ms

And Check if gray window is in the schedule 2s

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 135ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

When Go to "WAREHOUSE_TAB" 377ms

And Select warehouse "MGW" 1s 317ms

And Select view "DAYS_2" 2s 071ms

Then Check if gray window is in the schedule 2s

And Select warehouse "HRL" 1s 234ms

And Select view "DAYS_2" 2s 054ms

And Check if gray window is in the schedule 2s

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 192ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if windows are visible after switching warehouse

Steps

Given Login as "3cargo-carrier" and set token of apiUsername "super-admin-skz" 2s 535ms

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

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

When Go to "WAREHOUSE_TAB" 411ms

And Select warehouse "MGW" 1s 347ms

And Select view "DAYS_2" 2s 074ms

Then Check if gray window is in the schedule 2s

And Select warehouse "HRL" 1s 306ms

And Select view "DAYS_2" 2s 054ms

And Check if gray window is in the schedule 2s

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 165ms

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

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

When Find transport in table with status "advice-added" 1s 207ms

And Confirm statuses until reach "process-ended" 10s 306ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

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

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

When Find transport in table with status "planned" 15s 169ms

And Confirm statuses until reach "process-ended" 10s 344ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

When Find transport in table with status "planned" 1s 186ms

And Confirm statuses until reach "process-ended" 10s 277ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

When Find transport in table with status "planned" 15s 210ms

And Confirm statuses until reach "departed" 10s 350ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "departed"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

Then Check if transport has "departed" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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

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

When Find transport in table with status "created" 1s 202ms

And Confirm statuses until reach "process-ended" 10s 286ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

When Find transport in table with status "created" 1s 183ms

And Confirm statuses until reach "process-ended" 10s 311ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

When Find transport in table with status "planned" 1s 180ms

And Confirm statuses until reach "process-ended" 10s 297ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 365ms

When Find transport in table with status "planned" 1s 211ms

And Confirm statuses until reach "process-ended" 10s 338ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

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

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

When Accept or reject "accept" transferred transport 18s 033ms

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

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

And Set advice window in schedule 2s 752ms

And Fill advice form 14s 816ms

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

And If user is login then logout 116ms

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

And Find transport in table with status "advice-added" 1s 217ms

And Confirm statuses until reach "process-ended" 10s 313ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:35)

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

When Accept or reject "accept" transferred transport 18s 082ms

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

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

And Set advice window in schedule 2s 648ms

And Fill advice form 14s 707ms

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

And If user is login then logout 105ms

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

And Find transport in table with status "advice-added" 1s 217ms

And Confirm statuses until reach "process-ended" 10s 338ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:35)

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_ADVICE" "CHECKPOINT_BASED" "ARRIVAL" 241ms

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

When Login as "hochland-admin" 2s 823ms

And Find transport in table with status "advice-added" 1s 319ms

And Confirm statuses until reach "arrived" 10s 346ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:49)

And Go to transport details "DELIVERY" 000ms

Then Check if it is not possible to edit advice 000ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.rollbackAddedActionAuthorities() 066ms

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

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

When Find transport in table with status "advice-added" 1s 187ms

And Check if transport row is "blue" 3s 085ms

And Confirm statuses until reach "arrived" 10s 282ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:62)

And Check if transport row is "green" 000ms

And Confirm statuses until reach "during-unload" 000ms

Then Check if transport row is "orange" 000ms

And Confirm statuses until reach "unloaded" 000ms

Then Check if transport row is "darkgoldenrod" 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport row is "silver" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

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

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

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

And Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 557ms

And Fill advice form 8s 503ms

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

And Go to "TRANSPORT_TABLE" 223ms

And Find transport in table with status "advice-added" 1s 194ms

And Confirm statuses until reach "left-the-area" 10s 352ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "left-the-area"(file:Features/Atom/Statuses/ConfirmStatuses.feature:86)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

And Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 547ms

And Fill advice form 8s 452ms

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

And Go to "TRANSPORT_TABLE" 163ms

And Find transport in table with status "advice-added" 1s 217ms

And Confirm statuses until reach "left-the-area" 10s 357ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "left-the-area"(file:Features/Atom/Statuses/ConfirmStatuses.feature:86)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

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

And Show all transport types 1s 058ms

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

And Set advice window in schedule 2s 545ms

And Fill advice form 8s 417ms

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

And Go to "TRANSPORT_TABLE" 230ms

And Find transport in table with status "advice-added" 1s 194ms

When Add file to transport by API 838ms

And Confirm statuses until reach "process-ended" 10s 335ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:106)

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 531ms

And Fill advice form 8s 465ms

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

And Go to "TRANSPORT_TABLE" 172ms

And Find transport in table with status "advice-added" 1s 211ms

When Add file to transport by API 281ms

And Confirm statuses until reach "process-ended" 10s 351ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:106)

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

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

And Get "Magazynier (R)" settings from "hochland" in "TRANSFER_BETWEEN_WAREHOUSES" 047ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 133ms

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

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

And Login as "hochland-admin" 3s 131ms

And Show all transport types 1s 066ms

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

And Set advice window in schedule 6s 435ms

And Fill advice form 11s 904ms

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

And Go to "TRANSPORT_TABLE" 181ms

And Find transport in table with status "advice-added" 1s 194ms

And Confirm statuses until reach "during-load" 10s 355ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "during-load"(file:Features/Atom/Statuses/ConfirmStatuses.feature:128)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

After Hooks.rollbackCustomFieldSettings() 048ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "LOAD" 021ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 060ms

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

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

And Login as "keeeper-admin" 1s 984ms

And Show all transport types 1s 136ms

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

And Set advice window in schedule 2s 402ms

And Fill advice form 13s 307ms

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

And Go to "TRANSPORT_TABLE" 153ms

And Find transport in table with status "advice-added" 1s 216ms

And Confirm statuses until reach "arrived" 10s 313ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:128)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.rollbackCustomFieldSettings() 034ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "CONTAINER" 025ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 035ms

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

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

And Login as "keeeper-admin" 2s 122ms

And Show all transport types 1s 056ms

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

And Set advice window in schedule 2s 420ms

And Fill advice form 13s 301ms

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

And Go to "TRANSPORT_TABLE" 166ms

And Find transport in table with status "advice-added" 1s 194ms

And Confirm statuses until reach "arrived" 10s 331ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:128)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

After Hooks.rollbackCustomFieldSettings() 036ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 024ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 032ms

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

And Login as "keeeper-admin" 1s 977ms

And Go to "TRANSPORT_TABLE" 091ms

And Find transport in table with status "planned" 1s 159ms

And Confirm statuses until reach "arrived" 10s 344ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:145)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.rollbackCustomFieldSettings() 034ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 021ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 027ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 357ms

And Login as "keeeper-admin" 2s 019ms

And Go to "TRANSPORT_TABLE" 099ms

And Find transport in table with status "planned" 1s 207ms

And Confirm statuses until reach "arrived" 10s 326ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:145)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

After Hooks.rollbackCustomFieldSettings() 054ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 022ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 095ms

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

And Login as "hochland-admin" 2s 597ms

And Go to "TRANSPORT_TABLE" 156ms

And Find transport in table with status "advice-added" 1s 183ms

And Confirm statuses until reach "during-unload" 10s 345ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "during-unload"(file:Features/Atom/Statuses/ConfirmStatuses.feature:145)

Then Check if next status is not possible to confirm 000ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

After Hooks.rollbackCustomFieldSettings() 101ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 091ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "LOAD" 020ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 031ms

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

And Login as "keeeper-admin" 1s 830ms

And Show all transport types 1s 115ms

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

And Set advice window in schedule 2s 455ms

And Fill advice form 13s 309ms

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

And Go to "TRANSPORT_TABLE" 167ms

And Find transport in table with status "advice-added" 1s 224ms

When Confirm statuses until reach "arrived" 10s 346ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:168)

And Check if next status is not possible to confirm 000ms

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

And Go to transport details "LOAD" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

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

And Go to transport details "LOAD" 000ms

And Open section: "advice-panel" 000ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 000ms

And Confirm statuses until reach "process-ended" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackCustomFieldSettings() 034ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 093ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "CONTAINER" 035ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 038ms

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

And Login as "keeeper-admin" 2s 178ms

And Show all transport types 1s 052ms

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

And Set advice window in schedule 2s 375ms

And Fill advice form 13s 299ms

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

And Go to "TRANSPORT_TABLE" 185ms

And Find transport in table with status "advice-added" 1s 233ms

When Confirm statuses until reach "arrived" 10s 312ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:168)

And Check if next status is not possible to confirm 000ms

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

And Go to transport details "CONTAINER" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

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

And Go to transport details "CONTAINER" 000ms

And Open section: "advice-panel" 000ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 000ms

And Confirm statuses until reach "process-ended" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.rollbackCustomFieldSettings() 052ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

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

And Get "Magazynier (R)" settings from "hochland" in "TRANSFER_BETWEEN_WAREHOUSES" 020ms

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

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 076ms

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

And Login as "hochland-admin" 2s 423ms

And Show all transport types 1s 063ms

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

And Set advice window in schedule 6s 413ms

And Fill advice form 11s 926ms

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

And Go to "TRANSPORT_TABLE" 186ms

And Find transport in table with status "advice-added" 1s 199ms

When Confirm statuses until reach "during-load" 10s 368ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "during-load"(file:Features/Atom/Statuses/ConfirmStatuses.feature:168)

And Check if next status is not possible to confirm 000ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 000ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill "warehouseman-(u)" in transport form 000ms

And Confirm statuses until reach "process-ended" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.rollbackCustomFieldSettings() 060ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 022ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 034ms

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

And Login as "keeeper-admin" 2s 192ms

And Go to "TRANSPORT_TABLE" 103ms

And Find transport in table with status "planned" 1s 170ms

When Confirm statuses until reach "arrived" 10s 332ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:196)

And Check if next status is not possible to confirm 000ms

And Go to transport details "UNLOAD" 000ms

And Fill transport form 000ms

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

And Confirm statuses until reach "process-ended" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.rollbackCustomFieldSettings() 035ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 091ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 024ms

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 034ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 334ms

And Login as "keeeper-admin" 1s 872ms

And Go to "TRANSPORT_TABLE" 096ms

And Find transport in table with status "planned" 1s 199ms

When Confirm statuses until reach "arrived" 10s 265ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:196)

And Check if next status is not possible to confirm 000ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 000ms

And Fill transport form 000ms

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

And Confirm statuses until reach "process-ended" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.rollbackCustomFieldSettings() 040ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 026ms

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

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 094ms

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

And Login as "hochland-admin" 2s 320ms

And Go to "TRANSPORT_TABLE" 170ms

And Find transport in table with status "advice-added" 1s 173ms

When Confirm statuses until reach "during-unload" 10s 308ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "during-unload"(file:Features/Atom/Statuses/ConfirmStatuses.feature:196)

And Check if next status is not possible to confirm 000ms

And Go to transport details "DELIVERY" 000ms

And Fill transport form 000ms

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

And Confirm statuses until reach "process-ended" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.rollbackCustomFieldSettings() 097ms

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

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

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

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

And Login as "swiss-krono-delivery-guard" 1s 708ms

And Go to "TRANSPORT_TABLE" 141ms

When Confirm "Departure" status in transport row 3s 071ms

Then Verify that "Departure" has been confirmed 036ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 022ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 029ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 15s 314ms

When Login as "keeeper-admin" 2s 007ms

And Find transport in table with status "planned" 1s 170ms

And Confirm statuses until reach "arrived" 10s 325ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:235)

And Go to transport details "UNLOAD" 000ms

And Fill transport form 000ms

Then Check if next status is not possible to confirm in transport details 000ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackCustomFieldSettings() 036ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 025ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 029ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 331ms

When Login as "keeeper-admin" 1s 877ms

And Find transport in table with status "planned" 1s 187ms

And Confirm statuses until reach "arrived" 10s 282ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "arrived"(file:Features/Atom/Statuses/ConfirmStatuses.feature:235)

And Go to transport details "TANKER_GRANULATE_DELIVERY" 000ms

And Fill transport form 000ms

Then Check if next status is not possible to confirm in transport details 000ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.rollbackCustomFieldSettings() 034ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 021ms

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

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 100ms

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

When Login as "hochland-admin" 2s 392ms

And Find transport in table with status "advice-added" 1s 303ms

And Confirm statuses until reach "during-unload" 10s 366ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "during-unload"(file:Features/Atom/Statuses/ConfirmStatuses.feature:235)

And Go to transport details "DELIVERY" 000ms

And Fill transport form 000ms

Then Check if next status is not possible to confirm in transport details 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.rollbackCustomFieldSettings() 092ms

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

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

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

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 297ms

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

When Reject status: Book of disinfection 15s 066ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-btn-name='reject-checkpoint']"}
  (Session info: headless chrome=88.0.4324.146)
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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
*** Element info: {Using=xpath, value=//button[@data-btn-name='reject-checkpoint']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at CucumberTests.StatusTests.RejectStatuses.rejectStatusBookOfDisinfection(RejectStatuses.java:41)
	at ✽.Reject status: Book of disinfection(file:Features/Atom/Statuses/RejectStatuses.feature:10)

And Check if reject date is visible 000ms

Then If user is login then logout 000ms

And Login as "lantmannen-admin" 000ms

And Check if note was added to transport after status rejection 000ms

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 000ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 155ms

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" and set token of apiUsername "super-admin-lantmannen" 1s 120ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 303ms

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

When Reject status: Book of disinfection 15s 062ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-btn-name='reject-checkpoint']"}
  (Session info: headless chrome=88.0.4324.146)
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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
*** Element info: {Using=xpath, value=//button[@data-btn-name='reject-checkpoint']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at CucumberTests.StatusTests.RejectStatuses.rejectStatusBookOfDisinfection(RejectStatuses.java:41)
	at ✽.Reject status: Book of disinfection(file:Features/Atom/Statuses/RejectStatuses.feature:27)

And Check if reject date is visible 000ms

And Get rejection date 000ms

And Wait "60" seconds 000ms

And Reject status: Book of disinfection 000ms

Then Check if reject date has changed 000ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

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

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

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

When Reject status: Book of disinfection 089ms

Then Check if reject date is visible 220ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

And Open statuses popup 103ms

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

When Reject status: Book of disinfection 089ms

Then Open statuses popup 070ms

And Check if reject date is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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

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

And Confirm to the last status by API 225ms

When Find statuses for transport in table 1s 975ms

And Revoke statuses until reach "advice-added" 6s 832ms

Then Check if transport has "advice-added" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

And Confirm to the last status by API 285ms

When Find statuses for transport in table 1s 719ms

And Revoke statuses until reach "planned" 6s 740ms

Then Check if transport has "planned" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

When Find transport in table with status "new" 1s 150ms

And Open statuses popup 096ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 15s 058ms

Error message

org.junit.ComparisonFailure: Lista statusów jest niepoprawna expected:<[Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfTransportHasCheckpointsFromListInGroup(ConfirmStatuses.java:103)
	at ✽.Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0"(file:Features/Atom/Statuses/Statuses.feature:9)

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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

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

And Click button advice in transport table "EXTERNAL_DELIVERY" 125ms

And Set advice window in schedule 2s 731ms

And Fill advice form 12s 209ms

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

And Go to "TRANSPORT_TABLE" 235ms

When Find transport in table with status "advice-added" 1s 185ms

And Open statuses popup 099ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 15s 033ms

Error message

org.junit.ComparisonFailure: Lista statusów jest niepoprawna expected:<[Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfTransportHasCheckpointsFromListInGroup(ConfirmStatuses.java:103)
	at ✽.Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1"(file:Features/Atom/Statuses/Statuses.feature:26)

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

When Go to "WAREHOUSE_TAB" 701ms

And Select warehouse "Serownia" 1s 379ms

And Set week view 1s 123ms

And Show yesterday 1s 065ms

And Move window into the past 307ms

Then Check if window is "red" 2s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 252ms

After Hooks.rollbackAddedAuthorities() 017ms

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

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 040ms

When Go to "WAREHOUSE_TAB" 291ms

And Select warehouse "Magazyn - Nowa Sól" 2s 226ms

And Set week view 1s 147ms

And Show yesterday 1s 070ms

And Move window into the past 403ms

Then Check if window is "red" 2s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

After Hooks.rollbackAddedAuthorities() 028ms

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

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 034ms

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

And Set advice window in schedule 2s 618ms

And Fill advice form 8s 538ms

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

And Select warehouse "Magazyn Hala A" 1s 214ms

And Set week view 2s 045ms

And Show yesterday 1s 855ms

And Move window into the past 621ms

Then Check if window is "red" 2s 056ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

After Hooks.rollbackAddedAuthorities() 027ms

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

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" 323ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 380ms

When Go to "WAREHOUSE_TAB" 785ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 736ms

And Set week view 1s 117ms

And Check if time window length is correct after "CREATE" 031ms

And Change number of pallets in transport 52s 260ms

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

And Check if time window length is correct after "EDIT" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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

And Get "UNLOAD" settings from "keeeper" 045ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" 092ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 103ms

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

When Go to "WAREHOUSE_TAB" 305ms

And Select warehouse "Magazyn Surowców" 1s 195ms

And Set week view 1s 116ms

Then Check if time window has proper "60" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

After Hooks.rollbackTransportTypeSettings() 054ms

After Hooks.clearAlgorithmSettings() 128ms

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

And Get "UNLOAD" settings from "keeeper" 028ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" 089ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 057ms

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

When Go to "WAREHOUSE_TAB" 308ms

And Select warehouse "Magazyn Surowców" 1s 145ms

And Set week view 1s 091ms

Then Check if time window has proper "60" 055ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.rollbackTransportTypeSettings() 054ms

After Hooks.clearAlgorithmSettings() 091ms

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

And Get "LOAD" settings from "keeeper" 022ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" 085ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 055ms

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

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

And Show all transport types 1s 032ms

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

And Set advice window in schedule 2s 399ms

And Fill advice form 13s 294ms

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

Then Check if time window has proper "30" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.rollbackTransportTypeSettings() 066ms

After Hooks.clearAlgorithmSettings() 078ms

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

And Get "CONTAINER" settings from "keeeper" 025ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" 077ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "20;false" 056ms

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

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

And Show all transport types 1s 055ms

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

And Set advice window in schedule 2s 434ms

And Fill advice form 13s 331ms

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

Then Check if time window has proper "60" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.rollbackTransportTypeSettings() 059ms

After Hooks.clearAlgorithmSettings() 110ms

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

And Set algorithm setting for "super-admin-hochland" in "Serownia" 108ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 090ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 298ms

And Set token of apiUsername "super-admin-hochland" 105ms

When Go to transport details "DELIVERY" 32s 801ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 361ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 316ms

And Change filled value in transport details "warehouseman" "select" "Błajet" "0" 3s 552ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "TAK" "0" 3s 446ms

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

And Go to "WAREHOUSE_TAB" 897ms

And Select warehouse "Serownia" 1s 383ms

And Set week view 1s 102ms

Then Check if time window has proper "60" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.clearAlgorithmSettings() 137ms

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

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 038ms

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

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 511ms

And Check if time window counter value equals "1" 070ms

And Select view "DAYS_2" 2s 092ms

And Move advice window "2" 1s 337ms

And Select view "DAY" 2s 075ms

Then Check if time window counter value equals "0" 072ms

And Delete created transport by API 108ms

And Check if time window counter value equals "0" 038ms

And Click in free spot in schedule page to create gray window 173ms

And Check if time window counter value equals "0" 053ms

And Click in free spot in schedule page to create dedicated window 057ms

And Check if time window counter value equals "0" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.rollbackAddedAuthorities() 000ms

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

When Go to new transport "DELIVERY" 259ms

And Fill transport form 11s 447ms

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

And Set advice window in schedule 2s 189ms

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

And Go to "TRANSPORT_TABLE" 222ms

When Click on time window date 1s 317ms

And Open transport form when in schedule 1s 169ms

Then Check are transport values equals 133ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

When Go to new transport "DELIVERY" 349ms

And Fill transport form 40s 294ms

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

And Set advice window in schedule 2s 167ms

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

And Go to "TRANSPORT_TABLE" 239ms

When Click on time window date 1s 263ms

And Open transport form when in schedule 1s 268ms

Then Check are transport values equals 19s 438ms

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_CISTERN_DELIVERY" "super-admin-hochland" 002ms

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

When Go to new transport "CISTERN_DELIVERY" 345ms

And Fill transport form 34s 894ms

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

And Set advice window in schedule 2s 209ms

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

And Go to "TRANSPORT_TABLE" 196ms

When Click on time window date 1s 458ms

And Open transport form when in schedule 1s 203ms

Then Check are transport values equals 21s 382ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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

When Go to new transport "CISTERN_COLLECTION" 329ms

And Fill transport form 28s 424ms

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

And Set advice window in schedule 2s 204ms

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

And Go to "TRANSPORT_TABLE" 181ms

When Click on time window date 1s 399ms

And Open transport form when in schedule 1s 219ms

Then Check are transport values equals 21s 350ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

When Go to new transport "DELIVERY" 310ms

And Fill transport form 38s 081ms

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

And Set advice window in schedule 2s 165ms

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

And Go to "TRANSPORT_TABLE" 197ms

When Click on time window date 1s 300ms

And Open transport form when in schedule 1s 155ms

Then Check are transport values equals 19s 380ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

When Go to new transport "LOAD" 319ms

And Fill transport form 37s 993ms

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

And Set advice window in schedule 2s 160ms

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

And Go to "TRANSPORT_TABLE" 234ms

When Click on time window date 1s 294ms

And Open transport form when in schedule 1s 167ms

Then Check are transport values equals 19s 325ms

Hooks

After Hooks.deleteTransportAfterTest() 161ms

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

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "MANAGE_UNLOAD_STEPS" "ACTIVE" 115ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 044ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 101ms

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

And Login as "farmacol-admin" 2s 471ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 46s 417ms

And Go to "TRANSPORT_TABLE" 307ms

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

And Add step "unload" 102ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 445ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 346ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 351ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 333ms

Then Click "save-transport" save button 211ms

And Set advice window in schedule in "2" days 30s 896ms

And Click advice save button and wait for advice form to disappear 31s 099ms

And Go to "TRANSPORT_TABLE" 202ms

And Check if transport has "2" time windows 015ms

Hooks

After Hooks.deleteTransportAfterTest() 162ms

After Hooks.rollbackTransportTypeSettings() 105ms

After Hooks.rollbackAddedActionAuthorities() 045ms

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

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 051ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 197ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 563ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 094ms

And Go to "TRANSPORT_TABLE" 296ms

And Get checkpoint colors for transport 006ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 10s 525ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsChangeInColumnProperlyWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:102)
	at ✽.Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:232)

Hooks

After Hooks.deleteTransportAfterTest() 136ms

After Hooks.rollbackTransportTypeSettings() 062ms

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 032ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 064ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 246ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 085ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 039ms

And Go to "TRANSPORT_TABLE" 286ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 10s 505ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsChangeInColumnProperlyWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:102)
	at ✽.Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false"(file:Features/Atom/TimeWindow/TransportWindow.feature:232)

Hooks

After Hooks.deleteTransportAfterTest() 150ms

After Hooks.rollbackTransportTypeSettings() 112ms

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 033ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 047ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 217ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 103ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 840ms

And Get checkpoint colors for transport 005ms

And Go to "TRANSPORT_TABLE" 270ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 652ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=88.0.4324.146)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getCssValue(RemoteWebElement.java:165)
	at CucumberTests.TimeWindow.TimeWindowTest.checkIfWindowsHasProperColorsInSchedule(TimeWindowTest.java:176)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:117)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:250)

Hooks

After Hooks.deleteTransportAfterTest() 166ms

After Hooks.rollbackTransportTypeSettings() 085ms

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 032ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 062ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 189ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 111ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 713ms

And Get checkpoint colors for transport 005ms

And Go to "TRANSPORT_TABLE" 263ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 689ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=88.0.4324.146)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getCssValue(RemoteWebElement.java:165)
	at CucumberTests.TimeWindow.TimeWindowTest.checkIfWindowsHasProperColorsInSchedule(TimeWindowTest.java:176)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:117)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false"(file:Features/Atom/TimeWindow/TransportWindow.feature:250)

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.rollbackTransportTypeSettings() 125ms

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

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 003ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 030ms

And Set proper delay time to move order to archive after task timeout 038ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 302ms

And Wait "60" seconds 1m

And Go to "WAREHOUSE_TAB" 633ms

And Change warehouse in schedule to: "Katowice" 1s 141ms

And Verify that transport window is grey 097ms

And Verify that transport is in archive 558ms

Then Restore transport from archive 891ms

And Verify that transport has been successfully restored 15s 224ms

Hooks

After Hooks.deleteTransportAfterTest() 217ms

After Hooks.rollbackSettings() 073ms

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

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

When Fill auction form 15s 509ms

Then Verify that the auction has been added to transport 046ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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

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

When Fill auction form 15s 388ms

Then Verify that the auction has been added to transport 052ms

Hooks

After Hooks.deleteTransportAfterTest() 359ms

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

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

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

When If user is login then logout 117ms

And Login as "paa1-carrier@qa.qa-test" 3s 008ms

And Go to auction offer 1s 348ms

And Accept transport with minimum rate 15s 590ms

Then Check if carrier is assigned to transport 017ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

When If user is login then logout 086ms

And Login as "paa1-carrier@qa.qa-test" 1s 585ms

And Go to auction offer 1s 178ms

And Reject auction offer 15s 636ms

Then Verify that offer has been removed from transport 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

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

When If user is login then logout 097ms

And Login as "pskza1-carrier@qa.qa-test" 3s 409ms

And Go to auction offer 1s 192ms

And Reject auction offer 15s 589ms

Then Verify that offer has been removed from transport 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

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

When If user is login then logout 132ms

And Login as "paa1-carrier@qa.qa-test" 1s 255ms

And Go to auction offer 1s 206ms

And Offer prize above maximum - "20000" 141ms

Then Verify that is not possible to add offer 150ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 173ms

When If user is login then logout 095ms

And Login as "pskza1-carrier@qa.qa-test" 1s 065ms

And Go to auction offer 1s 205ms

And Offer prize above maximum - "20000" 137ms

Then Verify that is not possible to add offer 142ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 043ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 223ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 108ms

And Wait till auction end 1m 58s 013ms

Then Verify that is possible to add auction 055ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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 296ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 270ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 123ms

And Wait till auction end 1m 58s 027ms

Then Verify that is possible to add auction 048ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 198ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 130ms

And Go to auction offer 1s 207ms

When Offer "1000" 139ms

Then Verify that offer with "1000" has been added to auction 3s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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" 1s 076ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 251ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 106ms

And Go to auction offer 1s 212ms

When Offer "1000" 122ms

Then Verify that offer with "1000" has been added to auction 3s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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 103ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 207ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 106ms

And Go to auction offer 1s 183ms

When Offer "1000" 129ms

And Verify that offer with "1000" has been added to auction 3s 038ms

Then Go to auction offer 1s 183ms

And Revoke current offer 564ms

And Verify that offer has been revoked 30s 579ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 243ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 267ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 120ms

And Go to auction offer 1s 226ms

When Offer "1000" 137ms

And Verify that offer with "1000" has been added to auction 3s 040ms

Then Go to auction offer 1s 179ms

And Offer "1500" 148ms

And Verify that offer with "1500" has been added to auction 3s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 034ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 215ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 082ms

And Go to auction offer 1s 200ms

When Offer "1000" 130ms

And Verify that offer with "1000" has been added to auction 3s 036ms

Then Login as "swisskrono-admin" 1s 070ms

And Go to auction details 1s 201ms

And Finish active auction 055ms

And Verify that the transport has no active auction 149ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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" 1s 016ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 220ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 078ms

And Go to auction offer 1s 201ms

When Offer "1000" 143ms

Then Verify that carrier can see current place in auction depending on the "true" role 143ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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 044ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 245ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 109ms

And Go to auction offer 1s 187ms

When Offer "1000" 132ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 106ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 240ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 075ms

And Go to auction offer 1s 220ms

When Offer "300" 139ms

And Verify that carrier can't add offer to auction 033ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 043ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 218ms

And Show all transport "false" 011ms

When Go to auction form 1s 330ms

Then Verify carrier selection value "false" 035ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 049ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 259ms

And Show all transport "true" 080ms

When Go to auction form 1s 199ms

Then Verify carrier selection value "true" 036ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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 069ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

When Open transport auction form 215ms

And Select all companies checkbox in transport auction form 066ms

And Unselect company "PAA2" in transport auction form 071ms

And Put transport on auction 15s 164ms

And Open transport auction history 094ms

And Open participants section in transport auction history 059ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 274ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 230ms

When Open transport auction form 169ms

And Select all companies checkbox in transport auction form 058ms

And Unselect company "PSKZA2" in transport auction form 072ms

And Put transport on auction 15s 256ms

And Open transport auction history 079ms

And Open participants section in transport auction history 046ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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" 2s 984ms

When Go to new transport "UNLOAD" 15s 296ms

And Fill transport form 24s 619ms

And Click "save-transport" save button and wait for form to disappear 15s 979ms

And Set advice window in schedule 2s 221ms

And Check is transport created in schedule and set transport id 660ms

And Go to "TRANSPORT_TABLE" 233ms

And Go to transport details "UNLOAD" 32s 439ms

Then Check are transport values equals 21s 402ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 130ms

When Go to new transport "DELIVERY" 307ms

And Fill transport form 11s 456ms

And Click "save-transport" save button and wait for form to disappear 15s 641ms

And Set advice window in schedule 2s 172ms

And Check is transport created in schedule and set transport id 501ms

And Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "DELIVERY" 4s 351ms

Then Check are transport values equals 141ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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" 003ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 103ms

When Go to new transport "OWN_COLLECTION" 278ms

And Fill transport form 18s 023ms

And Click "save-transport" save button and wait for form to disappear 15s 633ms

And Set advice window in schedule 2s 152ms

And Check is transport created in schedule and set transport id 440ms

And Go to "TRANSPORT_TABLE" 166ms

And Go to transport details "OWN_COLLECTION" 4s 332ms

Then Check are transport values equals 125ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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" 001ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 482ms

When Go to new transport "DELIVERY" 363ms

And Fill transport form 40s 394ms

And Click "save-transport" save button and wait for form to disappear 15s 618ms

And Set advice window in schedule 2s 173ms

And Check is transport created in schedule and set transport id 625ms

And Go to "TRANSPORT_TABLE" 246ms

And Go to transport details "DELIVERY" 4s 625ms

Then Check are transport values equals 19s 400ms

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_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 453ms

When Go to new transport "CISTERN_DELIVERY" 347ms

And Fill transport form 34s 912ms

And Click "save-transport" save button and wait for form to disappear 15s 895ms

And Set advice window in schedule 2s 222ms

And Check is transport created in schedule and set transport id 588ms

And Go to "TRANSPORT_TABLE" 166ms

And Go to transport details "CISTERN_DELIVERY" 4s 390ms

Then Check are transport values equals 21s 384ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 435ms

When Go to new transport "CISTERN_COLLECTION" 318ms

And Fill transport form 28s 446ms

And Click "save-transport" save button and wait for form to disappear 15s 884ms

And Set advice window in schedule 2s 210ms

And Check is transport created in schedule and set transport id 584ms

And Go to "TRANSPORT_TABLE" 187ms

And Go to transport details "CISTERN_COLLECTION" 4s 377ms

Then Check are transport values equals 21s 393ms

Hooks

After Hooks.deleteTransportAfterTest() 171ms

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 486ms

When Go to new transport "OWN_COLLECTION" 379ms

And Fill transport form 32s 833ms

And Click "save-transport" save button and wait for form to disappear 15s 649ms

And Set advice window in schedule 2s 174ms

And Check is transport created in schedule and set transport id 593ms

And Go to "TRANSPORT_TABLE" 174ms

And Go to transport details "OWN_COLLECTION" 4s 543ms

Then Check are transport values equals 19s 400ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 503ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 371ms

And Fill transport form 32s 806ms

And Click "save-transport" save button and wait for form to disappear 15s 650ms

And Set advice window in schedule 2s 172ms

And Check is transport created in schedule and set transport id 629ms

And Go to "TRANSPORT_TABLE" 181ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 460ms

Then Check are transport values equals 4s 310ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 503ms

When Go to new transport "EXPORT" 441ms

And Fill transport form 40s 790ms

And Click "save-transport" save button and wait for form to disappear 15s 611ms

And Set advice window in schedule 2s 163ms

And Check is transport created in schedule and set transport id 624ms

And Go to "TRANSPORT_TABLE" 169ms

And Go to transport details "EXPORT" 5s 499ms

Then Check are transport values equals 4s 375ms

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" 003ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 509ms

When Go to new transport "DELIVERY" 15s 261ms

And Fill transport form 28s 410ms

And Click "save-transport" save button and wait for form to disappear 15s 613ms

And Set advice window in schedule 2s 161ms

And Check is transport created in schedule and set transport id 828ms

And Go to "TRANSPORT_TABLE" 208ms

And Go to transport details "DELIVERY" 32s 366ms

Then Check are transport values equals 36s 344ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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" 003ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 119ms

When Go to new transport "DELIVERY" 305ms

And Fill transport form 38s 069ms

And Click "save-transport" save button and wait for form to disappear 15s 607ms

And Set advice window in schedule 2s 156ms

And Check is transport created in schedule and set transport id 500ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "DELIVERY" 4s 311ms

Then Check are transport values equals 19s 329ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 149ms

When Go to new transport "LOAD" 289ms

And Fill transport form 38s 046ms

And Click "save-transport" save button and wait for form to disappear 15s 624ms

And Set advice window in schedule 2s 194ms

And Check is transport created in schedule and set transport id 524ms

And Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "LOAD" 4s 329ms

Then Check are transport values equals 19s 331ms

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_DELIVERY" "super-admin-keeeper" 003ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 181ms

When Go to new transport "UNLOAD" 320ms

And Fill transport form 37s 662ms

And Click "save-transport" save button and wait for form to disappear 15s 613ms

And Set advice window in schedule 2s 147ms

And Check is transport created in schedule and set transport id 585ms

And Go to "TRANSPORT_TABLE" 182ms

And Go to transport details "UNLOAD" 4s 379ms

Then Check are transport values equals 21s 413ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 169ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 344ms

And Fill transport form 37s 621ms

And Click "save-transport" save button and wait for form to disappear 15s 581ms

And Set advice window in schedule 2s 163ms

And Check is transport created in schedule and set transport id 631ms

And Go to "TRANSPORT_TABLE" 175ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 356ms

Then Check are transport values equals 21s 430ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 150ms

When Go to new transport "DELIVERY" 295ms

And Fill transport form 22s 922ms

And Click "save-transport" save button and wait for form to disappear 15s 583ms

And Set advice window in schedule 2s 175ms

And Check is transport created in schedule and set transport id 620ms

And Go to "TRANSPORT_TABLE" 181ms

And Go to transport details "DELIVERY" 4s 338ms

Then Check are transport values equals 17s 272ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 466ms

When Go to new transport "WEIGHING" 301ms

And Fill transport form 13s 613ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 608ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "WEIGHING" 4s 382ms

And Check are transport values equals 2s 188ms

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_TRANSPORT" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 230ms

When Go to new transport "TRANSPORT" 389ms

And Fill transport form 26s 804ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 612ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 110ms

And Go to transport details "TRANSPORT" 4s 460ms

And Check are transport values equals 6s 211ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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" 001ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 161ms

When Go to new transport "CONTAINER" 332ms

And Fill transport form 11s 194ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Show all transport "false" 007ms

And Go to "TRANSPORT_TABLE" 104ms

And Go to transport details "CONTAINER" 4s 346ms

And Check are transport values equals 088ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 486ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 361ms

And Fill transport form 12s 980ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 627ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 109ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 647ms

And Check are transport values equals 4s 202ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 784ms

When Go to new transport "DELIVERY" 292ms

And Fill transport form 22s 582ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 636ms

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 106ms

And Go to transport details "DELIVERY" 4s 544ms

And Check are transport values equals 17s 177ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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" 001ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 190ms

When Go to new transport "LOAD" 364ms

And Fill transport form 26s 350ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 643ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 118ms

And Go to transport details "LOAD" 4s 652ms

And Check are transport values equals 2s 163ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 110ms

When Go to new transport "LOAD" 330ms

And Fill transport form 24s 732ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 663ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 120ms

And Go to transport details "LOAD" 4s 392ms

And Check are transport values equals 19s 247ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 156ms

When Go to new transport "CONTAINER" 323ms

And Fill transport form 24s 697ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 651ms

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 117ms

And Go to transport details "CONTAINER" 4s 367ms

And Check are transport values equals 19s 211ms

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 249ms

When Go to new transport "SMALLS_IMPORT" 361ms

And Fill transport form 36s 403ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 116ms

And Go to transport details "SMALLS_IMPORT" 4s 435ms

And Check are transport values equals 10s 360ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 208ms

When Go to new transport "SMALLS_EXPORT" 406ms

And Fill transport form 36s 380ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 608ms

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 099ms

And Go to transport details "SMALLS_EXPORT" 4s 432ms

And Check are transport values equals 10s 375ms

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_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 131ms

When Go to new transport "TRANSPORT_ORDER" 441ms

And Fill transport form 30s 132ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 616ms

And Show all transport "true" 089ms

And Go to "TRANSPORT_TABLE" 111ms

And Go to transport details "TRANSPORT_ORDER" 4s 366ms

And Check are transport values equals 19s 332ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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" 401ms

And Fill transport form 37s 636ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 609ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 118ms

And Go to transport details "TRANSPORT" 4s 458ms

And Check are transport values equals 4s 224ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 193ms

When Go to new transport "INBOUND" 356ms

And Fill transport form 41s 145ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 609ms

And Show all transport "true" 086ms

And Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "INBOUND" 4s 423ms

And Check are transport values equals 2s 312ms

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_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 003ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 169ms

When Go to new transport "EXTERNAL_DELIVERY" 315ms

And Fill transport form 53s 739ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 650ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 120ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 429ms

And Check are transport values equals 4s 485ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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" 002ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 2s 815ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 282ms

And Fill transport form 47s 442ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 645ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 111ms

And Go to transport details "EXTERNAL_DELIVERY" 32s 449ms

And Check are transport values equals 4s 489ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 148ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 679ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 32s 492ms

And Fill transport form 30s 435ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 119ms

And Go to transport details "UNLOAD" 32s 442ms

Then Check are transport values equals 4s 273ms

Hooks

After Hooks.deleteTransportAfterTest() 153ms

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 157ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 280ms

And Show all transport "false" 010ms

When Go to transport details "TRANSPORT" 4s 528ms

And Fill transport form 10s 322ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 602ms

And Go to transport details "TRANSPORT" 4s 492ms

Then Check are transport values equals 4s 139ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 158ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 002ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 187ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 365ms

And Fill transport form 4s 725ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 628ms

And Go to transport details "CONTAINER" 4s 302ms

Then Check are transport values equals 070ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 165ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 330ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 395ms

And Fill transport form 11s 643ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 635ms

And Go to transport details "DELIVERY" 4s 324ms

Then Check are transport values equals 126ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 129ms

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 297ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION" 4s 391ms

And Fill transport form 21s 710ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Go to transport details "OWN_COLLECTION" 4s 349ms

Then Check are transport values equals 2s 207ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 370ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 380ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 723ms

And Fill transport form 35s 987ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 175ms

And Go to transport details "DELIVERY" 4s 480ms

Then Check are transport values equals 10s 578ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 357ms

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 289ms

And Show all transport "false" 007ms

When Go to transport details "OWN_COLLECTION" 4s 665ms

And Fill transport form 36s 751ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 131ms

And Go to transport details "OWN_COLLECTION" 4s 451ms

Then Check are transport values equals 6s 379ms

Hooks

After Hooks.deleteTransportAfterTest() 155ms

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 456ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 439ms

And Show all transport "false" 011ms

When Go to transport details "EXPORT" 5s 592ms

And Fill transport form 48s 200ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 170ms

And Go to transport details "EXPORT" 4s 539ms

Then Check are transport values equals 8s 469ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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 406ms

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 169ms

And Show all transport "false" 011ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 769ms

And Fill transport form 36s 246ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 726ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 435ms

Then Check are transport values equals 12s 464ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 491ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 289ms

And Show all transport "false" 007ms

When Go to transport details "CISTERN_DELIVERY" 4s 474ms

And Fill transport form 27s 348ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 649ms

And Go to transport details "CISTERN_DELIVERY" 4s 405ms

Then Check are transport values equals 6s 313ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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 362ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 002ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 335ms

And Show all transport "false" 011ms

When Go to transport details "CISTERN_COLLECTION" 4s 491ms

And Fill transport form 25s 921ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 623ms

And Go to transport details "CISTERN_COLLECTION" 4s 399ms

Then Check are transport values equals 6s 296ms

Hooks

After Hooks.deleteTransportAfterTest() 153ms

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 410ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 235ms

And Show all transport "false" 010ms

When Go to transport details "WEIGHING" 4s 401ms

And Fill transport form 12s 409ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 587ms

And Go to transport details "WEIGHING" 4s 338ms

Then Check are transport values equals 2s 131ms

Hooks

After Hooks.deleteTransportAfterTest() 061ms

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 333ms

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 443ms

And Show all transport "false" 012ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 622ms

And Fill transport form 35s 329ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 119ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 434ms

Then Check are transport values equals 6s 351ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 092ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 302ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 32s 405ms

And Fill transport form 25s 794ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 620ms

And Go to transport details "DELIVERY" 32s 323ms

Then Check are transport values equals 2s 207ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 160ms

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 220ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 599ms

And Fill transport form 1m 2s 513ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 145ms

And Go to transport details "DELIVERY" 4s 423ms

Then Check are transport values equals 132ms

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:267)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 203ms

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" 011ms

When Go to transport details "LOAD" 4s 707ms

And Fill transport form 57s 412ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 147ms

And Go to transport details "LOAD" 4s 478ms

Then Check are transport values equals 24s 765ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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 107ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 390ms

And Show all transport "false" 012ms

When Go to transport details "DELIVERY" 4s 382ms

And Fill transport form 16s 495ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 621ms

And Go to transport details "DELIVERY" 4s 322ms

Then Check are transport values equals 067ms

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 083ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 297ms

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 328ms

And Fill transport form 28s 255ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 128ms

And Go to transport details "LOAD" 4s 334ms

Then Check are transport values equals 2s 229ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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 184ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 399ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 4s 449ms

And Fill transport form 37s 849ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 132ms

And Go to transport details "UNLOAD" 4s 400ms

Then Check are transport values equals 6s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 139ms

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 376ms

And Show all transport "false" 005ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 466ms

And Fill transport form 36s 371ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 121ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 372ms

Then Check are transport values equals 6s 377ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 170ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 203ms

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 412ms

And Fill transport form 24s 802ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 653ms

And Go to transport details "LOAD" 4s 351ms

Then Check are transport values equals 4s 176ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 209ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 002ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 210ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 412ms

And Fill transport form 24s 738ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 618ms

And Go to transport details "CONTAINER" 4s 312ms

Then Check are transport values equals 4s 202ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

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 145ms

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 248ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_IMPORT" 4s 525ms

And Fill transport form 33s 121ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 620ms

And Go to transport details "SMALLS_IMPORT" 4s 436ms

Then Check are transport values equals 8s 360ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 265ms

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 242ms

And Show all transport "false" 013ms

When Go to transport details "SMALLS_EXPORT" 4s 516ms

And Fill transport form 33s 022ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 632ms

And Go to transport details "SMALLS_EXPORT" 4s 428ms

Then Check are transport values equals 8s 348ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 158ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 394ms

And Show all transport "true" 095ms

When Go to transport details "DELIVERY" 4s 331ms

And Fill transport form 19s 648ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 655ms

And Go to transport details "DELIVERY" 4s 339ms

Then Check are transport values equals 145ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 092ms

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 320ms

And Show all transport "true" 080ms

When Go to transport details "TRANSPORT_ORDER" 4s 501ms

And Fill transport form 26s 800ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 633ms

And Go to transport details "TRANSPORT_ORDER" 4s 382ms

Then Check are transport values equals 2s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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" 2s 711ms

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 179ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 452ms

And Fill transport form 8s 904ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 643ms

And Go to transport details "CONTAINER" 4s 383ms

Then Check are transport values equals 4s 109ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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 472ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 353ms

And Show all transport "false" 006ms

When Delete transport 17s 895ms

Then Transport not displayed in table of transports 15s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 180ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 206ms

And Show all transport "false" 011ms

When Delete transport 17s 266ms

Then Transport not displayed in table of transports 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 109ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 302ms

And Show all transport "false" 012ms

When Delete transport 17s 549ms

Then Transport not displayed in table of transports 15s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 224ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 214ms

And Show all transport "false" 010ms

When Delete transport 17s 087ms

Then Transport not displayed in table of transports 15s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 272ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 265ms

And Show all transport "false" 010ms

When Delete transport 17s 601ms

Then Transport not displayed in table of transports 15s 059ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 233ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 295ms

And Show all transport "false" 013ms

When Delete transport 17s 661ms

Then Transport not displayed in table of transports 15s 051ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 220ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 316ms

And Show all transport "true" 075ms

When Delete transport 19s 083ms

Then Transport not displayed in table of transports 15s 050ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 159ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 310ms

And Show all transport "true" 087ms

When Delete transport 17s 110ms

Then Transport not displayed in table of transports 15s 043ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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 095ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 545ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 32s 499ms

And Fill transport form 30s 490ms

And Click "save-transport" save button 1s 324ms

And Click cancel button in transport form 133ms

And Go to transport details "UNLOAD" 32s 429ms

Then Check are transport values equals 4s 268ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 144ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 223ms

And Show all transport "false" 012ms

When Go to transport details "TRANSPORT" 4s 489ms

And Fill transport form 10s 311ms

And Click "save-transport" save button 727ms

And Click cancel button in transport form 084ms

And Go to transport details "TRANSPORT" 4s 332ms

Then Check are transport values equals 4s 149ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 631ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 175ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 388ms

And Fill transport form 4s 723ms

And Click "save-transport" save button 706ms

And Click cancel button in transport form 065ms

And Go to transport details "CONTAINER" 4s 283ms

Then Check are transport values equals 046ms

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 093ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 268ms

And Show all transport "false" 007ms

When Go to transport details "DELIVERY" 4s 342ms

And Fill transport form 11s 587ms

And Click "save-transport" save button 709ms

And Click cancel button in transport form 079ms

And Go to transport details "DELIVERY" 4s 267ms

Then Check are transport values equals 128ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 157ms

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 284ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 374ms

And Fill transport form 21s 732ms

And Click "save-transport" save button 708ms

And Click cancel button in transport form 086ms

And Go to transport details "OWN_COLLECTION" 4s 313ms

Then Check are transport values equals 2s 235ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 467ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 345ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 4s 731ms

And Fill transport form 36s 114ms

And Click "save-transport" save button 1s 251ms

And Click cancel button in transport form 085ms

And Go to transport details "DELIVERY" 4s 399ms

Then Check are transport values equals 10s 536ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

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 437ms

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 333ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 714ms

And Fill transport form 36s 669ms

And Click "save-transport" save button 1s 255ms

And Click cancel button in transport form 089ms

And Go to transport details "OWN_COLLECTION" 4s 387ms

Then Check are transport values equals 6s 395ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 501ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 399ms

And Show all transport "false" 010ms

When Go to transport details "EXPORT" 5s 624ms

And Fill transport form 48s 217ms

And Click "save-transport" save button 1s 254ms

And Click cancel button in transport form 082ms

And Go to transport details "EXPORT" 4s 408ms

Then Check are transport values equals 8s 517ms

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 452ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 201ms

And Show all transport "false" 011ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 794ms

And Fill transport form 36s 235ms

And Click "save-transport" save button 927ms

And Click cancel button in transport form 081ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 422ms

Then Check are transport values equals 12s 459ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 421ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 325ms

And Show all transport "false" 012ms

When Go to transport details "CISTERN_DELIVERY" 4s 499ms

And Fill transport form 27s 361ms

And Click "save-transport" save button 808ms

And Click cancel button in transport form 098ms

And Go to transport details "CISTERN_DELIVERY" 4s 389ms

Then Check are transport values equals 6s 281ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 432ms

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 313ms

And Show all transport "false" 009ms

When Go to transport details "CISTERN_COLLECTION" 4s 463ms

And Fill transport form 26s 004ms

And Click "save-transport" save button 809ms

And Click cancel button in transport form 079ms

And Go to transport details "CISTERN_COLLECTION" 4s 357ms

Then Check are transport values equals 6s 309ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 428ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 205ms

And Show all transport "false" 011ms

When Go to transport details "WEIGHING" 4s 396ms

And Fill transport form 12s 296ms

And Click "save-transport" save button 715ms

And Click cancel button in transport form 072ms

And Go to transport details "WEIGHING" 4s 261ms

Then Check are transport values equals 2s 139ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 512ms

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 345ms

And Show all transport "false" 006ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 596ms

And Fill transport form 35s 402ms

And Click "save-transport" save button 1s 237ms

And Click cancel button in transport form 102ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 400ms

Then Check are transport values equals 6s 343ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 113ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 337ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 32s 440ms

And Fill transport form 25s 784ms

And Click "save-transport" save button 707ms

And Click cancel button in transport form 074ms

And Go to transport details "DELIVERY" 32s 308ms

Then Check are transport values equals 2s 213ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 220ms

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 178ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 4s 553ms

And Fill transport form 1m 2s 560ms

And Click "save-transport" save button 1s 261ms

And Click cancel button in transport form 096ms

And Go to transport details "DELIVERY" 4s 416ms

Then Check are transport values equals 151ms

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:267)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:136)

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 194ms

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 261ms

And Show all transport "false" 014ms

When Go to transport details "LOAD" 4s 729ms

And Fill transport form 57s 479ms

And Click "save-transport" save button 1s 259ms

And Click cancel button in transport form 093ms

And Go to transport details "LOAD" 4s 465ms

Then Check are transport values equals 24s 841ms

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 "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 995ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 401ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 370ms

And Fill transport form 16s 500ms

And Click "save-transport" save button 738ms

And Click cancel button in transport form 075ms

And Go to transport details "DELIVERY" 4s 323ms

Then Check are transport values equals 079ms

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" 2s 161ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 302ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 343ms

And Fill transport form 28s 264ms

And Click "save-transport" save button 1s 246ms

And Click cancel button in transport form 078ms

And Go to transport details "LOAD" 4s 282ms

Then Check are transport values equals 2s 233ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 215ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 376ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 4s 427ms

And Fill transport form 37s 928ms

And Click "save-transport" save button 1s 240ms

And Click cancel button in transport form 086ms

And Go to transport details "UNLOAD" 4s 343ms

Then Check are transport values equals 6s 403ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 101ms

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 340ms

And Show all transport "false" 010ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 503ms

And Fill transport form 36s 349ms

And Click "save-transport" save button 764ms

And Click cancel button in transport form 085ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 334ms

Then Check are transport values equals 6s 333ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 148ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 002ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 207ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 410ms

And Fill transport form 24s 796ms

And Click "save-transport" save button 711ms

And Click cancel button in transport form 077ms

And Go to transport details "LOAD" 4s 333ms

Then Check are transport values equals 4s 208ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 209ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 180ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 435ms

And Fill transport form 24s 794ms

And Click "save-transport" save button 710ms

And Click cancel button in transport form 076ms

And Go to transport details "CONTAINER" 4s 313ms

Then Check are transport values equals 4s 230ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 243ms

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 254ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_IMPORT" 4s 495ms

And Fill transport form 33s 147ms

And Click "save-transport" save button 747ms

And Click cancel button in transport form 091ms

And Go to transport details "SMALLS_IMPORT" 4s 343ms

Then Check are transport values equals 8s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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 189ms

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 271ms

And Show all transport "false" 012ms

When Go to transport details "SMALLS_EXPORT" 4s 527ms

And Fill transport form 33s 115ms

And Click "save-transport" save button 761ms

And Click cancel button in transport form 076ms

And Go to transport details "SMALLS_EXPORT" 4s 359ms

Then Check are transport values equals 8s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 157ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 336ms

And Show all transport "true" 149ms

When Go to transport details "DELIVERY" 4s 337ms

And Fill transport form 19s 655ms

And Click "save-transport" save button 708ms

And Click cancel button in transport form 094ms

And Go to transport details "DELIVERY" 4s 310ms

Then Check are transport values equals 190ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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 117ms

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 304ms

And Show all transport "true" 086ms

When Go to transport details "TRANSPORT_ORDER" 4s 476ms

And Fill transport form 26s 781ms

And Click "save-transport" save button 725ms

And Click cancel button in transport form 078ms

And Go to transport details "TRANSPORT_ORDER" 4s 347ms

Then Check are transport values equals 2s 265ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 170ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 224ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 281ms

And If user is login then logout 111ms

Then Login as "dka1-supplier" 3s 009ms

And Click button advice in transport table "LOAD" 208ms

And Check if moved to first possible start date in schedule 420ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 519ms

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 303ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 254ms

When Go to "TRANSPORT_TABLE" 118ms

And Show all transport types 1s 040ms

And Verify that transport has "0" files 037ms

Then Add file to transport by API 429ms

And Verify that transport has "1" files 684ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 083ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 180ms

When Go to "TRANSPORT_TABLE" 095ms

And Show all transport types 1s 040ms

And Verify that transport has "0" files 039ms

Then Add file to transport by API 237ms

And Verify that transport has "1" files 571ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 417ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 380ms

When Go to "TRANSPORT_TABLE" 072ms

And Show all transport types 1s 059ms

And Verify that transport has "0" files 038ms

Then Add file to transport by API 209ms

And Verify that transport has "1" files 421ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 101ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 193ms

When Go to "TRANSPORT_TABLE" 115ms

And Show all transport types 1s 046ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 221ms

And Verify that transport has "1" files 927ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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 082ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 175ms

And Delete transport 17s 682ms

When Go to "ARCHIVE_TAB" 203ms

And Show "DELIVERY" 056ms

And Verify that transport has "0" files 725ms

Then Add file to transport 161ms

And Verify that transport has "1" files 357ms

Hooks

After Hooks.deleteTransportAfterTest() 061ms

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 208ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 189ms

And Delete transport 17s 356ms

When Go to "ARCHIVE_TAB" 204ms

And Show "LOAD" 086ms

And Verify that transport has "0" files 1s 036ms

Then Add file to transport 143ms

And Verify that transport has "1" files 359ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 419ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 387ms

And Delete transport 17s 874ms

When Go to "ARCHIVE_TAB" 235ms

And Show "DELIVERY" 058ms

And Verify that transport has "0" files 999ms

Then Add file to transport 165ms

And Verify that transport has "1" files 1s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 192ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 209ms

And Delete transport 17s 534ms

When Go to "ARCHIVE_TAB" 234ms

And Show "CONTAINER" 074ms

And Verify that transport has "0" files 1s 121ms

Then Add file to transport 142ms

And Verify that transport has "1" files 448ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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" 092ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 222ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 112ms

And Set token of apiUsername "paa1-carrier@qa.qa-test" 092ms

And Accept transferred transport by Api 199ms

And Login as "paa1-carrier@qa.qa-test" 1s 062ms

Then Verify that large_entrepreneur_declaration file has been added and can be downloaded 16s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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 163ms

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 114ms

Then Verify that large_entrepreneur_declaration file has been added and can be downloaded 17s 866ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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" 092ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 189ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 159ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 368ms

And Login as "paa1-carrier@qa.qa-test" 1s 001ms

Then Verify that large_entrepreneur_declaration file has been added and can be downloaded 16s 117ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 259ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 244ms

When Go to "TRANSPORT_TABLE" 112ms

And Show all transport "true" 072ms

Then Verify that transport has "1" CMR file 1s 177ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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" 985ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 384ms

When Go to "TRANSPORT_TABLE" 081ms

And Show all transport "true" 054ms

Then Verify that transport has "2" CMR file 1s 179ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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 054ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 267ms

When Go to "TRANSPORT_TABLE" 109ms

And Show all transport "true" 092ms

Then Verify that CMR document can be downloaded 17s 469ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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 093ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 245ms

And Show all transport "true" 110ms

And Delete transport 17s 135ms

When Go to "ARCHIVE_TAB" 235ms

And Show "TRANSPORT_ORDER" 051ms

Then Verify that CMR document can be downloaded 16s 809ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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 402ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 404ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 227ms

And Click pencil and move transport to next day in schedule 16s 978ms

Then Check if transport is in new location in schedule 2s 114ms

And Check if dates in transport form are correct 3s 460ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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 175ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 325ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 250ms

And Click pencil and move transport to next day in schedule 16s 680ms

Then Check if transport is in new location in schedule 2s 130ms

And Check if dates in transport form are correct 3s 363ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 064ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 303ms

And Show all transport "false" 014ms

When Find transport pencil button in transports table 1s 233ms

And Click pencil and move transport to next day in schedule 16s 818ms

Then Check if transport is in new location in schedule 2s 133ms

And Check if dates in transport form are correct 3s 394ms

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 215ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 333ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 222ms

And Click pencil and move transport to next day in schedule 16s 361ms

Then Check if transport is in new location in schedule 2s 106ms

And Check if dates in transport form are correct 3s 359ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 176ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 372ms

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 342ms

Then Check if transport is in new location in schedule 2s 119ms

And Check if dates in transport form are correct 3s 418ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 180ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 349ms

And Show all transport "true" 079ms

When Find transport pencil button in transports table 1s 227ms

And Click pencil and move transport to next day in schedule 16s 462ms

Then Check if transport is in new location in schedule 2s 130ms

And Check if dates in transport form are correct 3s 432ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 223ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 201ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 047ms

And Click button advice in transport table "DELIVERY" 131ms

And Set advice window in schedule 2s 594ms

And Fill advice form 8s 523ms

And Click advice save button and wait for advice form to disappear 30s 744ms

And Go to "TRANSPORT_TABLE" 216ms

And Find transport pencil button in transports table 1s 222ms

And Click pencil and move transport to next day in schedule 17s 624ms

Then Check if transport is in new location in schedule 2s 107ms

And Check if dates in transport form are correct 3s 434ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 488ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 405ms

And Show all transport "false" 008ms

When Find transport pencil button in transports table 1s 203ms

And Click pencil and move transport to next day in schedule 16s 893ms

And Move advice window "3" 1s 340ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 162ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 323ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 184ms

And Click pencil and move transport to next day in schedule 16s 727ms

And Move advice window "3" 1s 380ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 039ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 332ms

And Show all transport "false" 011ms

When Find transport pencil button in transports table 1s 209ms

And Click pencil and move transport to next day in schedule 16s 962ms

And Move advice window "3" 1s 555ms

Then Check if advice window is in new location 053ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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 105ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 304ms

And Show all transport "false" 005ms

When Find transport pencil button in transports table 1s 176ms

And Click pencil and move transport to next day in schedule 16s 252ms

And Move advice window "3" 1s 316ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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 073ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 371ms

And Show all transport "false" 011ms

When Find transport pencil button in transports table 1s 221ms

And Click pencil and move transport to next day in schedule 16s 320ms

And Move advice window "3" 1s 325ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 124ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 347ms

And Show all transport "true" 074ms

When Find transport pencil button in transports table 1s 230ms

And Click pencil and move transport to next day in schedule 16s 406ms

And Move advice window "3" 1s 362ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 453ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 405ms

And Go to transport details "DELIVERY" 4s 713ms

When Open section: "discrepancy-report-panel" 1s 051ms

Then Verify that no discrepancies found label is visible in discrepancy report section 068ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 449ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 114ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 359ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 367ms

And Go to transport details "DELIVERY" 4s 724ms

And Fill transport form 36s 098ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 112ms

When Go to transport details "DELIVERY" 4s 437ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 447ms

And Click "save-transport" save button 723ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 030ms

And Verify that discrepancy report section contains validation errors 022ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 330ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 350ms

When Go to transport details "DELIVERY" 4s 695ms

Then Verify that discrepancy report section is available 039ms

And Open section: "discrepancy-report-panel" 1s 071ms

And Verify that generate new discrepancy report button is visible 039ms

Hooks

After Hooks.deleteTransportAfterTest() 155ms

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 422ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 328ms

When Go to transport details "OWN_COLLECTION" 4s 683ms

Then Verify that discrepancy report section is available 030ms

And Open section: "discrepancy-report-panel" 1s 057ms

And Verify that generate new discrepancy report button is visible 035ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 319ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 355ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 562ms

Then Verify that discrepancy report section is available 038ms

And Open section: "discrepancy-report-panel" 1s 060ms

And Verify that generate new discrepancy report button is visible 036ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 426ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 356ms

When Go to transport details "EXPORT" 5s 585ms

Then Verify that discrepancy report section is available 042ms

And Open section: "discrepancy-report-panel" 1s 064ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 434ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 160ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 755ms

Then Verify that discrepancy report section is available 024ms

And Open section: "discrepancy-report-panel" 1s 045ms

And Verify that generate new discrepancy report button is visible 037ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 352ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 313ms

When Go to transport details "CISTERN_DELIVERY" 4s 476ms

Then Verify that discrepancy report section is not available 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 465ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 266ms

When Go to transport details "CISTERN_COLLECTION" 4s 461ms

Then Verify that discrepancy report section is not available 15s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 318ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 232ms

When Go to transport details "WEIGHING" 4s 384ms

Then Verify that discrepancy report section is not available 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 504ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 330ms

When Go to "TRANSPORT_TABLE" 105ms

And Go to transport details "DELIVERY" 4s 754ms

And Change filled value in transport details "warehouseman" "select" "Błajet" "0" 3s 529ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 333ms

And Open section: "discrepancy-report-panel" 1s 070ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 36s 114ms

And Fill discrepancy report section without closing the form 19s 637ms

And Generate discrepancy report 16s 883ms

And Download discrepancy report 188ms

Then Verify that discrepancy report file has correct values 15s 162ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/15_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:49)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:238)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 476ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 336ms

When Go to "TRANSPORT_TABLE" 108ms

And Go to transport details "DELIVERY" 4s 750ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 36s 101ms

And Open section: "discrepancy-report-panel" 1s 082ms

And Fill discrepancy report section without closing the form 19s 696ms

And Generate discrepancy report 16s 236ms

And Download discrepancy report 168ms

And Verify that discrepancy report file has correct values 15s 152ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/16_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:49)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:238)
	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() 116ms

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" 091ms

And Add action authority with: "piast" "piast-admin" "LOAD" "MANAGE_UNLOAD_STEPS" "ACTIVE" 044ms

And Get "LOAD" settings from "piast" 034ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 077ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 213ms

And Login as "piast-admin" 1s 959ms

And Go to "TRANSPORT_TABLE" 156ms

When Go to transport details "LOAD" 4s 668ms

And Add step "unload" 112ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 537ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 533ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 637ms

And Go to transport details "LOAD" 4s 625ms

And Verify that transport has "3" steps 020ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.rollbackTransportTypeSettings() 046ms

After Hooks.rollbackAddedActionAuthorities() 073ms

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 401ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 241ms

When Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "SMALLS_IMPORT" 17s 098ms

Then Verify that user can't edit time range for load and unload 15s 009ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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" 096ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 370ms

And Login as "neuca-admin" 869ms

And Go to "TRANSPORT_TABLE" 200ms

And Show all transport types 15s 051ms

When Go to transport details "DELIVERY" 32s 539ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 072ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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" 095ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 410ms

And Login as "hochland-admin" 1s 237ms

And Go to "TRANSPORT_TABLE" 124ms

And Show all transport types 1s 065ms

When Go to transport details "EXPORT" 5s 483ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 062ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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" 087ms

And Get "DELIVERY" settings from "neuca" 038ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 094ms

And Login as "neuca-admin" 894ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 322ms

When Go to "TRANSPORT_TABLE" 210ms

And Go to transport details "DELIVERY" 32s 476ms

And Set number of pallets in "load" step in transport - "32" 143ms

And Check if number of pallets check message is not visible in transport form 15s 038ms

And Set number of pallets in "load" step in transport - "34" 117ms

Then Check if number of pallets check message is visible in transport form 052ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.rollbackTransportTypeSettings() 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" 093ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "MANAGE_UNLOAD_STEPS" "ACTIVE" 052ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 076ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 058ms

And Login as "farmacol-admin" 2s 473ms

And Go to new transport "EXTERNAL_DELIVERY" 291ms

And Add step "unload" 094ms

And Click "save-transport-and-close" save button 667ms

Then Verify that "time-range-from-date-2" has validation error 014ms

Then Verify that "time-range-to-date-2" has validation error 018ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 334ms

And Click "save-transport-and-close" save button 703ms

And Verify that "time-range-from-date-2" has no validation error 016ms

And Verify that "time-range-to-date-2" has no validation error 018ms

Hooks

After Hooks.deleteTransportAfterTest() 002ms

After Hooks.rollbackTransportTypeSettings() 066ms

After Hooks.rollbackAddedActionAuthorities() 044ms

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" 053ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 236ms

When Login as "piast-admin" 1s 961ms

And Go to transport details "LOAD" 4s 812ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 114ms

And Fill step data 15s 074ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 123ms

And Fill step data 5s 471ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 681ms

Then Go to transport details "LOAD" 4s 576ms

And Check if "unload" step is added as "3" step in transport form 041ms

And Check if "load" step is added as "4" step in transport form 045ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

After Hooks.rollbackAddedActionAuthorities() 036ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created by similar button has correct values

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 218ms

When Go to new transport "SMALLS_IMPORT" 413ms

And Fill transport form 36s 380ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 643ms

And Show all transport "false" 011ms

And Go to transport details "SMALLS_IMPORT" 4s 435ms

And Create transport by create similar button 30s 829ms

And Open similar transport details 258ms

Then Check are transport values equals 10s 390ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.deleteSimilarTransportAfterTest() 071ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created by similar button has correct values

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 001ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 250ms

When Go to new transport "TRANSPORT_ORDER" 381ms

And Fill transport form 30s 147ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 618ms

And Show all transport "true" 096ms

And Go to transport details "TRANSPORT_ORDER" 4s 429ms

And Create transport by create similar button 30s 812ms

And Open similar transport details 268ms

Then Check are transport values equals 19s 351ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.deleteSimilarTransportAfterTest() 067ms

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 266ms

When Go to new transport "SMALLS_IMPORT" 395ms

And Fill transport form 32s 987ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 654ms

And Go to transport details "SMALLS_IMPORT" 4s 465ms

And Go to transport print details form 3s 161ms

Then Check are transport values equals 8s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 216ms

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 234ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 381ms

And Go to transport details "SMALLS_IMPORT" 4s 455ms

Then Verify that the transport can be edited 1s 322ms

And Close transport details 15s 121ms

And If user is login then logout 109ms

And Login as "pskza1-carrier@qa.qa-test" 1s 316ms

And Go to transport details "SMALLS_IMPORT" 4s 485ms

And Verify that the transport cannot be edited 46s 337ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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 295ms

And Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 002ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 249ms

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 507ms

Then Verify that the transport can be edited 1s 302ms

And Close transport details 15s 135ms

And If user is login then logout 128ms

And Login as "pskza1-carrier@qa.qa-test" 1s 259ms

And Go to transport details "SMALLS_EXPORT" 4s 484ms

And Verify that the transport cannot be edited 46s 365ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 132ms

And Get inputs from database "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 204ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 113ms

And Go to transport details "SMALLS_IMPORT" 4s 491ms

Then Verify that the hidden data in transport are not visible 1s 042ms

And Close transport details 15s 117ms

And If user is login then logout 104ms

And Login as "swisskrono-admin" 2s 104ms

And Go to transport details "SMALLS_IMPORT" 4s 499ms

And Verify that the hidden data in transport are visible 1s 251ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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 095ms

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 213ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 127ms

And Go to transport details "SMALLS_EXPORT" 4s 456ms

Then Verify that the hidden data in transport are not visible 1s 045ms

And Close transport details 15s 099ms

And If user is login then logout 124ms

And Login as "swisskrono-admin" 1s 363ms

And Go to transport details "SMALLS_EXPORT" 4s 510ms

And Verify that the hidden data in transport are visible 1s 246ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 584ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 476ms

When Go to transport details "DELIVERY" 4s 726ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 329ms

And Change filled value in transport details "warehouseman" "select" "Błajet" "0" 3s 526ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 519ms

And Fill discrepancy report section without closing the form 19s 662ms

And Click "save-transport" save button 1s 241ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 109ms

And Check if transport details form is disappeared 15s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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" 093ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 089ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 325ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 422ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 3s 790ms

When Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "DELIVERY" 4s 695ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 342ms

Then Verify that "transport-description" in transport has value "opis" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

After Hooks.rollbackAddedActionAuthorities() 062ms

After Hooks.rollbackWarehousesAccess() 152ms

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" 090ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 411ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 068ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 127ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 862ms

When Go to "TRANSPORT_TABLE" 161ms

And Go to transport details "DELIVERY" 4s 697ms

Then Verify that "transport-description" in transport form is disabled 025ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.rollbackRemovedActionAuthorities() 038ms

After Hooks.rollbackWarehousesAccess() 121ms

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" 105ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 054ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 387ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 952ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 146ms

And Go to transport details "DELIVERY" 4s 698ms

Then Verify that "CARRIER" in transport form is visible 049ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.rollbackAddedActionAuthorities() 033ms

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" 097ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 042ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 245ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 202ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 087ms

And Go to transport details "TRANSPORT" 4s 423ms

Then Verify that "CARRIER" in transport form is visible 036ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.rollbackAddedActionAuthorities() 038ms

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" 093ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 281ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 610ms

And Show all transport "true" 071ms

When Go to "TRANSPORT_TABLE" 081ms

And Go to transport details "TRANSPORT_ORDER" 4s 447ms

Then Verify that "CARRIER" in transport form is visible 035ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.rollbackAddedActionAuthorities() 043ms

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" 087ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 036ms

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 774ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 157ms

And Go to transport details "DELIVERY" 4s 798ms

Then Verify that "CARRIER" in transport form is not visible 15s 021ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

After Hooks.rollbackRemovedActionAuthorities() 045ms

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" 101ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 042ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 238ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 291ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 103ms

And Go to transport details "TRANSPORT" 4s 453ms

Then Verify that "CARRIER" in transport form is not visible 15s 051ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.rollbackRemovedActionAuthorities() 051ms

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" 088ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 039ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 264ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 092ms

And Show all transport "true" 064ms

When Go to "TRANSPORT_TABLE" 106ms

And Go to transport details "TRANSPORT_ORDER" 4s 451ms

Then Verify that "CARRIER" in transport form is not visible 15s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackRemovedActionAuthorities() 044ms

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" 093ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 067ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 036ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 378ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 542ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 177ms

And Go to transport details "DELIVERY" 4s 787ms

Then Verify that "CARRIER" in transport form is not disabled 032ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackAddedActionAuthorities() 075ms

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" 093ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 037ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 213ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 574ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 086ms

And Go to transport details "TRANSPORT" 4s 444ms

Then Verify that "CARRIER" in transport form is not disabled 032ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackAddedActionAuthorities() 069ms

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" 090ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 039ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 041ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 225ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 940ms

And Show all transport "true" 072ms

When Go to "TRANSPORT_TABLE" 078ms

And Go to transport details "TRANSPORT_ORDER" 4s 472ms

Then Verify that "CARRIER" in transport form is not disabled 018ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

After Hooks.rollbackAddedActionAuthorities() 058ms

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" 088ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 036ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 038ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 352ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 565ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 145ms

And Go to transport details "DELIVERY" 4s 640ms

Then Verify that "CARRIER" in transport form is disabled 030ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.rollbackAddedActionAuthorities() 035ms

After Hooks.rollbackRemovedActionAuthorities() 047ms

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" 094ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 046ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 006ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 212ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 086ms

And Go to transport details "TRANSPORT" 4s 425ms

Then Verify that "CARRIER" in transport form is disabled 026ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.rollbackAddedActionAuthorities() 033ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

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" 094ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 037ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 007ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 209ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 857ms

And Show all transport "true" 070ms

When Go to "TRANSPORT_TABLE" 082ms

And Go to transport details "TRANSPORT_ORDER" 4s 444ms

Then Verify that "CARRIER" in transport form is disabled 030ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.rollbackAddedActionAuthorities() 033ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

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" 090ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 310ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 045ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 041ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 045ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 850ms

When Find transport in table with status "planned" 1s 234ms

And Confirm statuses until reach "process-ended" 10s 324ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm btn-primary btn-wide'] (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-128-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.HTNPhK}, 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=88.0.4324.146, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 37b3d5450ca09b5282c2bf51a930345b
	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:197)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:327)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:317)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:59)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Transport/TransportForm/TransportForm.feature:190)

And Wait "90" seconds 000ms

And Go to "ARCHIVE_TAB" 000ms

And Show "DELIVERY" 000ms

And Go to transport details "DELIVERY" 000ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Wait "7" seconds 000ms

And Go to transport details "DELIVERY" 000ms

Then Verify that "transport-description" in transport has value "opis" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackAddedActionAuthorities() 030ms

After Hooks.rollbackRemovedActionAuthorities() 076ms

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" 2s 768ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 340ms

When Go to transport details "DELIVERY" 4s 666ms

And Fill transport form 36s 017ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 374ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 141ms

And Go to new transport "DELIVERY" 286ms

Then Verify that driver "XXX ZZZ" is in list 693ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 211ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 217ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 205ms

And If user is login then logout 078ms

And Login as "pskza1-carrier@qa.qa-test" 1s 119ms

Then Verify that the transport has been transferred 1s 133ms

And Accept or reject "accept" transferred transport 15s 774ms

And Go to transport details "SMALLS_IMPORT" 4s 555ms

And Verify that "transaction-price" in transport form is visible 040ms

And Verify that transaction price field has correct value 023ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 043ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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 283ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 239ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 204ms

And If user is login then logout 089ms

And Login as "pskza1-carrier@qa.qa-test" 1s 151ms

Then Verify that the transport has been transferred 1s 131ms

And Accept or reject "accept" transferred transport 15s 781ms

And Go to transport details "SMALLS_EXPORT" 4s 506ms

And Verify that "transaction-price" in transport form is visible 033ms

And Verify that transaction price field has correct value 038ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport details button is not shown

Steps

Given Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 020ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 433ms

And Show all transport types 1s 037ms

Then Check if transport number is visible "DELIVERY" 30s 080ms

Error message

java.lang.AssertionError: Nie znaleziono na stronie elementu transport-details-button
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.TransportFormTest.checkIfTransportNumberIsVisible(TransportFormTest.java:53)
	at ✽.Check if transport number is visible "DELIVERY"(file:Features/Atom/Transport/TransportTable/TransportTable.feature:8)

And Check if transport details is not visible 000ms

Hooks

After Hooks.deleteTransportAfterTest() 185ms

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 392ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 329ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 120ms

When Accept or reject "accept" transferred transport 17s 701ms

Then Verify that transport is accept or reject "accept" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 159ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 223ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 069ms

When Accept or reject "reject" transferred transport 17s 015ms

Then Verify that transport is accept or reject "reject" 15s 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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 161ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 235ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 125ms

When Accept or reject "accept" transferred transport 17s 957ms

Then Verify that transport is accept or reject "accept" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 188ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 223ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 065ms

When Accept or reject "reject" transferred transport 17s 975ms

Then Verify that transport is accept or reject "reject" 15s 021ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 246ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 228ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 065ms

When Accept or reject "accept" transferred transport 18s 099ms

Then Verify that transport is accept or reject "accept" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 276ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 257ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 083ms

When Accept or reject "reject" transferred transport 18s 004ms

Then Verify that transport is accept or reject "reject" 15s 065ms

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" 3s 090ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 178ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 271ms

And If user is login then logout 119ms

And Login as "paa1-carrier@qa.qa-test" 1s 263ms

Then Verify that the transport has been transferred with "true" 1s 223ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 068ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 217ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 186ms

And If user is login then logout 103ms

And Login as "paa1-carrier@qa.qa-test" 1s 164ms

Then Verify that the transport has been transferred with "false" 1s 248ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 120ms

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 093ms

And If user is login then logout 103ms

And Login as "pskza1-carrier@qa.qa-test" 1s 178ms

Then Verify that the transport has been transferred 1s 126ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 232ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 217ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 139ms

And If user is login then logout 087ms

And Login as "pskza1-carrier@qa.qa-test" 1s 226ms

Then Verify that the transport has been transferred 1s 125ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 043ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 233ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 170ms

And Go to auction offer 1s 210ms

When Offer "1000" 124ms

And Verify that offer with "1000" has been added to auction 3s 033ms

And If user is login then logout 069ms

And Login as "swisskrono-admin" 1s 281ms

Then Go to auction details 1s 200ms

And Pass transport to carrier from auction details 1s 257ms

And If user is login then logout 424ms

And Login as "pskza1-carrier@qa.qa-test" 1s 225ms

And Verify that the transport has been transferred 1s 112ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 031ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 198ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 112ms

And Go to auction offer 1s 210ms

When Offer "1000" 121ms

And Verify that offer with "1000" has been added to auction 3s 040ms

And Wait till auction end 1m 54s 015ms

And If user is login then logout 109ms

Then Login as "swisskrono-admin" 1s 507ms

And Go to auction details 1s 198ms

And Pass transport to carrier from auction details 1s 283ms

And If user is login then logout 405ms

And Login as "pskza1-carrier@qa.qa-test" 1s 278ms

And Verify that the transport has been transferred 1s 138ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 094ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 235ms

And Go to "TRANSPORT_TABLE" 118ms

When Open transport transfer modal 1s 242ms

Then Verify that all enabled companies from "swisskrono" are shown in select 128ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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" 098ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 891ms

And Login as "adama-admin" 955ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 213ms

And Go to "TRANSPORT_TABLE" 105ms

When Open transport transfer modal 1s 259ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 109ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.rollbackRejectedSections() 133ms

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 082ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 442ms

When Go to "TRANSPORT_TABLE" 111ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 443ms

Then Check if new assortment group is disabled in transport form 025ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 092ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 212ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 002ms

When Show all transport types 1s 052ms

And Click button advice in transport table "CONTAINER" 102ms

And Set advice window in schedule 2s 484ms

And Click button cancel in advice form 15s 331ms

And Set advice window in schedule 2s 126ms

And Click button cancel in advice form 15s 258ms

And Set advice window in schedule 2s 108ms

And Fill advice form 15s 620ms

And Click advice save button and wait for advice form to disappear 31s 191ms

And Go to "TRANSPORT_TABLE" 179ms

And Go to transport details "CONTAINER" 4s 441ms

Then Check are advice values equals 2s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 113ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 002ms

When Go to new transport "TRANSPORT" 364ms

And Fill transport form 26s 811ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 616ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 22s 839ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 122ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 937ms

And Accept or reject "reject" transferred transport 15s 870ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 059ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 106ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 273ms

And Accept or reject "accept" transferred transport 16s 058ms

Then Verify that transport is accept or reject "accept" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 107ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 001ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 322ms

When Show all transport types 1s 045ms

And Click button advice in transport table "DELIVERY" 140ms

And Set advice window in schedule 2s 635ms

And Click button cancel in advice form 15s 374ms

And Go to "TRANSPORT_TABLE" 185ms

When Go to transport details "DELIVERY" 4s 518ms

And Fill transport form 1m 2s 391ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 173ms

And Go to transport details "DELIVERY" 4s 444ms

Then Check are transport values equals 132ms

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:267)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Scenario/TransportTransfer.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 117ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3304	56	144	0	0	3504	324	56	380	5h 8m 15s 242ms	Failed

Tag Report