Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.415	08 maj 2021, 06:12

	Steps	Scenarios	Features
@deleteTransportAfterTest	3400	40	91	0	0	3531	346	41	387	5h 49m 10s 583ms	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" 3s 285ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 4s 488ms

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

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

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

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

And Fill advice form 16s 934ms

And Click advice save button to check error message 097ms

Then Check if possible advice alert is displayed 054ms

Hooks

After Hooks.deleteTransportAfterTest() 621ms

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

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

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

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

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

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

And Fill advice form 8s 493ms

And Click advice save button to check error message 077ms

Then Check if possible advice alert is displayed 016ms

Hooks

After Hooks.deleteTransportAfterTest() 194ms

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

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

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

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

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

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

And Fill advice form 8s 484ms

And Click advice save button to check error message 084ms

Then Check if possible advice alert is displayed 014ms

Hooks

After Hooks.deleteTransportAfterTest() 221ms

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

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

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

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

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

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

And Fill advice form 13s 370ms

And Click advice save button to check error message 061ms

Then Check if possible advice alert is displayed 014ms

Hooks

After Hooks.deleteTransportAfterTest() 215ms

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

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

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

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

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

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

And Fill advice form 13s 370ms

And Click advice save button to check error message 057ms

Then Check if possible advice alert is displayed 013ms

Hooks

After Hooks.deleteTransportAfterTest() 172ms

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

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

And Show all transport types 1s 032ms

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

And Go to "TRANSPORT_TABLE" 174ms

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

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

And Fill transport form 4s 717ms

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

And Expand advice panel 099ms

And Edit advice in transport details 12s 459ms

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

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

And Expand advice panel 092ms

Then Check are advice values equals after edition 187ms

Hooks

After Hooks.deleteTransportAfterTest() 175ms

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

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

And Show all transport types 1s 035ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 42s 527ms

And Go to "TRANSPORT_TABLE" 263ms

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

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

And Fill transport form 1m 2s 097ms

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

And Expand advice panel 082ms

And Edit advice in transport details 6s 588ms

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

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

And Expand advice panel 088ms

Then Check are advice values equals after edition 090ms

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

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

And Show all transport types 1s 032ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-piast" 42s 196ms

And Go to "TRANSPORT_TABLE" 235ms

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

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

And Fill transport form 57s 066ms

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

And Expand advice panel 090ms

And Edit advice in transport details 6s 666ms

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

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

And Expand advice panel 078ms

Then Check are advice values equals after edition 073ms

Hooks

After Hooks.deleteTransportAfterTest() 250ms

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

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

And Show all transport types 1s 057ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

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

And Fill transport form 24s 594ms

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

And Expand advice panel 095ms

And Edit advice in transport details 18s 357ms

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

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

And Expand advice panel 095ms

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

Hooks

After Hooks.deleteTransportAfterTest() 239ms

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

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

And Show all transport types 1s 045ms

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

And Go to "TRANSPORT_TABLE" 164ms

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

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

And Fill transport form 24s 653ms

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

And Expand advice panel 105ms

And Edit advice in transport details 18s 511ms

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

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

And Expand advice panel 156ms

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

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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

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

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

When Show all transport types 1s 032ms

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

And Set advice window in schedule 2s 496ms

And Fill advice form 12s 336ms

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

And Go to "TRANSPORT_TABLE" 228ms

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

Then Check are advice values equals 302ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 6s 501ms

And Fill advice form 11s 775ms

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

And Go to "TRANSPORT_TABLE" 181ms

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

Then Check are advice values equals 2s 271ms

Hooks

After Hooks.deleteTransportAfterTest() 178ms

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

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

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

When Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 754ms

And Fill advice form 8s 453ms

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

And Go to "TRANSPORT_TABLE" 225ms

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

Then Check are advice values equals 194ms

Hooks

After Hooks.deleteTransportAfterTest() 239ms

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

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

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

When Show all transport types 1s 033ms

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

And Set advice window in schedule 2s 652ms

And Fill advice form 8s 302ms

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

And Go to "TRANSPORT_TABLE" 168ms

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

Then Check are advice values equals 266ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

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

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

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

When Show all transport types 1s 028ms

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

And Set advice window in schedule 2s 511ms

And Fill advice form 13s 123ms

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

And Go to "TRANSPORT_TABLE" 158ms

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

Then Check are advice values equals 2s 263ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 465ms

And Fill advice form 13s 264ms

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

And Go to "TRANSPORT_TABLE" 167ms

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

Then Check are advice values equals 2s 299ms

Hooks

After Hooks.deleteTransportAfterTest() 219ms

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 Set token of apiUsername "super-admin-adama" 110ms

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

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

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

And Accept transferred transport by Api 410ms

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

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

When Show all transport types 1s 376ms

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

And Set advice window in schedule 2s 586ms

And Fill advice form 11s 889ms

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

And Go to "TRANSPORT_TABLE" 273ms

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

Then Check are advice values equals 2s 267ms

Hooks

After Hooks.deleteTransportAfterTest() 180ms

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 Set token of apiUsername "super-admin-skz" 108ms

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

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

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

And Accept transferred transport by Api 290ms

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

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

When Show all transport types 1s 109ms

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

And Set advice window in schedule 2s 747ms

And Fill advice form 14s 415ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

Then Check are advice values equals 2s 570ms

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 Set token of apiUsername "super-admin-skz" 108ms

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

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

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

And Accept transferred transport by Api 124ms

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

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

When Show all transport types 1s 156ms

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

And Set advice window in schedule 2s 650ms

And Fill advice form 14s 563ms

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

And Go to "TRANSPORT_TABLE" 181ms

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

Then Check are advice values equals 2s 313ms

Hooks

After Hooks.deleteTransportAfterTest() 265ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Accept transferred transport by Api 133ms

And Login as "paa1-carrier@qa.qa-test" 1s 559ms

When Show all transport types 1s 327ms

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

And Set week view 1s 667ms

And Show yesterday 1s 065ms

Then Check if advice restriction blockade windows are visible 021ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Accept transferred transport by Api 133ms

And Login as "pskza1-carrier@qa.qa-test" 1s 204ms

When Show all transport types 1s 121ms

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

And Set week view 2s 458ms

And Show yesterday 1s 100ms

Then Check if advice restriction blockade windows are visible 120ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 15s 254ms

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

And Accept transferred transport by Api 123ms

And Login as "pskza1-carrier@qa.qa-test" 1s 614ms

When Show all transport types 1s 108ms

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

And Set week view 2s 090ms

And Show yesterday 1s 125ms

Then Check if advice restriction blockade windows are visible 096ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 040ms

And Click on time window date 1s 331ms

And Select view "DAYS_4" 2s 056ms

And Move advice window "3" 1s 317ms

Then Check if advice window is in new location 018ms

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

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

And Show all transport "false" 013ms

And Click on time window date 15s 794ms

And Select view "DAYS_4" 2s 062ms

And Move advice window "3" 1s 557ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 011ms

And Click on time window date 15s 529ms

And Select view "DAYS_4" 2s 063ms

And Move advice window "3" 1s 360ms

Then Check if advice window is in new location 021ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 010ms

And Click on time window date 1s 688ms

And Select view "DAYS_4" 2s 047ms

And Move advice window "3" 1s 339ms

Then Check if advice window is in new location 012ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 423ms

And Select view "DAYS_4" 2s 049ms

And Move advice window "3" 1s 280ms

Then Check if advice window is in new location 017ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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

And Show all transport "true" 098ms

And Click on time window date 1s 454ms

And Select view "DAYS_4" 2s 049ms

And Move advice window "3" 1s 383ms

Then Check if advice window is in new location 017ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

When Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 798ms

And Fill advice form 8s 297ms

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

And Go to "TRANSPORT_TABLE" 217ms

And Click on time window date 1s 434ms

And Select view "DAYS_4" 2s 049ms

And Move advice window "3" 1s 416ms

Then Check if advice window is in new location 019ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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

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

And Go to "TRANSPORT_TABLE" 134ms

And Show all transport types 1s 029ms

And Click on time window date 1s 441ms

And Scroll to time window "adviceWindow" 035ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 153ms

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

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

And Go to "TRANSPORT_TABLE" 104ms

And Show all transport types 1s 037ms

And Click on time window date 1s 480ms

And Scroll to time window "adviceWindow" 028ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

And Go to "TRANSPORT_TABLE" 094ms

And Show all transport types 1s 028ms

And Click on time window date 1s 385ms

And Scroll to time window "adviceWindow" 028ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

And Go to "TRANSPORT_TABLE" 277ms

And Show all transport types 15s 060ms

And Click on time window date 15s 999ms

And Scroll to time window "adviceWindow" 034ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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

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

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

When Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 658ms

And Fill advice form 8s 410ms

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

And Go to "TRANSPORT_TABLE" 264ms

And Click on time window date 1s 423ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Go to "WAREHOUSE_TAB" 938ms

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

When Go to new transport "DELIVERY" 407ms

And Fill transport form 39s 839ms

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

And Click previous page button in browser 017ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Go to "WAREHOUSE_TAB" 780ms

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

When Go to new transport "DELIVERY" 420ms

And Fill transport form 39s 665ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

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

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

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

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

When Show all transport types 1s 036ms

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

And Fill advice form 11s 570ms

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

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

And Open statuses popup 201ms

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

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

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

And Login as "farmacol-admin" 1s 381ms

And Go to "WAREHOUSE_TAB" 856ms

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

And Set week view 2s 206ms

And Move cursor over time window element 399ms

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

Hooks

After Hooks.deleteTransportAfterTest() 148ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 34s 243ms

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

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

And Set advice window in schedule 2s 121ms

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

Then Go to "OWN_COMPANY_TAB" 235ms

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

Hooks

After Hooks.deleteTransportAfterTest() 171ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 16s 296ms

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

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

And Set advice window in schedule 2s 135ms

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

Then Go to "OWN_COMPANY_TAB" 284ms

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

Hooks

After Hooks.deleteTransportAfterTest() 141ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 197ms

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

And Show all transport types 1s 071ms

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 192ms

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

And Show all transport types 1s 063ms

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

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 092ms

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

And Show all transport types 1s 057ms

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 129ms

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

And Show all transport types 1s 073ms

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 093ms

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

When Go to "ARCHIVE_TAB" 188ms

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

And Show "SMALLS_IMPORT" 065ms

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

Hooks

After Hooks.deleteTransportAfterTest() 137ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 15s 291ms

And Delete created transport by API 075ms

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

When Go to "ARCHIVE_TAB" 235ms

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

And Show "SMALLS_IMPORT" 067ms

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

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 15s 328ms

And Delete created transport by API 164ms

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

When Go to "ARCHIVE_TAB" 225ms

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

And Show "SMALLS_IMPORT" 071ms

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

Hooks

After Hooks.deleteTransportAfterTest() 188ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 15s 271ms

And Delete created transport by API 311ms

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

When Go to "ARCHIVE_TAB" 243ms

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

And Show "SMALLS_IMPORT" 059ms

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

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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

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

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

And Go to "TRANSPORT_TABLE" 113ms

And Show all transport "true" 075ms

And Select transportType "TRANSPORT_ORDER" 1s 136ms

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

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 199ms

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

And Toggle transport table days limit filter 084ms

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

When Go to "TRANSPORT_TABLE" 110ms

And Go to auction form 1s 259ms

And Select contractors group "Kraj" 074ms

Then Verify that carrier "PSKZA1" is selected 018ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.removeContractorsGroup() 074ms

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

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

When Go to "TRANSPORT_TABLE" 095ms

And Go to auction form 1s 200ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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

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

When Go to "TRANSPORT_TABLE" 089ms

And Go to auction form 1s 281ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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

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

And Show all transport "false" 015ms

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

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

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

And Expand index panel 105ms

And Click add index button 114ms

And Fill index form 10s 480ms

And Click ok button in index form 15s 155ms

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

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

And Expand index panel 106ms

Then Check are transport values equals 068ms

Hooks

After Hooks.deleteTransportAfterTest() 170ms

After Hooks.deleteProductAfterTest() 081ms

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

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

And Show all transport "true" 066ms

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

And Expand index panel 087ms

And Click add index button 117ms

And Fill index form 7s 420ms

And Click ok button in index form 15s 118ms

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

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

And Expand index panel 106ms

Then Check are transport values equals 2s 097ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

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

And Show all transport "false" 008ms

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

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

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

And Add index to transport 25s 806ms

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

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

And Expand index panel 098ms

And Click delete index button 079ms

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

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

And Expand index panel 081ms

Then Verify that transport has no indexes 15s 050ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.deleteProductAfterTest() 047ms

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

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

And Show all transport "true" 065ms

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

And Add index to transport 22s 745ms

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

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

And Expand index panel 116ms

And Click delete index button 057ms

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

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

And Expand index panel 079ms

Then Verify that transport has no indexes 15s 002ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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

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

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

And Add index to transport 24s 467ms

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

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

When Click on index details icon 090ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.deleteProductAfterTest() 070ms

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

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

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

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

And Show all transport types 1s 032ms

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

And Set advice window in schedule 2s 495ms

And Fill advice form 11s 613ms

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

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

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 209ms

After Hooks.cleanUserDetailsAfterTest() 112ms

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

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 729ms

And Fill advice form 8s 290ms

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

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

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 149ms

After Hooks.cleanUserDetailsAfterTest() 145ms

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

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

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 489ms

And Fill advice form 13s 159ms

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

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

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 132ms

After Hooks.cleanUserDetailsAfterTest() 224ms

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

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

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

And Show all transport types 1s 035ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 44s 895ms

And Go to "TRANSPORT_TABLE" 186ms

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

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

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

And Fill transport form 4s 689ms

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

And Expand advice panel 086ms

And Edit advice in transport details 12s 205ms

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

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

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 162ms

After Hooks.cleanUserDetailsAfterTest() 119ms

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

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

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

And Show all transport types 1s 041ms

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

And Go to "TRANSPORT_TABLE" 214ms

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

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

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

And Fill transport form 1m 1s 935ms

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

And Expand advice panel 115ms

And Edit advice in transport details 6s 630ms

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

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

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 123ms

After Hooks.cleanUserDetailsAfterTest() 134ms

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

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

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

And Show all transport types 1s 038ms

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

And Go to "TRANSPORT_TABLE" 147ms

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

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

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

And Fill transport form 24s 651ms

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

And Expand advice panel 099ms

And Edit advice in transport details 18s 419ms

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

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

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 176ms

After Hooks.cleanUserDetailsAfterTest() 122ms

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wjazd na teren zakładu" 3m 18s 500ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:53)

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 380ms

After Hooks.cleanUserDetailsAfterTest() 150ms

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

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

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updatePartnership(ApolloUpdateDbService.java:27)
	at CucumberTests.Company.EditCompanyTest.prepareCompanyVerificationMailSetting(EditCompanyTest.java:122)
	at ✽.Prepare company "Dostawca Hochland Automat 1" verification email setting "48h"(file:Features/Atom/Mail/AdviceMail.feature:64)

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

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

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

And Wait "120" seconds 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.cleanUserDetailsAfterTest() 000ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.editJsonTextNode(JsonApiUtil.java:141)
	at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:308)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

After Hooks.rollbackVerificationEmailSettingAfterTest() 003ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updatePartnership(ApolloUpdateDbService.java:27)
	at CucumberTests.Hooks.rollbackVerificationEmailSettingAfterTest(Hooks.java:553)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 166ms

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

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 3m 17s 333ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AuctionMail.feature:25)

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.cleanUserDetailsAfterTest() 103ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Steps

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

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

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

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

Error message

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

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApi(AuctionTransport.java:61)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"(file:Features/Atom/Mail/AuctionMail.feature:35)

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

And Wait till auction end 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 151ms

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

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

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

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

Error message

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

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApi(AuctionTransport.java:61)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"(file:Features/Atom/Mail/AuctionMail.feature:49)

And Wait till auction end 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.cleanUserDetailsAfterTest() 100ms

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

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

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

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

Error message

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

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApi(AuctionTransport.java:61)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"(file:Features/Atom/Mail/AuctionMail.feature:62)

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

After Hooks.cleanUserDetailsAfterTest() 103ms

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

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

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

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

Error message

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

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApi(AuctionTransport.java:61)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"(file:Features/Atom/Mail/AuctionMail.feature:76)

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 111ms

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

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

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

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

Error message

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

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApi(AuctionTransport.java:61)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"(file:Features/Atom/Mail/AuctionMail.feature:90)

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.cleanUserDetailsAfterTest() 147ms

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

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

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

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

Error message

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

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

And Wait "90" seconds 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.cleanUserDetailsAfterTest() 103ms

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

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

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

And Go to "TRANSPORT_TABLE" 130ms

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

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

And Fill transport form 35s 686ms

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

And Fill discrepancy report section 35s 680ms

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

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

And Generate discrepancy report 17s 752ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Utworzono protokół niezgodności" 3m 16s 028ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/DiscrepancyReportMail.feature:18)

Hooks

After Hooks.deleteTransportAfterTest() 150ms

After Hooks.cleanUserDetailsAfterTest() 215ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 757ms

And Select warehouse "Serownia" 1s 385ms

And Set week view 1s 074ms

And Show yesterday 1s 077ms

And Move window into the past 311ms

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

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 148ms

After Hooks.cleanUserDetailsAfterTest() 298ms

After Hooks.rollbackAddedAuthorities() 038ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica import" 3m 14s 909ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:26)

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.cleanUserDetailsAfterTest() 140ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica eksport" 3m 19s 579ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:26)

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 153ms

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 3m 16s 224ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportTransferMail.feature:10)

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 160ms

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

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

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 "false" 19s 168ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zostało przekazane nowe zlecenie" 3m 50s 489ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportTransferMail.feature:22)

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 107ms

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 3m 18s 845ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportTransferMail.feature:34)

Hooks

After Hooks.deleteTransportAfterTest() 131ms

After Hooks.cleanUserDetailsAfterTest() 298ms

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

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

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

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

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

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

Then If user is login then logout 086ms

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

And Go to auction details 1s 222ms

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 3m 18s 724ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportTransferMail.feature:52)

Hooks

After Hooks.deleteTransportAfterTest() 198ms

After Hooks.cleanUserDetailsAfterTest() 175ms

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

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

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

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nowe zapytanie ofertowe" 3m 18s 255ms

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:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportTransferMail.feature:64)

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.cleanUserDetailsAfterTest() 136ms

View Feature Pallet limit

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 40s 691ms

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

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

And Set advice window in schedule 2s 159ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Pallet limit

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 222ms

And Show all transport "false" 007ms

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

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

And Click "save-transport" save button 763ms

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 091ms

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

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

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

And Go to "TRANSPORT_TABLE" 133ms

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

And Set advice window in schedule 2s 793ms

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.deleteModeOfTransportationAfterTest() 074ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "DISABLED" 097ms

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

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

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

And Go to "TRANSPORT_TABLE" 189ms

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

And Set advice window in schedule 2s 836ms

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

Hooks

After Hooks.deleteTransportAfterTest() 073ms

After Hooks.deleteModeOfTransportationAfterTest() 078ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "ACCEPTED" 072ms

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

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

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

And Go to "TRANSPORT_TABLE" 191ms

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

And Set advice window in schedule 2s 805ms

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

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.deleteModeOfTransportationAfterTest() 089ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "UPDATED" 077ms

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

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

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

And Go to "TRANSPORT_TABLE" 200ms

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

And Set advice window in schedule 3s 087ms

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.deleteModeOfTransportationAfterTest() 087ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "REJECTED" 091ms

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

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

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

And Go to "TRANSPORT_TABLE" 228ms

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

And Set advice window in schedule 2s 876ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.deleteModeOfTransportationAfterTest() 090ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "BLOCKED" 068ms

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

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

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

And Go to "TRANSPORT_TABLE" 193ms

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

And Set advice window in schedule 2s 804ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.deleteModeOfTransportationAfterTest() 072ms

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

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

And Add transport by SKApi in "MGW" 217ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 958ms

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

And Set advice window in schedule 2s 661ms

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

And Fill advice form 14s 679ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 112ms

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

Then Check are transport values equals 327ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 002ms

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

And Go to "TRANSPORT_TABLE" 129ms

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

Then Check are transport values equals 320ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 51s 994ms

And Go to "TRANSPORT_TABLE" 111ms

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

Then Check are transport values equals 311ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

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

When Add transport by SKApi in "HRL" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 52s 035ms

And Go to "TRANSPORT_TABLE" 150ms

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

Then Check are transport values equals 377ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

When Add transport by SKApi in "HRL" 003ms

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

And Go to "TRANSPORT_TABLE" 115ms

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

Then Check are transport values equals 350ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 125ms

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

Then Check are transport values equals 381ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" 002ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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

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

When Add transport by SKApi in "" 002ms

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

And Go to "TRANSPORT_TABLE" 109ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Set advice window in schedule 2s 807ms

And Fill advice form 14s 751ms

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

And Go to "TRANSPORT_TABLE" 180ms

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

Then Check are advice values equals 2s 287ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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

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

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

And Set advice window in schedule 2s 798ms

And Fill advice form 14s 570ms

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

And Go to "TRANSPORT_TABLE" 146ms

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

Then Check are advice values equals 2s 285ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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

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

Steps

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

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

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

And Set advice window in schedule 2s 833ms

And Fill advice form 14s 482ms

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

And Go to "TRANSPORT_TABLE" 218ms

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

Then Check are advice values equals 2s 284ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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

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

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

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

And Set advice window in schedule 3s 101ms

And Fill advice form 14s 474ms

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

And Go to "TRANSPORT_TABLE" 176ms

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

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

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

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

And Set advice window in schedule 2s 739ms

And Fill advice form 14s 625ms

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

And Go to "TRANSPORT_TABLE" 178ms

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Verify that advice data are saved properly

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

Steps

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

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

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

And Set advice window in schedule 2s 742ms

And Fill advice form 14s 524ms

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

And Go to "TRANSPORT_TABLE" 202ms

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

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

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

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

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

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

And Fill advice form 14s 487ms

And Click advice save button to check error message 067ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 42s 469ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

And Expand advice panel 107ms

And Edit advice in transport details 13s 999ms

And Fill arrival date field 2s 284ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 205ms

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

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

And Add transport by SKApi in "MGW" 001ms

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

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

And Go to "TRANSPORT_TABLE" 169ms

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

And Expand advice panel 099ms

And Edit advice in transport details 13s 960ms

And Fill arrival date field 2s 257ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 228ms

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

And Expand advice panel 108ms

And Edit advice in transport details 14s 110ms

And Fill arrival date field 2s 280ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 865ms

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

And Select view "DAYS_2" 2s 082ms

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

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

And Select view "DAYS_2" 2s 036ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 208ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 817ms

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

And Select view "DAYS_2" 2s 073ms

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

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

And Select view "DAYS_2" 2s 039ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 172ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 758ms

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

And Select view "DAYS_2" 2s 070ms

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

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

And Select view "DAYS_2" 2s 044ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 136ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 471ms

And Select warehouse "MGW" 1s 180ms

And Select view "DAYS_2" 2s 070ms

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

And Select warehouse "HRL" 1s 430ms

And Select view "DAYS_2" 2s 033ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 166ms

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

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

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

And Confirm statuses until reach "process-ended" 27s 975ms

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

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

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

And Confirm statuses until reach "process-ended" 22s 176ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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

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

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

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

Then Check if transport has "departed" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

And Confirm statuses until reach "process-ended" 12s 361ms

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

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

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

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

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

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

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

And Set advice window in schedule 2s 719ms

And Fill advice form 14s 485ms

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

And Check if window is "silver" 2s 019ms

And Go to "TRANSPORT_TABLE" 199ms

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

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

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

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

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

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

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

And Set advice window in schedule 2s 669ms

And Fill advice form 14s 447ms

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

And Check if window is "silver" 2s 028ms

And Go to "TRANSPORT_TABLE" 183ms

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

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

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

And Find transport in table with status "advice-added" 3s 340ms

And Confirm statuses until reach "arrived" 3s 792ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.rollbackAddedActionAuthorities() 059ms

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

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

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

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

And Confirm statuses until reach "arrived" 3s 748ms

And Check if transport row is "green" 3s 055ms

And Confirm statuses until reach "during-unload" 3s 710ms

Then Check if transport row is "orange" 3s 055ms

And Confirm statuses until reach "unloaded" 3s 732ms

Then Check if transport row is "darkgoldenrod" 3s 049ms

And Confirm statuses until reach "process-ended" 18s 717ms

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 640ms

And Fill advice form 8s 250ms

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

And Go to "TRANSPORT_TABLE" 201ms

And Find transport in table with status "advice-added" 3s 161ms

And Confirm statuses until reach "left-the-area" 17s 226ms

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

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

And Show all transport types 1s 029ms

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

And Set advice window in schedule 2s 582ms

And Fill advice form 8s 310ms

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

And Go to "TRANSPORT_TABLE" 176ms

And Find transport in table with status "advice-added" 3s 192ms

And Confirm statuses until reach "left-the-area" 17s 250ms

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

And Show all transport types 1s 031ms

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

And Set advice window in schedule 2s 661ms

And Fill advice form 8s 409ms

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

And Go to "TRANSPORT_TABLE" 206ms

And Find transport in table with status "advice-added" 3s 172ms

When Add file to transport by API 516ms

And Confirm statuses until reach "process-ended" 34s 918ms

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

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 603ms

And Fill advice form 8s 333ms

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

And Go to "TRANSPORT_TABLE" 187ms

And Find transport in table with status "advice-added" 3s 201ms

When Add file to transport by API 277ms

And Confirm statuses until reach "process-ended" 35s 010ms

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

Hooks

After Hooks.deleteTransportAfterTest() 153ms

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

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

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

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

And Login as "swiss-krono-delivery-guard" 1s 302ms

And Go to "TRANSPORT_TABLE" 169ms

When Confirm "Departure" status in transport row 3s 089ms

Then Verify that "Departure" has been confirmed 025ms

Hooks

After Hooks.deleteTransportAfterTest() 154ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is possible to confirm status with given confirmation date [A-7159]

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 451ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 917ms

And Login as "bausch-admin" 1s 123ms

And Go to "TRANSPORT_TABLE" 259ms

And Find transport in table with status "advice-added" 3s 229ms

When Confirm statuses until reach "on-the-way" 9s 187ms

And Open statuses popup 055ms

And Toggle status date confirmation checkbox 269ms

And Confirm statuses until reach "process-ended" 18s 746ms

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.deleteModeOfTransportationAfterTest() 110ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 270ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 233ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 733ms

And Login as "bausch-admin" 1s 068ms

And Go to "TRANSPORT_TABLE" 212ms

And Find transport in table with status "advice-added" 3s 213ms

When Confirm statuses until reach "on-the-way" 9s 244ms

And Open statuses popup 046ms

And Toggle status date confirmation checkbox 261ms

And Change status execution date to "1" days from today 2s 206ms

Then Verify that status cannot be confirmed 1s 085ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.deleteModeOfTransportationAfterTest() 085ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 292ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 252ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 687ms

And Login as "bausch-admin" 965ms

And Go to "TRANSPORT_TABLE" 225ms

And Find transport in table with status "advice-added" 3s 205ms

When Confirm statuses until reach "on-the-way" 9s 357ms

And Open statuses popup 053ms

And Toggle status date confirmation checkbox 253ms

And Change status execution date to "-1" days from today 2s 158ms

Then Verify that status cannot be confirmed 1s 069ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

After Hooks.deleteModeOfTransportationAfterTest() 127ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackTaskChanges

Scenario Outline Confirmed statuses of existing orders should not be deleted - even after editing the order [A-6874]

Steps

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 798ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 040ms

When Login as "farmacol-admin" 1s 749ms

And Go to "TRANSPORT_TABLE" 280ms

And Confirm statuses until reach "during-unload" 9s 242ms

And Set actual confirmed transport status list 1s 327ms

And Disable task by API 045ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 378ms

And Edit transport hours and recalculate statuses 16s 301ms

Then Verify that all confirmed statuses are still on transport status list 155ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

After Hooks.rollbackTaskChanges() 042ms

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

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

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

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

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

When Reject status: Book of disinfection 074ms

And Check if reject date is visible 242ms

Then If user is login then logout 074ms

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

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

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 26s 293ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 158ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status twice and reject date is changing

Steps

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

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 368ms

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

When Reject status: Book of disinfection 072ms

And Check if reject date is visible 133ms

And Get rejection date 025ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 054ms

Then Check if reject date has changed 1s 073ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

When Reject status: Book of disinfection 051ms

Then Check if reject date is visible 138ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

And Open statuses popup 102ms

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

When Reject status: Book of disinfection 071ms

Then Open statuses popup 064ms

And Check if reject date is visible 084ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Status revocation

@deleteTransportAfterTest

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

Steps

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

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

And Confirm to the last status by API 260ms

When Find statuses for transport in table 2s 302ms

And Revoke statuses until reach "advice-added" 6s 786ms

Then Check if transport has "advice-added" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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 286ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 397ms

And Confirm to the last status by API 241ms

When Find statuses for transport in table 1s 688ms

And Revoke statuses until reach "planned" 6s 636ms

Then Check if transport has "planned" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after created transport without advice, transport has checkpoints only from "preparation" section

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 125ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 216ms

When Find transport in table with status "new" 3s 179ms

And Open statuses popup 090ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 058ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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 066ms

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 001ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 175ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 079ms

And Set advice window in schedule 2s 799ms

And Fill advice form 12s 097ms

And Click advice save button and wait for advice form to disappear 30s 730ms

And Go to "TRANSPORT_TABLE" 217ms

When Find transport in table with status "advice-added" 3s 167ms

And Open statuses popup 069ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 063ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Steps

Given Set token of apiUsername "super-admin-farmacol" 204ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 146ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 684ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 027ms

When Login as "farmacol-admin" 1s 103ms

And Go to "TRANSPORT_TABLE" 224ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 6s 566ms

And Disable task by API 054ms

And Find transport pencil button in transports table 1s 195ms

And Click pencil and move transport to next day in schedule 18s 629ms

And Go to "TRANSPORT_TABLE" 226ms

Then Verify that "START_OF_UNLOADING" is not visible 136ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.rollbackTaskChanges() 046ms

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 631ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 386ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 079ms

When Go to "WAREHOUSE_TAB" 779ms

And Select warehouse "Serownia" 1s 362ms

And Set week view 1s 087ms

And Show yesterday 1s 094ms

And Move window into the past 277ms

Then Check if window is "red" 2s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

After Hooks.rollbackAddedAuthorities() 057ms

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" 932ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 312ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 055ms

When Go to "WAREHOUSE_TAB" 601ms

And Select warehouse "Magazyn - Nowa Sól" 2s 080ms

And Set week view 1s 175ms

And Show yesterday 1s 059ms

And Move window into the past 404ms

Then Check if window is "red" 2s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

After Hooks.rollbackAddedAuthorities() 042ms

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 272ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 214ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 043ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 020ms

When Show all transport types 1s 031ms

And Click button advice in transport table "DELIVERY" 089ms

And Set advice window in schedule 2s 650ms

And Fill advice form 8s 265ms

And Click advice save button and wait for advice form to disappear 30s 713ms

And Select warehouse "Magazyn Hala A" 1s 184ms

And Set week view 2s 202ms

And Show yesterday 1s 281ms

And Move window into the past 548ms

Then Check if window is "red" 2s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.rollbackAddedAuthorities() 028ms

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 540ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 002ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 538ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 496ms

When Go to "WAREHOUSE_TAB" 838ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 837ms

And Set week view 1s 095ms

And Check if time window length is correct after "CREATE" 023ms

And Change number of pallets in transport 53s 378ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 171ms

And Check if time window length is correct after "EDIT" 035ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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 183ms

And Get "UNLOAD" settings from "keeeper" 035ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 132ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 117ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 307ms

When Go to "WAREHOUSE_TAB" 333ms

And Select warehouse "Magazyn Surowców" 1s 216ms

And Set week view 1s 084ms

Then Check if time window has proper "60" 013ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

After Hooks.rollbackTransportTypeSettings() 067ms

After Hooks.clearAlgorithmSettings() 144ms

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 078ms

And Get "UNLOAD" settings from "keeeper" 052ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 112ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 066ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 358ms

When Go to "WAREHOUSE_TAB" 458ms

And Select warehouse "Magazyn Surowców" 1s 221ms

And Set week view 1s 081ms

Then Check if time window has proper "60" 014ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.rollbackTransportTypeSettings() 083ms

After Hooks.clearAlgorithmSettings() 117ms

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 076ms

And Get "LOAD" settings from "keeeper" 048ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 124ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 059ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 202ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 003ms

And Show all transport types 1s 055ms

And Click button advice in transport table "LOAD" 105ms

And Set advice window in schedule 2s 446ms

And Fill advice form 13s 095ms

And Click advice save button and wait for advice form to disappear 30s 699ms

Then Check if time window has proper "30" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.rollbackTransportTypeSettings() 060ms

After Hooks.clearAlgorithmSettings() 102ms

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 272ms

And Get "CONTAINER" settings from "keeeper" 035ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 120ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "20;false" 085ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 255ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 002ms

And Show all transport types 1s 041ms

And Click button advice in transport table "CONTAINER" 082ms

And Set advice window in schedule 2s 450ms

And Fill advice form 12s 944ms

And Click advice save button and wait for advice form to disappear 30s 741ms

Then Check if time window has proper "60" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.rollbackTransportTypeSettings() 058ms

After Hooks.clearAlgorithmSettings() 103ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings

Scenario Outline Check if supplier can change time window size by change number of pallets

Steps

Given Set token of apiUsername "super-admin-hochland" 110ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 167ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 108ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 313ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 465ms

When Go to transport details "DELIVERY" 32s 713ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 331ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 141ms

And Go to "WAREHOUSE_TAB" 838ms

And Select warehouse "Serownia" 1s 389ms

And Set week view 1s 079ms

Then Check if time window has proper "60" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

After Hooks.clearAlgorithmSettings() 249ms

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 379ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 047ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 212ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 332ms

And Check if time window counter value equals "1" 063ms

And Select view "DAYS_2" 2s 108ms

And Move advice window "2" 1s 326ms

And Select view "DAY" 2s 067ms

Then Check if time window counter value equals "0" 048ms

And Delete created transport by API 122ms

And Check if time window counter value equals "0" 038ms

And Click in free spot in schedule page to create gray window 166ms

And Check if time window counter value equals "0" 044ms

And Click in free spot in schedule page to create dedicated window 043ms

And Check if time window counter value equals "0" 041ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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" 1s 266ms

When Go to new transport "DELIVERY" 359ms

And Fill transport form 11s 392ms

And Click "save-transport" save button and wait for form to disappear 15s 630ms

And Set advice window in schedule 2s 174ms

And Check is transport created in schedule and set transport id 471ms

And Go to "TRANSPORT_TABLE" 198ms

When Click on time window date 1s 307ms

And Open transport form when in schedule 1s 144ms

Then Check are transport values equals 131ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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 578ms

When Go to new transport "DELIVERY" 423ms

And Fill transport form 38s 618ms

And Click "save-transport" save button and wait for form to disappear 15s 809ms

And Set advice window in schedule 2s 124ms

And Check is transport created in schedule and set transport id 652ms

And Go to "TRANSPORT_TABLE" 232ms

When Click on time window date 1s 369ms

And Open transport form when in schedule 1s 266ms

Then Check are transport values equals 19s 286ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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" 001ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 458ms

When Go to new transport "CISTERN_DELIVERY" 496ms

And Fill transport form 21s 553ms

Error message

java.lang.AssertionError: Nie można wypełnić pola warehouse, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/TimeWindow/TransportWindow.feature:175)

And 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

And Go to "TRANSPORT_TABLE" 000ms

When Click on time window date 000ms

And Open transport form when in schedule 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 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_CISTERN_COLLECTION" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 629ms

When Go to new transport "CISTERN_COLLECTION" 398ms

And Fill transport form 28s 194ms

And Click "save-transport" save button and wait for form to disappear 15s 963ms

And Set advice window in schedule 2s 193ms

And Check is transport created in schedule and set transport id 664ms

And Go to "TRANSPORT_TABLE" 163ms

When Click on time window date 1s 406ms

And Open transport form when in schedule 1s 201ms

Then Check are transport values equals 21s 328ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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" 001ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 380ms

When Go to new transport "DELIVERY" 269ms

And Fill transport form 37s 750ms

And Click "save-transport" save button and wait for form to disappear 15s 603ms

And Set advice window in schedule 2s 167ms

And Check is transport created in schedule and set transport id 642ms

And Go to "TRANSPORT_TABLE" 177ms

When Click on time window date 1s 365ms

And Open transport form when in schedule 1s 149ms

Then Check are transport values equals 19s 244ms

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" 001ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 091ms

When Go to new transport "LOAD" 265ms

And Fill transport form 38s 319ms

And Click "save-transport" save button and wait for form to disappear 15s 684ms

And Set advice window in schedule 2s 171ms

And Check is transport created in schedule and set transport id 552ms

And Go to "TRANSPORT_TABLE" 199ms

When Click on time window date 1s 293ms

And Open transport form when in schedule 1s 151ms

Then Check are transport values equals 19s 257ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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" 113ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 094ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 062ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 100ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 146ms

And Login as "farmacol-admin" 1s 621ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 712ms

And Go to "TRANSPORT_TABLE" 247ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 417ms

And Add step "unload" 107ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 457ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 320ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 336ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 269ms

Then Click "save-transport" save button 181ms

And Set advice window in schedule in "2" days 5s 092ms

And Click advice save button and wait for advice form to disappear 30s 980ms

And Go to "TRANSPORT_TABLE" 215ms

And Check if transport has "2" time windows 012ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

After Hooks.rollbackTransportTypeSettings() 083ms

After Hooks.rollbackAddedActionAuthorities() 059ms

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" 124ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 051ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 105ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 233ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 563ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 706ms

And Go to "TRANSPORT_TABLE" 285ms

And Get checkpoint colors for transport 007ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 42s 796ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.rollbackTransportTypeSettings() 085ms

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" 113ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 046ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 058ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 214ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 018ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 209ms

And Go to "TRANSPORT_TABLE" 279ms

And Get checkpoint colors for transport 003ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 41s 769ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.rollbackTransportTypeSettings() 094ms

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" 158ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 052ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 086ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 273ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 153ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 930ms

And Get checkpoint colors for transport 004ms

And Go to "TRANSPORT_TABLE" 285ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 5s 037ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:118)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:247)

Hooks

After Hooks.deleteTransportAfterTest() 136ms

After Hooks.rollbackTransportTypeSettings() 114ms

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" 107ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 045ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 064ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 243ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 060ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 924ms

And Get checkpoint colors for transport 002ms

And Go to "TRANSPORT_TABLE" 289ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 30s 816ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.rollbackTransportTypeSettings() 070ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if window is active after using "create similar" on that window [A-7009]

Steps

Given Set token of apiUsername "super-admin-farmacol" 112ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 205ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 704ms

And Login as "super-admin-farmacol" 1s 764ms

And Show all transport types 1s 043ms

And Click on time window date 1s 709ms

Then Open transport form when in schedule 1s 281ms

And Click create similar button 15s 101ms

And Click cancel button in transport form 103ms

And Open transport form when in schedule 1s 167ms

Then Check if transport form modal is visible 024ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 304ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 001ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 035ms

And Set proper delay time to move order to archive after task timeout 047ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 277ms

And Go to "WAREHOUSE_TAB" 695ms

And Change warehouse in schedule to: "Katowice" 1s 069ms

And Wait "60" seconds 1m

And Verify that transport window is grey 024ms

And Verify that transport is in archive 1s 119ms

Then Restore transport from archive 1s 101ms

And Verify that transport has been successfully restored 15s 263ms

Hooks

After Hooks.deleteTransportAfterTest() 165ms

After Hooks.rollbackSettings() 053ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings

Scenario Outline Check if confirming transport status removed it to the archive

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 1s 195ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 185ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 048ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 001ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.setCompanySettingsByName(ApolloUpdateDbService.java:20)
	at CucumberTests.Settings.SettingsTest.prepareSettingWithValueWith(SettingsTest.java:55)
	at ✽.Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco"(file:Features/Atom/Transport/Archive.feature:39)

When Go to "TRANSPORT_TABLE" 000ms

And Click button advice in transport table "OWN_COLLECTION" 000ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "planned-magazyn-tychy" 000ms

And Confirm statuses until reach "process-ended" 000ms

And Wait "12" seconds 000ms

Then Go to "ARCHIVE_TAB" 000ms

And Show "OWN_COLLECTION" 000ms

And Verify that created transport is "true" in transport table 000ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

After Hooks.rollbackSettings() 034ms

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 085ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 220ms

When Fill auction form 15s 429ms

Then Verify that the auction has been added to transport 041ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 350ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 335ms

When Fill auction form 15s 389ms

Then Verify that the auction has been added to transport 036ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 089ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 204ms

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 082ms

And Login as "paa1-carrier@qa.qa-test" 1s 357ms

And Go to auction offer 1s 351ms

And Accept transport with minimum rate 15s 632ms

Then Check if carrier is assigned to transport 016ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 364ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 110ms

When If user is login then logout 075ms

And Login as "paa1-carrier@qa.qa-test" 1s 325ms

And Go to auction offer 1s 274ms

And Reject auction offer 15s 605ms

Then Verify that offer has been removed from transport 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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 291ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 250ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 143ms

When If user is login then logout 158ms

And Login as "pskza1-carrier@qa.qa-test" 1s 164ms

And Go to auction offer 1s 234ms

And Reject auction offer 15s 598ms

Then Verify that offer has been removed from transport 15s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 130ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 263ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 104ms

When If user is login then logout 298ms

And Login as "paa1-carrier@qa.qa-test" 1s 291ms

And Go to auction offer 1s 312ms

And Offer prize above maximum - "20000" 124ms

Then Verify that is not possible to add offer 144ms

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 220ms

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 093ms

When If user is login then logout 088ms

And Login as "pskza1-carrier@qa.qa-test" 1s 790ms

And Go to auction offer 1s 342ms

And Offer prize above maximum - "20000" 123ms

Then Verify that is not possible to add offer 129ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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 067ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 229ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 086ms

And Wait till auction end 1m 58s 014ms

Then Verify that is possible to add auction 045ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 316ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 220ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 091ms

And Wait till auction end 1m 58s 014ms

Then Verify that is possible to add auction 046ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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 544ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 240ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 181ms

And Go to auction offer 1s 212ms

When Offer "1000" 159ms

Then Verify that offer with "1000" has been added to auction 3s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 130ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 387ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 252ms

And Go to auction offer 1s 221ms

When Offer "1000" 112ms

Then Verify that offer with "1000" has been added to auction 3s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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 071ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 283ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 099ms

And Go to auction offer 1s 186ms

When Offer "1000" 097ms

And Verify that offer with "1000" has been added to auction 3s 025ms

Then Go to auction offer 1s 150ms

And Revoke current offer 598ms

And Verify that offer has been revoked 30s 607ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 272ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 418ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 158ms

And Go to auction offer 1s 187ms

When Offer "1000" 112ms

And Verify that offer with "1000" has been added to auction 3s 034ms

Then Go to auction offer 1s 167ms

And Offer "1500" 159ms

And Verify that offer with "1500" has been added to auction 3s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 074ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 373ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 091ms

And Go to auction offer 1s 171ms

When Offer "1000" 107ms

And Verify that offer with "1000" has been added to auction 3s 024ms

Then Login as "swisskrono-admin" 1s 057ms

And Go to auction details 1s 204ms

And Finish active auction 063ms

And Verify that the transport has no active auction 149ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 137ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 247ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 102ms

And Go to auction offer 1s 234ms

When Offer "1000" 108ms

Then Verify that carrier can see current place in auction depending on the "true" role 133ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 115ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 327ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 115ms

And Go to auction offer 1s 302ms

When Offer "1000" 146ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 581ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 441ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 107ms

And Go to auction offer 1s 219ms

When Offer "300" 106ms

And Verify that carrier can't add offer to auction 024ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 056ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 186ms

And Show all transport "false" 010ms

When Go to auction form 1s 217ms

Then Verify carrier selection value "false" 034ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 115ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 292ms

And Show all transport "true" 077ms

When Go to auction form 1s 176ms

Then Verify carrier selection value "true" 062ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 113ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 189ms

When Open transport auction form 168ms

And Select all companies checkbox in transport auction form 058ms

And Unselect company "PAA2" in transport auction form 065ms

And Put transport on auction 15s 172ms

And Open transport auction history 114ms

And Open participants section in transport auction history 050ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 510ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 216ms

When Open transport auction form 197ms

And Select all companies checkbox in transport auction form 071ms

And Unselect company "PSKZA2" in transport auction form 059ms

And Put transport on auction 15s 151ms

And Open transport auction history 068ms

And Open participants section in transport auction history 059ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_UNLOAD" "super-admin-pgf" 002ms

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 095ms

When Go to new transport "UNLOAD" 15s 277ms

And Fill transport form 16s 182ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//li//span[text()='Magazyn Rozładunków'] | //li[text()='Magazyn Rozładunków' and @role='option']"}
  (Session info: headless chrome=90.0.4430.93)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.jKzpZs}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: d802efd668825be5b2b300d32c864374
*** Element info: {Using=xpath, value=//li//span[text()='Magazyn Rozładunków'] | //li[text()='Magazyn Rozładunków' and @role='option']}
	at sun.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:229)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:214)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:166)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/CrudTransport.feature:8)

And 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

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "UNLOAD" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 318ms

When Go to new transport "DELIVERY" 255ms

And Fill transport form 11s 380ms

And Click "save-transport" save button and wait for form to disappear 15s 613ms

And Set advice window in schedule 2s 132ms

And Check is transport created in schedule and set transport id 508ms

And Go to "TRANSPORT_TABLE" 208ms

And Go to transport details "DELIVERY" 4s 343ms

Then Check are transport values equals 106ms

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_OWN_COLLECTION" "super-admin-adama" 001ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 161ms

When Go to new transport "OWN_COLLECTION" 310ms

And Fill transport form 17s 851ms

And Click "save-transport" save button and wait for form to disappear 15s 632ms

And Set advice window in schedule 2s 161ms

And Check is transport created in schedule and set transport id 449ms

And Go to "TRANSPORT_TABLE" 154ms

And Go to transport details "OWN_COLLECTION" 4s 277ms

Then Check are transport values equals 138ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 702ms

When Go to new transport "DELIVERY" 351ms

And Fill transport form 38s 563ms

And Click "save-transport" save button and wait for form to disappear 15s 585ms

And Set advice window in schedule 2s 127ms

And Check is transport created in schedule and set transport id 650ms

And Go to "TRANSPORT_TABLE" 253ms

And Go to transport details "DELIVERY" 4s 742ms

Then Check are transport values equals 19s 309ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 443ms

When Go to new transport "CISTERN_DELIVERY" 451ms

And Fill transport form 21s 624ms

Error message

java.lang.AssertionError: Nie można wypełnić pola warehouse, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/CrudTransport.feature:8)

And 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

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "CISTERN_DELIVERY" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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 474ms

When Go to new transport "CISTERN_COLLECTION" 438ms

And Fill transport form 27s 982ms

And Click "save-transport" save button and wait for form to disappear 15s 913ms

And Set advice window in schedule 2s 216ms

And Check is transport created in schedule and set transport id 542ms

And Go to "TRANSPORT_TABLE" 166ms

And Go to transport details "CISTERN_COLLECTION" 4s 380ms

Then Check are transport values equals 21s 269ms

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-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 455ms

When Go to new transport "OWN_COLLECTION" 395ms

And Fill transport form 32s 628ms

And Click "save-transport" save button and wait for form to disappear 15s 674ms

And Set advice window in schedule 2s 127ms

And Check is transport created in schedule and set transport id 560ms

And Go to "TRANSPORT_TABLE" 150ms

And Go to transport details "OWN_COLLECTION" 4s 551ms

Then Check are transport values equals 19s 306ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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 637ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 394ms

And Fill transport form 32s 718ms

And Click "save-transport" save button and wait for form to disappear 15s 661ms

And Set advice window in schedule 2s 140ms

And Check is transport created in schedule and set transport id 584ms

And Go to "TRANSPORT_TABLE" 172ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 434ms

Then Check are transport values equals 4s 267ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 680ms

When Go to new transport "EXPORT" 409ms

And Fill transport form 40s 411ms

And Click "save-transport" save button and wait for form to disappear 15s 588ms

And Set advice window in schedule 2s 106ms

And Check is transport created in schedule and set transport id 569ms

And Go to "TRANSPORT_TABLE" 311ms

And Go to transport details "EXPORT" 4s 755ms

Then Check are transport values equals 4s 341ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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" 001ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 145ms

When Go to new transport "DELIVERY" 15s 254ms

And Fill transport form 28s 236ms

And Click "save-transport" save button and wait for form to disappear 15s 596ms

And Set advice window in schedule 2s 141ms

And Check is transport created in schedule and set transport id 709ms

And Go to "TRANSPORT_TABLE" 204ms

And Go to transport details "DELIVERY" 32s 266ms

Then Check are transport values equals 36s 282ms

Hooks

After Hooks.deleteTransportAfterTest() 177ms

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" 001ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 137ms

When Go to new transport "DELIVERY" 290ms

And Fill transport form 37s 672ms

And Click "save-transport" save button and wait for form to disappear 15s 608ms

And Set advice window in schedule 2s 121ms

And Check is transport created in schedule and set transport id 805ms

And Go to "TRANSPORT_TABLE" 296ms

And Go to transport details "DELIVERY" 4s 304ms

Then Check are transport values equals 19s 271ms

Hooks

After Hooks.deleteTransportAfterTest() 154ms

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 059ms

When Go to new transport "LOAD" 287ms

And Fill transport form 37s 746ms

And Click "save-transport" save button and wait for form to disappear 15s 675ms

And Set advice window in schedule 2s 132ms

And Check is transport created in schedule and set transport id 525ms

And Go to "TRANSPORT_TABLE" 234ms

And Go to transport details "LOAD" 4s 283ms

Then Check are transport values equals 19s 299ms

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-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 216ms

When Go to new transport "UNLOAD" 324ms

And Fill transport form 37s 320ms

And Click "save-transport" save button and wait for form to disappear 15s 590ms

And Set advice window in schedule 2s 140ms

And Check is transport created in schedule and set transport id 510ms

And Go to "TRANSPORT_TABLE" 201ms

And Go to transport details "UNLOAD" 4s 336ms

Then Check are transport values equals 21s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 402ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 326ms

And Fill transport form 37s 257ms

And Click "save-transport" save button and wait for form to disappear 15s 602ms

And Set advice window in schedule 2s 140ms

And Check is transport created in schedule and set transport id 546ms

And Go to "TRANSPORT_TABLE" 176ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 361ms

Then Check are transport values equals 21s 355ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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" 003ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 150ms

When Go to new transport "DELIVERY" 284ms

And Fill transport form 22s 619ms

And Click "save-transport" save button and wait for form to disappear 15s 590ms

And Set advice window in schedule 2s 129ms

And Check is transport created in schedule and set transport id 528ms

And Go to "TRANSPORT_TABLE" 173ms

And Go to transport details "DELIVERY" 4s 356ms

Then Check are transport values equals 17s 212ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_WEIGHING" "super-admin-hochland" 001ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 448ms

When Go to new transport "WEIGHING" 348ms

And Fill transport form 13s 399ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 618ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 124ms

And Go to transport details "WEIGHING" 4s 386ms

And Check are transport values equals 2s 150ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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" 001ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 106ms

When Go to new transport "TRANSPORT" 363ms

And Fill transport form 26s 546ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 624ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "TRANSPORT" 4s 414ms

And Check are transport values equals 6s 232ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 148ms

When Go to new transport "CONTAINER" 309ms

And Fill transport form 11s 083ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 625ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 123ms

And Go to transport details "CONTAINER" 4s 310ms

And Check are transport values equals 064ms

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_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 475ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 370ms

And Fill transport form 12s 887ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 625ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 135ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 557ms

And Check are transport values equals 4s 148ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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" 001ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 559ms

When Go to new transport "DELIVERY" 305ms

And Fill transport form 22s 422ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 627ms

And Show all transport "false" 007ms

And Go to "TRANSPORT_TABLE" 126ms

And Go to transport details "DELIVERY" 4s 693ms

And Check are transport values equals 17s 189ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 176ms

When Go to new transport "LOAD" 356ms

And Fill transport form 26s 216ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 587ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "LOAD" 4s 765ms

And Check are transport values equals 2s 149ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 001ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 405ms

When Go to new transport "LOAD" 290ms

And Fill transport form 24s 476ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 661ms

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 123ms

And Go to transport details "LOAD" 4s 352ms

And Check are transport values equals 19s 217ms

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_CONTAINER" "super-admin-keeeper" 001ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 464ms

When Go to new transport "CONTAINER" 295ms

And Fill transport form 24s 480ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 114ms

And Go to transport details "CONTAINER" 4s 354ms

And Check are transport values equals 19s 231ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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" 001ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 204ms

When Go to new transport "SMALLS_IMPORT" 378ms

And Fill transport form 36s 230ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 596ms

And Show all transport "false" 007ms

And Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "SMALLS_IMPORT" 4s 360ms

And Check are transport values equals 10s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 001ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 252ms

When Go to new transport "SMALLS_EXPORT" 412ms

And Fill transport form 36s 199ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Show all transport "false" 007ms

And Go to "TRANSPORT_TABLE" 126ms

And Go to transport details "SMALLS_EXPORT" 4s 340ms

And Check are transport values equals 10s 404ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 268ms

When Go to new transport "TRANSPORT_ORDER" 593ms

And Fill transport form 29s 867ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 630ms

And Show all transport "true" 086ms

And Go to "TRANSPORT_TABLE" 103ms

And Go to transport details "TRANSPORT_ORDER" 4s 369ms

And Check are transport values equals 19s 274ms

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_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 297ms

When Go to new transport "TRANSPORT" 358ms

And Fill transport form 37s 453ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 587ms

And Show all transport "false" 007ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "TRANSPORT" 4s 412ms

And Check are transport values equals 4s 187ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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" 001ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 127ms

When Go to new transport "INBOUND" 348ms

And Fill transport form 40s 826ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 651ms

And Show all transport "true" 087ms

And Go to "TRANSPORT_TABLE" 115ms

And Go to transport details "INBOUND" 4s 403ms

And Check are transport values equals 2s 253ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 001ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 185ms

When Go to new transport "EXTERNAL_DELIVERY" 283ms

And Fill transport form 53s 263ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 624ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 120ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 403ms

And Check are transport values equals 4s 479ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "dfa1-supplier" 002ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 1s 888ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 274ms

And Fill transport form 46s 792ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 639ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 125ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 350ms

And Check are transport values equals 4s 364ms

Hooks

After Hooks.deleteTransportAfterTest() 034ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteTransportAfterTest(Hooks.java:174)
	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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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 104ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 921ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 32s 499ms

And Fill transport form 30s 298ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 104ms

And Go to transport details "UNLOAD" 32s 382ms

Then Check are transport values equals 4s 237ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 277ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 286ms

And Show all transport "false" 010ms

When Go to transport details "TRANSPORT" 4s 488ms

And Fill transport form 10s 285ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 653ms

And Go to transport details "TRANSPORT" 4s 424ms

Then Check are transport values equals 4s 098ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 250ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 170ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 334ms

And Fill transport form 4s 717ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 616ms

And Go to transport details "CONTAINER" 4s 329ms

Then Check are transport values equals 037ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

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 123ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 275ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 354ms

And Fill transport form 11s 530ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 569ms

And Go to transport details "DELIVERY" 4s 361ms

Then Check are transport values equals 116ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 196ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 002ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 359ms

And Show all transport "false" 008ms

When Go to transport details "OWN_COLLECTION" 4s 354ms

And Fill transport form 21s 519ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 598ms

And Go to transport details "OWN_COLLECTION" 4s 321ms

Then Check are transport values equals 2s 190ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 647ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 484ms

And Show all transport "false" 012ms

When Go to transport details "DELIVERY" 5s 231ms

And Fill transport form 35s 755ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 090ms

And Go to transport details "DELIVERY" 4s 431ms

Then Check are transport values equals 10s 513ms

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 574ms

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 337ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION" 4s 674ms

And Fill transport form 36s 392ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 099ms

And Go to transport details "OWN_COLLECTION" 4s 414ms

Then Check are transport values equals 6s 339ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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 563ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 422ms

And Show all transport "false" 005ms

When Go to transport details "EXPORT" 5s 009ms

And Fill transport form 47s 814ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 124ms

And Go to transport details "EXPORT" 4s 387ms

Then Check are transport values equals 8s 416ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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 520ms

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 247ms

And Show all transport "false" 007ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 517ms

And Fill transport form 36s 103ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 412ms

Then Check are transport values equals 12s 395ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 706ms

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 363ms

And Show all transport "false" 009ms

When Go to transport details "CISTERN_DELIVERY" 4s 538ms

And Fill transport form 27s 046ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 629ms

And Go to transport details "CISTERN_DELIVERY" 4s 395ms

Then Check are transport values equals 6s 261ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 569ms

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 430ms

And Show all transport "false" 007ms

When Go to transport details "CISTERN_COLLECTION" 4s 598ms

And Fill transport form 25s 671ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 616ms

And Go to transport details "CISTERN_COLLECTION" 4s 389ms

Then Check are transport values equals 6s 221ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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 552ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 224ms

And Show all transport "false" 009ms

When Go to transport details "WEIGHING" 4s 422ms

And Fill transport form 12s 175ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 614ms

And Go to transport details "WEIGHING" 4s 350ms

Then Check are transport values equals 2s 167ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 392ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 002ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 302ms

And Show all transport "false" 009ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 542ms

And Fill transport form 35s 029ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 075ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 394ms

Then Check are transport values equals 6s 288ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 102ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 311ms

And Show all transport "false" 015ms

When Go to transport details "DELIVERY" 32s 544ms

And Fill transport form 25s 479ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 579ms

And Go to transport details "DELIVERY" 32s 400ms

Then Check are transport values equals 2s 150ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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 301ms

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 181ms

And Show all transport "false" 006ms

When Go to transport details "LOAD" 4s 706ms

And Fill transport form 57s 183ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 124ms

And Go to transport details "LOAD" 4s 420ms

Then Check are transport values equals 24s 682ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 127ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 354ms

And Show all transport "false" 006ms

When Go to transport details "DELIVERY" 4s 435ms

And Fill transport form 16s 334ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 637ms

And Go to transport details "DELIVERY" 4s 268ms

Then Check are transport values equals 080ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 016ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 276ms

And Show all transport "false" 007ms

When Go to transport details "LOAD" 4s 340ms

And Fill transport form 27s 914ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 105ms

And Go to transport details "LOAD" 4s 274ms

Then Check are transport values equals 2s 186ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 182ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 369ms

And Show all transport "false" 006ms

When Go to transport details "UNLOAD" 4s 398ms

And Fill transport form 37s 645ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 636ms

And Go to transport details "UNLOAD" 4s 346ms

Then Check are transport values equals 6s 414ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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 175ms

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 338ms

And Show all transport "false" 011ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 381ms

And Fill transport form 35s 953ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 596ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 338ms

Then Check are transport values equals 6s 310ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 160ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 205ms

And Show all transport "false" 005ms

When Go to transport details "LOAD" 4s 364ms

And Fill transport form 24s 575ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 636ms

And Go to transport details "LOAD" 4s 305ms

Then Check are transport values equals 4s 156ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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 097ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 174ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 360ms

And Fill transport form 24s 432ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 628ms

And Go to transport details "CONTAINER" 4s 345ms

Then Check are transport values equals 4s 160ms

Hooks

After Hooks.deleteTransportAfterTest() 053ms

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 337ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 003ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 206ms

And Show all transport "false" 006ms

When Go to transport details "SMALLS_EXPORT" 4s 475ms

And Fill transport form 32s 828ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 617ms

And Go to transport details "SMALLS_EXPORT" 4s 362ms

Then Check are transport values equals 8s 311ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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 125ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 253ms

And Show all transport "true" 054ms

When Go to transport details "DELIVERY" 4s 269ms

And Fill transport form 19s 476ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 573ms

And Go to transport details "DELIVERY" 4s 283ms

Then Check are transport values equals 166ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 102ms

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 251ms

And Show all transport "true" 076ms

When Go to transport details "TRANSPORT_ORDER" 4s 444ms

And Fill transport form 26s 717ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 620ms

And Go to transport details "TRANSPORT_ORDER" 4s 335ms

Then Check are transport values equals 2s 216ms

Hooks

After Hooks.deleteTransportAfterTest() 056ms

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 204ms

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 269ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 324ms

And Fill transport form 8s 832ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 579ms

And Go to transport details "CONTAINER" 4s 401ms

Then Check are transport values equals 4s 098ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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 421ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 347ms

And Show all transport "false" 008ms

When Delete transport 17s 861ms

Then Transport not displayed in table of transports 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 276ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 186ms

And Show all transport "false" 007ms

When Delete transport 2s 164ms

Then Transport not displayed in table of transports 15s 061ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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 069ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 270ms

And Show all transport "false" 006ms

When Delete transport 17s 516ms

Then Transport not displayed in table of transports 15s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 051ms

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 243ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 183ms

And Show all transport "false" 009ms

When Delete transport 16s 965ms

Then Transport not displayed in table of transports 15s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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 186ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 196ms

And Show all transport "false" 006ms

When Delete transport 17s 712ms

Then Transport not displayed in table of transports 15s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 244ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 239ms

And Show all transport "false" 007ms

When Delete transport 17s 680ms

Then Transport not displayed in table of transports 15s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

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 209ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 292ms

And Show all transport "true" 067ms

When Delete transport 19s 031ms

Then Transport not displayed in table of transports 15s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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 083ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 269ms

And Show all transport "true" 073ms

When Delete transport 17s 118ms

Then Transport not displayed in table of transports 15s 032ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 127ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 614ms

And Show all transport "false" 006ms

When Go to transport details "UNLOAD" 32s 395ms

And Fill transport form 30s 221ms

And Click "save-transport" save button 1s 220ms

And Click cancel button in transport form 076ms

And Go to transport details "UNLOAD" 32s 362ms

Then Check are transport values equals 4s 244ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 120ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 193ms

And Show all transport "false" 007ms

When Go to transport details "TRANSPORT" 4s 451ms

And Fill transport form 10s 275ms

And Click "save-transport" save button 706ms

And Click cancel button in transport form 076ms

And Go to transport details "TRANSPORT" 4s 264ms

Then Check are transport values equals 4s 109ms

Hooks

After Hooks.deleteTransportAfterTest() 056ms

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 238ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 140ms

And Show all transport "false" 006ms

When Go to transport details "CONTAINER" 4s 320ms

And Fill transport form 4s 698ms

And Click "save-transport" save button 701ms

And Click cancel button in transport form 061ms

And Go to transport details "CONTAINER" 4s 243ms

Then Check are transport values equals 044ms

Hooks

After Hooks.deleteTransportAfterTest() 046ms

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 315ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 230ms

And Show all transport "false" 006ms

When Go to transport details "DELIVERY" 4s 301ms

And Fill transport form 11s 499ms

And Click "save-transport" save button 696ms

And Click cancel button in transport form 073ms

And Go to transport details "DELIVERY" 4s 212ms

Then Check are transport values equals 082ms

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 "adama-admin" and set token of apiUsername "super-admin-adama" 1s 001ms

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 281ms

And Show all transport "false" 007ms

When Go to transport details "OWN_COLLECTION" 4s 443ms

And Fill transport form 21s 441ms

And Click "save-transport" save button 685ms

And Click cancel button in transport form 059ms

And Go to transport details "OWN_COLLECTION" 4s 261ms

Then Check are transport values equals 2s 183ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 465ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 309ms

And Show all transport "false" 008ms

When Go to transport details "DELIVERY" 4s 824ms

And Fill transport form 35s 563ms

And Click "save-transport" save button 1s 238ms

And Click cancel button in transport form 066ms

And Go to transport details "DELIVERY" 4s 319ms

Then Check are transport values equals 10s 420ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 539ms

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 328ms

And Show all transport "false" 007ms

When Go to transport details "OWN_COLLECTION" 4s 665ms

And Fill transport form 36s 303ms

And Click "save-transport" save button 1s 241ms

And Click cancel button in transport form 070ms

And Go to transport details "OWN_COLLECTION" 4s 519ms

Then Check are transport values equals 6s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 560ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 002ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 560ms

And Show all transport "false" 009ms

When Go to transport details "EXPORT" 5s 715ms

And Fill transport form 47s 532ms

And Click "save-transport" save button 831ms

And Click cancel button in transport form 099ms

And Go to transport details "EXPORT" 4s 431ms

Then Check are transport values equals 8s 432ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 556ms

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 170ms

And Show all transport "false" 009ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 675ms

And Fill transport form 36s 123ms

And Click "save-transport" save button 908ms

And Click cancel button in transport form 073ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 353ms

Then Check are transport values equals 12s 377ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 564ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 371ms

And Show all transport "false" 021ms

When Go to transport details "CISTERN_DELIVERY" 4s 497ms

And Fill transport form 27s 273ms

And Click "save-transport" save button 785ms

And Click cancel button in transport form 102ms

And Go to transport details "CISTERN_DELIVERY" 4s 312ms

Then Check are transport values equals 6s 237ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 590ms

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 292ms

And Show all transport "false" 009ms

When Go to transport details "CISTERN_COLLECTION" 4s 392ms

And Fill transport form 25s 700ms

And Click "save-transport" save button 733ms

And Click cancel button in transport form 079ms

And Go to transport details "CISTERN_COLLECTION" 4s 319ms

Then Check are transport values equals 6s 208ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 562ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 245ms

And Show all transport "false" 012ms

When Go to transport details "WEIGHING" 4s 389ms

And Fill transport form 12s 225ms

And Click "save-transport" save button 697ms

And Click cancel button in transport form 068ms

And Go to transport details "WEIGHING" 4s 252ms

Then Check are transport values equals 2s 161ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 545ms

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 310ms

And Show all transport "false" 007ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 575ms

And Fill transport form 34s 931ms

And Click "save-transport" save button 891ms

And Click cancel button in transport form 079ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 341ms

Then Check are transport values equals 6s 266ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 046ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 273ms

And Show all transport "false" 006ms

When Go to transport details "DELIVERY" 32s 399ms

And Fill transport form 25s 457ms

And Click "save-transport" save button 674ms

And Click cancel button in transport form 056ms

And Go to transport details "DELIVERY" 32s 469ms

Then Check are transport values equals 2s 168ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 137ms

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 166ms

And Show all transport "false" 009ms

When Go to transport details "LOAD" 4s 662ms

And Fill transport form 56s 863ms

And Click "save-transport" save button 995ms

And Click cancel button in transport form 111ms

And Go to transport details "LOAD" 4s 344ms

Then Check are transport values equals 24s 685ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 171ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 459ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 4s 333ms

And Fill transport form 16s 401ms

And Click "save-transport" save button 692ms

And Click cancel button in transport form 061ms

And Go to transport details "DELIVERY" 4s 274ms

Then Check are transport values equals 065ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 112ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 270ms

And Show all transport "false" 007ms

When Go to transport details "LOAD" 4s 277ms

And Fill transport form 28s 136ms

And Click "save-transport" save button 1s 222ms

And Click cancel button in transport form 073ms

And Go to transport details "LOAD" 4s 255ms

Then Check are transport values equals 2s 194ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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 175ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 328ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 4s 393ms

And Fill transport form 37s 619ms

And Click "save-transport" save button 717ms

And Click cancel button in transport form 075ms

And Go to transport details "UNLOAD" 4s 364ms

Then Check are transport values equals 6s 310ms

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 "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 283ms

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 278ms

And Show all transport "false" 008ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 536ms

And Fill transport form 35s 986ms

And Click "save-transport" save button 675ms

And Click cancel button in transport form 073ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 322ms

Then Check are transport values equals 6s 282ms

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 "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 455ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 169ms

And Show all transport "false" 007ms

When Go to transport details "LOAD" 4s 371ms

And Fill transport form 24s 580ms

And Click "save-transport" save button 705ms

And Click cancel button in transport form 068ms

And Go to transport details "LOAD" 4s 286ms

Then Check are transport values equals 4s 148ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

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 122ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 195ms

And Show all transport "false" 007ms

When Go to transport details "CONTAINER" 4s 370ms

And Fill transport form 24s 600ms

And Click "save-transport" save button 699ms

And Click cancel button in transport form 064ms

And Go to transport details "CONTAINER" 4s 282ms

Then Check are transport values equals 4s 147ms

Hooks

After Hooks.deleteTransportAfterTest() 050ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 242ms

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 230ms

And Show all transport "false" 009ms

When Go to transport details "SMALLS_IMPORT" 4s 397ms

And Fill transport form 32s 828ms

And Click "save-transport" save button 746ms

And Click cancel button in transport form 061ms

And Go to transport details "SMALLS_IMPORT" 4s 274ms

Then Check are transport values equals 8s 267ms

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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 277ms

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 205ms

And Show all transport "false" 004ms

When Go to transport details "SMALLS_EXPORT" 4s 522ms

And Fill transport form 32s 952ms

And Click "save-transport" save button 703ms

And Click cancel button in transport form 059ms

And Go to transport details "SMALLS_EXPORT" 4s 329ms

Then Check are transport values equals 8s 298ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 104ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 274ms

And Show all transport "true" 081ms

When Go to transport details "DELIVERY" 4s 282ms

And Fill transport form 19s 459ms

And Click "save-transport" save button 694ms

And Click cancel button in transport form 077ms

And Go to transport details "DELIVERY" 4s 288ms

Then Check are transport values equals 137ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 212ms

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 226ms

And Show all transport "true" 065ms

When Go to transport details "TRANSPORT_ORDER" 4s 426ms

And Fill transport form 26s 597ms

And Click "save-transport" save button 719ms

And Click cancel button in transport form 050ms

And Go to transport details "TRANSPORT_ORDER" 4s 282ms

Then Check are transport values equals 2s 208ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

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 093ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 198ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 226ms

And If user is login then logout 224ms

Then Login as "dka1-supplier" 1s 840ms

And Click button advice in transport table "LOAD" 138ms

And Check if moved to first possible start date in schedule 407ms

Hooks

After Hooks.deleteTransportAfterTest() 051ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 460ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to create transport with new address [A-7158]

Steps

Given Set token of apiUsername "super-admin-piast" 120ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 007ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 437ms

Then Go to new transport "LOAD" 338ms

And Fill transport form 23s 234ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 601ms

And Go to "COMPANIES_TAB" 466ms

And Go to company "Dostawca Piast Automat 1" details 160ms

And Check if new address with "Adresat" is visible in company details 123ms

And Go to "TRANSPORT_TABLE" 203ms

And Go to transport details "LOAD" 4s 779ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.deleteAddressAfterTest() 044ms

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 158ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 176ms

When Go to "TRANSPORT_TABLE" 100ms

And Show all transport types 1s 031ms

And Verify that transport has "0" files 028ms

Then Add file to transport by API 361ms

And Verify that transport has "1" files 780ms

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 029ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 165ms

When Go to "TRANSPORT_TABLE" 109ms

And Show all transport types 1s 028ms

And Verify that transport has "0" files 030ms

Then Add file to transport by API 233ms

And Verify that transport has "1" files 582ms

Hooks

After Hooks.deleteTransportAfterTest() 053ms

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 409ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 409ms

When Go to "TRANSPORT_TABLE" 105ms

And Show all transport types 1s 026ms

And Verify that transport has "0" files 029ms

Then Add file to transport by API 215ms

And Verify that transport has "1" files 362ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 995ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 167ms

When Go to "TRANSPORT_TABLE" 099ms

And Show all transport types 1s 033ms

And Verify that transport has "0" files 025ms

Then Add file to transport by API 202ms

And Verify that transport has "1" files 987ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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 054ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 152ms

And Delete transport 17s 617ms

When Go to "ARCHIVE_TAB" 202ms

And Show "DELIVERY" 048ms

And Verify that transport has "0" files 610ms

Then Add file to transport 141ms

And Verify that transport has "1" files 364ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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 339ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 262ms

And Delete transport 17s 305ms

When Go to "ARCHIVE_TAB" 204ms

And Show "LOAD" 082ms

And Verify that transport has "0" files 1s 055ms

Then Add file to transport 130ms

And Verify that transport has "1" files 353ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 442ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 319ms

And Delete transport 18s 152ms

When Go to "ARCHIVE_TAB" 245ms

And Show "DELIVERY" 063ms

And Verify that transport has "0" files 829ms

Then Add file to transport 138ms

And Verify that transport has "1" files 386ms

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 "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 150ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 177ms

And Delete transport 17s 563ms

When Go to "ARCHIVE_TAB" 277ms

And Show "CONTAINER" 100ms

And Verify that transport has "0" files 975ms

Then Add file to transport 155ms

And Verify that transport has "1" files 317ms

Hooks

After Hooks.deleteTransportAfterTest() 047ms

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" 096ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 170ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 103ms

And Accept transferred transport by Api 152ms

And Login as "paa1-carrier@qa.qa-test" 1s 293ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 206ms

Hooks

After Hooks.deleteTransportAfterTest() 054ms

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 334ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 193ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 099ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 285ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

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" 112ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 240ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 141ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 288ms

And Login as "paa1-carrier@qa.qa-test" 1s 168ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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 369ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 202ms

When Go to "TRANSPORT_TABLE" 128ms

And Show all transport "true" 058ms

Then Verify that transport has "1" CMR file 1s 170ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 033ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 241ms

When Go to "TRANSPORT_TABLE" 114ms

And Show all transport "true" 054ms

Then Verify that transport has "2" CMR file 1s 164ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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 080ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 235ms

When Go to "TRANSPORT_TABLE" 099ms

And Show all transport "true" 064ms

Then Verify that "CMR" document can be downloaded 17s 506ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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 301ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 248ms

And Show all transport "true" 083ms

And Delete transport 17s 125ms

When Go to "ARCHIVE_TAB" 215ms

And Show "TRANSPORT_ORDER" 062ms

Then Verify that "CMR" document can be downloaded 16s 760ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Transport files

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline The link to the delivery document appears after confirming the respective status [A-6905]

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 2s 165ms

And Create default accepted mode of transportation by API with "pba1-carrier" 364ms

And If user is login then logout 230ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 282ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 243ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 088ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 009ms

And Click button advice in transport table "LOAD_PL" 1s 854ms

And Set advice window in schedule 2s 773ms

And Fill advice form 9s

And Click advice save button and wait for advice form to disappear 30s 674ms

And Find transport in table with status "advice-added" 3s 314ms

When Confirm statuses until reach "on-the-way" 9s 413ms

Then Verify that "delivery_document" document can be downloaded 16s 248ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.deleteModeOfTransportationAfterTest() 067ms

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 507ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 376ms

And Show all transport "false" 005ms

When Find transport pencil button in transports table 1s 209ms

And Click pencil and move transport to next day in schedule 16s 582ms

Then Check if transport is in new location in schedule 2s 098ms

And Check if dates in transport form are correct 3s 462ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 273ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 334ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 232ms

And Click pencil and move transport to next day in schedule 16s 743ms

Then Check if transport is in new location in schedule 2s 105ms

And Check if dates in transport form are correct 3s 306ms

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 316ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 323ms

And Show all transport "false" 005ms

When Find transport pencil button in transports table 1s 227ms

And Click pencil and move transport to next day in schedule 16s 855ms

Then Check if transport is in new location in schedule 2s 109ms

And Check if dates in transport form are correct 3s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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 108ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 336ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 193ms

And Click pencil and move transport to next day in schedule 16s 384ms

Then Check if transport is in new location in schedule 2s 087ms

And Check if dates in transport form are correct 3s 432ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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 165ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 416ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 211ms

And Click pencil and move transport to next day in schedule 16s 235ms

Then Check if transport is in new location in schedule 2s 142ms

And Check if dates in transport form are correct 3s 302ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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 223ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 400ms

And Show all transport "true" 054ms

When Find transport pencil button in transports table 1s 192ms

And Click pencil and move transport to next day in schedule 16s 398ms

Then Check if transport is in new location in schedule 2s 117ms

And Check if dates in transport form are correct 3s 393ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 368ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 234ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 036ms

And Click button advice in transport table "DELIVERY" 091ms

And Set advice window in schedule 2s 575ms

And Fill advice form 8s 307ms

And Click advice save button and wait for advice form to disappear 30s 683ms

And Go to "TRANSPORT_TABLE" 224ms

And Find transport pencil button in transports table 1s 198ms

And Click pencil and move transport to next day in schedule 17s 515ms

Then Check if transport is in new location in schedule 2s 142ms

And Check if dates in transport form are correct 3s 416ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 723ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 464ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 223ms

And Click pencil and move transport to next day in schedule 16s 353ms

And Move advice window "3" 1s 323ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 078ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 257ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 226ms

And Click pencil and move transport to next day in schedule 16s 689ms

And Move advice window "3" 1s 371ms

Then Check if advice window is in new location 021ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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" 955ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 263ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 164ms

And Click pencil and move transport to next day in schedule 17s 218ms

And Move advice window "3" 1s 447ms

Then Check if advice window is in new location 015ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 135ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 307ms

And Show all transport "false" 005ms

When Find transport pencil button in transports table 1s 207ms

And Click pencil and move transport to next day in schedule 16s 306ms

And Move advice window "3" 1s 295ms

Then Check if advice window is in new location 019ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 176ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 353ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 202ms

And Click pencil and move transport to next day in schedule 16s 407ms

And Move advice window "3" 1s 304ms

Then Check if advice window is in new location 016ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 158ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 256ms

And Show all transport "true" 075ms

When Find transport pencil button in transports table 1s 220ms

And Click pencil and move transport to next day in schedule 16s 366ms

And Move advice window "3" 1s 327ms

Then Check if advice window is in new location 016ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 607ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 384ms

And Go to transport details "DELIVERY" 4s 733ms

When Open section: "discrepancy-report-panel" 1s 065ms

Then Verify that no discrepancies found label is visible in discrepancy report section 060ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 406ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 073ms

Hooks

After Hooks.deleteTransportAfterTest() 171ms

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 453ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 383ms

And Go to transport details "DELIVERY" 4s 707ms

And Fill transport form 35s 657ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 097ms

When Go to transport details "DELIVERY" 4s 414ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 391ms

And Click "save-transport" save button 695ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 020ms

And Verify that discrepancy report section contains validation errors 016ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 999ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 462ms

When Go to transport details "DELIVERY" 4s 759ms

Then Verify that discrepancy report section is available 034ms

And Open section: "discrepancy-report-panel" 1s 057ms

And Verify that generate new discrepancy report button is visible 042ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 368ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 297ms

When Go to transport details "OWN_COLLECTION" 4s 808ms

Then Verify that discrepancy report section is available 031ms

And Open section: "discrepancy-report-panel" 1s 051ms

And Verify that generate new discrepancy report button is visible 016ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 403ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 322ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 558ms

Then Verify that discrepancy report section is available 032ms

And Open section: "discrepancy-report-panel" 1s 050ms

And Verify that generate new discrepancy report button is visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 425ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 465ms

When Go to transport details "EXPORT" 5s 746ms

Then Verify that discrepancy report section is available 029ms

And Open section: "discrepancy-report-panel" 1s 058ms

And Verify that generate new discrepancy report button is visible 041ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 298ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 166ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 741ms

Then Verify that discrepancy report section is available 025ms

And Open section: "discrepancy-report-panel" 1s 043ms

And Verify that generate new discrepancy report button is visible 037ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 346ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 373ms

When Go to transport details "CISTERN_DELIVERY" 4s 469ms

Then Verify that discrepancy report section is not available 15s 033ms

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 432ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 285ms

When Go to transport details "CISTERN_COLLECTION" 4s 456ms

Then Verify that discrepancy report section is not available 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 736ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 318ms

When Go to transport details "WEIGHING" 4s 425ms

Then Verify that discrepancy report section is not available 15s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 874ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 436ms

When Go to "TRANSPORT_TABLE" 115ms

And Go to transport details "DELIVERY" 4s 672ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 560ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 325ms

And Open section: "discrepancy-report-panel" 1s 057ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 35s 588ms

And Fill discrepancy report section without closing the form 19s 293ms

And Generate discrepancy report 16s 731ms

And Download discrepancy report 125ms

Then Verify that discrepancy report file has correct values 15s 154ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/49_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:250)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 380ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 346ms

When Go to "TRANSPORT_TABLE" 143ms

And Go to transport details "DELIVERY" 4s 916ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 35s 776ms

And Open section: "discrepancy-report-panel" 1s 066ms

And Fill discrepancy report section without closing the form 19s 260ms

And Generate discrepancy report 1s 239ms

And Download discrepancy report 129ms

And Verify that discrepancy report file has correct values 15s 127ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/50_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:250)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:93)

And Fill edited discrepancy report section 000ms

And Generate edited discrepancy report 000ms

And Download discrepancy report 000ms

Then Verify that discrepancy report file has correct values 000ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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" 112ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 041ms

And Get "LOAD" settings from "piast" 029ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 074ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 199ms

And Login as "piast-admin" 1s 432ms

And Go to "TRANSPORT_TABLE" 243ms

When Go to transport details "LOAD" 4s 679ms

And Add step "unload" 096ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 482ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 453ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 611ms

And Go to transport details "LOAD" 4s 556ms

And Verify that transport has "3" steps 014ms

Hooks

After Hooks.deleteTransportAfterTest() 061ms

After Hooks.rollbackTransportTypeSettings() 041ms

After Hooks.rollbackAddedActionAuthorities() 022ms

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" 1s 888ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 379ms

When Go to "TRANSPORT_TABLE" 113ms

And Go to transport details "SMALLS_IMPORT" 17s 077ms

Then Verify that user can't edit time range for load and unload 15s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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" 113ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 340ms

And Login as "neuca-admin" 905ms

And Go to "TRANSPORT_TABLE" 271ms

And Show all transport types 15s 051ms

When Go to transport details "DELIVERY" 32s 532ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 048ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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" 107ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 311ms

And Login as "hochland-admin" 1s 636ms

And Go to "TRANSPORT_TABLE" 142ms

And Show all transport types 1s 071ms

When Go to transport details "EXPORT" 5s 614ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 055ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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" 110ms

And Get "DELIVERY" settings from "neuca" 039ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 087ms

And Login as "neuca-admin" 853ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 292ms

When Go to "TRANSPORT_TABLE" 203ms

And Go to transport details "DELIVERY" 32s 476ms

And Set number of pallets in "load" step in transport - "32" 115ms

And Check if number of pallets check message is not visible in transport form 15s 052ms

And Set number of pallets in "load" step in transport - "34" 108ms

Then Check if number of pallets check message is visible in transport form 034ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.rollbackTransportTypeSettings() 130ms

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" 209ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 046ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 035ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 059ms

And Login as "farmacol-admin" 1s 583ms

And Go to new transport "EXTERNAL_DELIVERY" 371ms

And Add step "unload" 084ms

And Click "save-transport-and-close" save button 694ms

Then Verify that "time-range-from-date-2" has validation error 1s 023ms

Then Verify that "time-range-to-date-2" has validation error 1s 026ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 289ms

And Click "save-transport-and-close" save button 690ms

And Verify that "time-range-from-date-2" has no validation error 015ms

And Verify that "time-range-to-date-2" has no validation error 014ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.rollbackTransportTypeSettings() 058ms

After Hooks.rollbackAddedActionAuthorities() 031ms

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" 103ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 032ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 240ms

When Login as "piast-admin" 1s 461ms

And Go to transport details "LOAD" 4s 798ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 120ms

And Fill step data 14s 921ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 001ms

And Add step "load" 126ms

And Fill step data 5s 467ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

Then Go to transport details "LOAD" 4s 616ms

And Check if "unload" step is added as "3" step in transport form 030ms

And Check if "load" step is added as "4" step in transport form 033ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.rollbackAddedActionAuthorities() 036ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackRemovedActionAuthorities

Scenario Outline Check if step is draggable according to authority @A-6865

Steps

Given Set token of apiUsername "super-admin-skz" 111ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 035ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 004ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 240ms

When Login as "super-admin-skz" 2s 204ms

And Go to transport details "SMALLS_EXPORT" 4s 545ms

And Check if step is draggable "LOAD" 023ms

And Check if step is not draggable "UNLOAD" 017ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.rollbackAddedActionAuthorities() 031ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created without advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 005ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 146ms

When Go to new transport "SMALLS_IMPORT" 386ms

And Fill transport form 19s 642ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 594ms

And Show all transport "false" 007ms

And Go to transport details "SMALLS_IMPORT" 4s 502ms

And Click create similar button 15s 181ms

And Fill "transport" form "CREATE_SIMILAR_SMALLS_IMPORT" by "super-admin-skz" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 571ms

And Open similar transport details 263ms

Then Check are transport values equals 2s 101ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.deleteSimilarTransportAfterTest() 131ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created without advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 587ms

When Go to new transport "TRANSPORT_ORDER" 462ms

And Fill transport form 23s 680ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 630ms

And Show all transport "true" 088ms

And Go to transport details "TRANSPORT_ORDER" 4s 600ms

And Click create similar button 15s 171ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT_ORDER" by "super-admin-alrec" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 618ms

And Open similar transport details 272ms

Then Check are transport values equals 2s 188ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

After Hooks.deleteSimilarTransportAfterTest() 049ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created with advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 006ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 728ms

When Go to new transport "DELIVERY" 15s 397ms

And Fill transport form 35s 533ms

And Click "save-transport" save button and wait for form to disappear 15s 658ms

And Set advice window in schedule 2s 134ms

And Check is transport created in schedule and set transport id 804ms

And Go to "TRANSPORT_TABLE" 181ms

And Go to transport details "DELIVERY" 32s 360ms

And Click create similar button 15s 144ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 348ms

And Click "save-transport" save button and wait for form to disappear 10s 526ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@type='submit' and @data-field-name='save-transport'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.jKzpZs}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: d802efd668825be5b2b300d32c864374
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport" save button and wait for form to disappear(file:Features/Atom/Transport/TransportForm/TransportForm.feature:37)

And Set advice window in schedule in "2" days 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Open similar transport details 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 023ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteTransportAfterTest(Hooks.java:174)
	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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

After Hooks.deleteSimilarTransportAfterTest() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct carrier

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 001ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 013ms

When Go to new transport "DELIVERY" 15s 349ms

And Fill transport form 35s 552ms

And Click "save-transport" save button and wait for form to disappear 15s 645ms

And Set advice window in schedule 2s 141ms

And Check is transport created in schedule and set transport id 15s 038ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='slot-114767102-2021-05-09-00-15']//div[@data-transport-id]"}
  (Session info: headless chrome=90.0.4430.93)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.jKzpZs}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: d802efd668825be5b2b300d32c864374
*** Element info: {Using=xpath, value=//div[@id='slot-114767102-2021-05-09-00-15']//div[@data-transport-id]}
	at sun.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.Schedule.SchedulePage.getTransportId(SchedulePage.java:161)
	at CucumberTests.Transport.AdviceTransport.checkIsTransportCreatedInScheduleAndSetTransportId(AdviceTransport.java:157)
	at ✽.Check is transport created in schedule and set transport id(file:Features/Atom/Transport/TransportForm/TransportForm.feature:56)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

And Click create similar button 000ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 000ms

And Click "save-transport" save button and wait for form to disappear 000ms

And Set advice window in schedule in "2" days 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Open similar transport details 000ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

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" 001ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 425ms

When Go to new transport "SMALLS_IMPORT" 558ms

And Fill transport form 32s 755ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 594ms

And Go to transport details "SMALLS_IMPORT" 4s 365ms

And Go to transport print details form 3s 102ms

Then Check are transport values equals 8s 248ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 310ms

And Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 238ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 195ms

And Go to transport details "SMALLS_IMPORT" 4s 477ms

Then Verify that the transport can be edited 1s 273ms

And Close transport details 15s 088ms

And If user is login then logout 087ms

And Login as "pskza1-carrier@qa.qa-test" 1s 402ms

And Go to transport details "SMALLS_IMPORT" 4s 488ms

And Verify that the transport cannot be edited 46s 280ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 377ms

And Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 247ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 078ms

And Go to transport details "SMALLS_EXPORT" 4s 565ms

Then Verify that the transport can be edited 1s 263ms

And Close transport details 15s 091ms

And If user is login then logout 341ms

And Login as "pskza1-carrier@qa.qa-test" 1s 233ms

And Go to transport details "SMALLS_EXPORT" 4s 519ms

And Verify that the transport cannot be edited 46s 284ms

Hooks

After Hooks.deleteTransportAfterTest() 150ms

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 442ms

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 314ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 098ms

And Go to transport details "SMALLS_IMPORT" 4s 467ms

Then Verify that the hidden data in transport are not visible 1s 039ms

And Close transport details 15s 116ms

And If user is login then logout 102ms

And Login as "swisskrono-admin" 1s 504ms

And Go to transport details "SMALLS_IMPORT" 4s 525ms

And Verify that the hidden data in transport are visible 1s 227ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 110ms

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 252ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 112ms

And Go to transport details "SMALLS_EXPORT" 4s 441ms

Then Verify that the hidden data in transport are not visible 1s 028ms

And Close transport details 15s 134ms

And If user is login then logout 091ms

And Login as "swisskrono-admin" 1s 511ms

And Go to transport details "SMALLS_EXPORT" 4s 496ms

And Verify that the hidden data in transport are visible 1s 191ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 394ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 414ms

When Go to transport details "DELIVERY" 4s 770ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 309ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 507ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 567ms

And Fill discrepancy report section without closing the form 19s 481ms

And Click "save-transport" save button 1s 215ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Check if transport details form is disappeared 15s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 113ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 036ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 254ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 296ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 3s 572ms

When Go to "TRANSPORT_TABLE" 230ms

And Go to transport details "DELIVERY" 4s 747ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 313ms

Then Verify that "transport-description" in transport has value "opis" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.rollbackAddedActionAuthorities() 028ms

After Hooks.rollbackWarehousesAccess() 143ms

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" 107ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 313ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 044ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 122ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 756ms

When Go to "TRANSPORT_TABLE" 168ms

And Go to transport details "DELIVERY" 4s 735ms

Then Verify that "transport-description" in transport form is disabled 028ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.rollbackRemovedActionAuthorities() 040ms

After Hooks.rollbackWarehousesAccess() 114ms

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" 151ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 027ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 313ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 733ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 216ms

And Go to transport details "DELIVERY" 4s 901ms

Then Verify that "CARRIER" in transport form is visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.rollbackAddedActionAuthorities() 026ms

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" 112ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 033ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 176ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 322ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "TRANSPORT" 4s 487ms

Then Verify that "CARRIER" in transport form is visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 052ms

After Hooks.rollbackAddedActionAuthorities() 029ms

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" 152ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 033ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 208ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 651ms

And Show all transport "true" 068ms

When Go to "TRANSPORT_TABLE" 114ms

And Go to transport details "TRANSPORT_ORDER" 4s 435ms

Then Verify that "CARRIER" in transport form is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

After Hooks.rollbackAddedActionAuthorities() 029ms

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" 119ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 071ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 337ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 953ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 290ms

And Go to transport details "DELIVERY" 4s 703ms

Then Verify that "CARRIER" in transport form is not visible 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.rollbackRemovedActionAuthorities() 038ms

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" 104ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 027ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 175ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 447ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 169ms

And Go to transport details "TRANSPORT" 4s 448ms

Then Verify that "CARRIER" in transport form is not visible 15s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

After Hooks.rollbackRemovedActionAuthorities() 041ms

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" 126ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 026ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 188ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 488ms

And Show all transport "true" 067ms

When Go to "TRANSPORT_TABLE" 124ms

And Go to transport details "TRANSPORT_ORDER" 4s 945ms

Then Verify that "CARRIER" in transport form is not visible 15s 057ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

After Hooks.rollbackRemovedActionAuthorities() 037ms

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" 112ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 373ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 824ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 202ms

And Go to transport details "DELIVERY" 4s 732ms

Then Verify that "CARRIER" in transport form is not disabled 022ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.rollbackAddedActionAuthorities() 112ms

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" 120ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 042ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 200ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 402ms

And Show all transport "false" 007ms

When Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "TRANSPORT" 4s 697ms

Then Verify that "CARRIER" in transport form is not disabled 024ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

After Hooks.rollbackAddedActionAuthorities() 064ms

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" 109ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 048ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 175ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 568ms

And Show all transport "true" 070ms

When Go to "TRANSPORT_TABLE" 115ms

And Go to transport details "TRANSPORT_ORDER" 4s 484ms

Then Verify that "CARRIER" in transport form is not disabled 023ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.rollbackAddedActionAuthorities() 056ms

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" 100ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 038ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 279ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 443ms

And Show all transport "false" 011ms

When Go to "TRANSPORT_TABLE" 222ms

And Go to transport details "DELIVERY" 4s 731ms

Then Verify that "CARRIER" in transport form is disabled 021ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.rollbackAddedActionAuthorities() 031ms

After Hooks.rollbackRemovedActionAuthorities() 033ms

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" 110ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 033ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 005ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 265ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 633ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 105ms

And Go to transport details "TRANSPORT" 4s 491ms

Then Verify that "CARRIER" in transport form is disabled 026ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

After Hooks.rollbackAddedActionAuthorities() 027ms

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" 104ms

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" 006ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 199ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 889ms

And Show all transport "true" 096ms

When Go to "TRANSPORT_TABLE" 084ms

And Go to transport details "TRANSPORT_ORDER" 4s 423ms

Then Verify that "CARRIER" in transport form is disabled 019ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.rollbackAddedActionAuthorities() 025ms

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" 110ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 242ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 038ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 035ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 039ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 470ms

When Find transport in table with status "planned" 3s 295ms

And Confirm statuses until reach "process-ended" 21s 503ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 263ms

And Show "DELIVERY" 079ms

And Go to transport details "DELIVERY" 32s 437ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 312ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 604ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 356ms

Then Verify that "transport-description" in transport has value "opis" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.rollbackAddedActionAuthorities() 040ms

After Hooks.rollbackRemovedActionAuthorities() 077ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 152ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 390ms

When Go to transport details "DELIVERY" 4s 669ms

And Fill transport form 35s 716ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 351ms

And Click "save-transport-and-close" save button and wait for form to disappear 695ms

And Go to new transport "DELIVERY" 247ms

Then Verify that driver "XXX ZZZ" is in list 15s 073ms

Error message

java.lang.AssertionError: Kierowca XXX ZZZ nie jest widoczny na liście kierowców w formularzu zlecenia!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.TransportFormTest.verifyThatDriverIsInList(TransportFormTest.java:353)
	at ✽.Verify that driver "XXX ZZZ" is in list(file:Features/Atom/Transport/TransportForm/TransportForm.feature:265)

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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 404ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 238ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 076ms

And If user is login then logout 088ms

And Login as "pskza1-carrier@qa.qa-test" 1s 345ms

Then Verify that the transport has been transferred 1s 149ms

And Accept or reject "accept" transferred transport 15s 794ms

And Go to transport details "SMALLS_IMPORT" 4s 560ms

And Verify that "transaction-price" in transport form is visible 041ms

And Verify that transaction price field has correct value 015ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 326ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 279ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 092ms

And If user is login then logout 108ms

And Login as "pskza1-carrier@qa.qa-test" 1s 366ms

Then Verify that the transport has been transferred 1s 123ms

And Accept or reject "accept" transferred transport 15s 753ms

And Go to transport details "SMALLS_EXPORT" 4s 514ms

And Verify that "transaction-price" in transport form is visible 028ms

And Verify that transaction price field has correct value 021ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

Given Set token of apiUsername "super-admin-dayco" 102ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 202ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 1s 586ms

And Click button advice in transport table "OWN_COLLECTION" 211ms

And Set advice window in schedule 2s 512ms

And Fill advice form 6s 869ms

And Click advice save button and wait for advice form to disappear 30s 640ms

And Go to "TRANSPORT_TABLE" 167ms

And Find transport in table with status "planned" 3s 196ms

And Confirm statuses until reach "on-the-area" 3s 780ms

And Go to transport details "OWN_COLLECTION" 4s 403ms

And Click create similar button 15s 086ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 568ms

And Click "save-transport-and-close" save button and wait for form to disappear 10s 549ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@type='submit' and @data-field-name='save-transport-and-close'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.jKzpZs}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: d802efd668825be5b2b300d32c864374
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/Transport/TransportForm/TransportForm.feature:368)

And Open similar transport details 000ms

Then Check if transport form modal is visible 000ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

Given Set token of apiUsername "super-admin-dayco" 112ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 190ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 1s 030ms

And Click button advice in transport table "OWN_COLLECTION" 306ms

And Set advice window in schedule 2s 481ms

And Fill advice form 6s 811ms

And Click advice save button and wait for advice form to disappear 30s 693ms

And Go to "TRANSPORT_TABLE" 174ms

And Find transport in table with status "planned" 3s 213ms

And Confirm statuses until reach "during-load" 7s 019ms

And Go to transport details "OWN_COLLECTION" 4s 368ms

And Click create similar button 15s 189ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 476ms

And Click "save-transport-and-close" save button and wait for form to disappear 10s 514ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@type='submit' and @data-field-name='save-transport-and-close'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.jKzpZs}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: d802efd668825be5b2b300d32c864374
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/Transport/TransportForm/TransportForm.feature:368)

And Open similar transport details 000ms

Then Check if transport form modal is visible 000ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 487ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 246ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 072ms

When Click invoice button 2s 393ms

And Set default invoice currency value 054ms

Then Check that default currency value in invoice form is "EUR" 041ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_IMPORT" and principal alias "swisskrono" 002ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updateInvoiceDefaultCurrency(ApolloUpdateDbService.java:55)
	at CucumberTests.Transport.InvoiceTest.changeDefaultCurrencyValueInDatabaseForInTransportType(InvoiceTest.java:48)
	at ✽.Change invoice default currency value in database for "USD" transport type alias "SMALLS_IMPORT" and principal alias "swisskrono"(file:Features/Atom/Transport/TransportTable/Invoice.feature:11)

And Clear all cache 000ms

And Login as "swisskrono-admin" 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Show all transport types 000ms

And Click invoice button 000ms

Then Check that default currency value in invoice form is "USD" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.rollbackInvoiceCurrency() 000ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updateInvoiceDefaultCurrency(ApolloUpdateDbService.java:55)
	at CucumberTests.Hooks.rollbackInvoiceCurrency(Hooks.java:633)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 275ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 232ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 085ms

When Click invoice button 2s 498ms

And Set default invoice currency value 040ms

Then Check that default currency value in invoice form is "EUR" 034ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_EXPORT" and principal alias "swisskrono" 002ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updateInvoiceDefaultCurrency(ApolloUpdateDbService.java:55)
	at CucumberTests.Transport.InvoiceTest.changeDefaultCurrencyValueInDatabaseForInTransportType(InvoiceTest.java:48)
	at ✽.Change invoice default currency value in database for "USD" transport type alias "SMALLS_EXPORT" and principal alias "swisskrono"(file:Features/Atom/Transport/TransportTable/Invoice.feature:11)

And Clear all cache 000ms

And Login as "swisskrono-admin" 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Show all transport types 000ms

And Click invoice button 000ms

Then Check that default currency value in invoice form is "USD" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.rollbackInvoiceCurrency() 000ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updateInvoiceDefaultCurrency(ApolloUpdateDbService.java:55)
	at CucumberTests.Hooks.rollbackInvoiceCurrency(Hooks.java:633)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport details button is not shown

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 1s 120ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 300ms

And Show all transport types 1s 030ms

Then Check if transport number is visible "DELIVERY" 15s 048ms

And Check if transport details is not visible 15s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 116ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 116ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 370ms

When Click on transport row 047ms

Then Verify if transport row is selected 028ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 500ms

And Show all transport "false" 013ms

And Go to "TRANSPORT_TABLE" 151ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 350ms

When Click on transport row 050ms

Then Verify if transport row is selected 022ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 275ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 098ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 266ms

When Click on transport row 072ms

Then Verify if transport row is selected 019ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 597ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 106ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 294ms

When Click on transport row 046ms

Then Verify if transport row is selected 025ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 473ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 122ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 293ms

When Click on transport row 048ms

Then Verify if transport row is selected 022ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 362ms

And Show all transport "true" 059ms

And Go to "TRANSPORT_TABLE" 114ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 242ms

When Click on transport row 066ms

Then Verify if transport row is selected 019ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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" 2s 227ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 236ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 096ms

When Accept or reject "accept" transferred transport 17s 548ms

Then Verify that transport is accept or reject "accept" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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 703ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 272ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 048ms

When Accept or reject "reject" transferred transport 17s 540ms

Then Verify that transport is accept or reject "reject" 15s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 033ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 337ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 058ms

When Accept or reject "accept" transferred transport 18s 043ms

Then Verify that transport is accept or reject "accept" 015ms

Hooks

After Hooks.deleteTransportAfterTest() 048ms

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 181ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 401ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 058ms

When Accept or reject "reject" transferred transport 17s 942ms

Then Verify that transport is accept or reject "reject" 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

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 179ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 272ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 069ms

When Accept or reject "accept" transferred transport 18s 668ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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 254ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 230ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 067ms

When Accept or reject "reject" transferred transport 18s 541ms

Then Verify that transport is accept or reject "reject" 15s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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 516ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 208ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 081ms

And If user is login then logout 100ms

And Login as "paa1-carrier@qa.qa-test" 1s 390ms

Then Verify that the transport has been transferred with "true" 1s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 057ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 205ms

And If user is login then logout 085ms

And Login as "paa1-carrier@qa.qa-test" 1s 250ms

Then Verify that the transport has been transferred with "false" 1s 182ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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 136ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 202ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 047ms

And If user is login then logout 090ms

And Login as "pskza1-carrier@qa.qa-test" 1s 552ms

Then Verify that the transport has been transferred 1s 127ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 343ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 249ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 079ms

And If user is login then logout 210ms

And Login as "pskza1-carrier@qa.qa-test" 1s 265ms

Then Verify that the transport has been transferred 1s 125ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 213ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 409ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 145ms

And Go to auction offer 1s 166ms

When Offer "1000" 174ms

And Verify that offer with "1000" has been added to auction 3s 028ms

And If user is login then logout 061ms

And Login as "swisskrono-admin" 1s 204ms

Then Go to auction details 1s 224ms

And Pass transport to carrier from auction details 1s 107ms

And If user is login then logout 798ms

And Login as "pskza1-carrier@qa.qa-test" 1s 281ms

And Verify that the transport has been transferred 1s 136ms

Hooks

After Hooks.deleteTransportAfterTest() 182ms

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 366ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 339ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 109ms

And Go to auction offer 1s 168ms

When Offer "1000" 127ms

And Verify that offer with "1000" has been added to auction 3s 026ms

And Wait till auction end 1m 54s 013ms

And If user is login then logout 115ms

Then Login as "swisskrono-admin" 1s 336ms

And Go to auction details 1s 179ms

And Pass transport to carrier from auction details 1s 143ms

And If user is login then logout 1s 031ms

And Login as "pskza1-carrier@qa.qa-test" 1s 292ms

And Verify that the transport has been transferred 1s 091ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 319ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 298ms

And Go to "TRANSPORT_TABLE" 107ms

When Open transport transfer modal 1s 202ms

Then Verify that all enabled companies from "swisskrono" are shown in select 105ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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" 124ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 328ms

And Login as "adama-admin" 1s 150ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 212ms

And Go to "TRANSPORT_TABLE" 111ms

When Open transport transfer modal 1s 213ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 087ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

After Hooks.rollbackRejectedSections() 078ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if transport is not visible to carrier after expiring of time to accept transport [A-7037]

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 088ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 186ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 147ms

And If user is login then logout 299ms

When Login as "paa1-carrier@qa.qa-test" 1s 895ms

And Verify that the transport has been transferred with "true" 1s 174ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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 141ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 345ms

When Go to "TRANSPORT_TABLE" 110ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 396ms

Then Check if new assortment group is disabled in transport form 025ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 094ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 205ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 001ms

When Show all transport types 1s 023ms

And Click button advice in transport table "CONTAINER" 075ms

And Set advice window in schedule 2s 415ms

And Click button cancel in advice form 15s 316ms

And Set advice window in schedule 2s 171ms

And Click button cancel in advice form 15s 237ms

And Set advice window in schedule 2s 117ms

And Fill advice form 15s 728ms

And Click advice save button and wait for advice form to disappear 30s 664ms

And Go to "TRANSPORT_TABLE" 155ms

And Go to transport details "CONTAINER" 4s 421ms

Then Check are advice values equals 2s 320ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 128ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 001ms

When Go to new transport "TRANSPORT" 375ms

And Fill transport form 26s 778ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 632ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 152ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 102ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 780ms

And Accept or reject "reject" transferred transport 15s 748ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 183ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 195ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 482ms

And Accept or reject "accept" transferred transport 15s 846ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 105ms

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 181ms

When Show all transport types 1s 040ms

And Click button advice in transport table "DELIVERY" 076ms

And Set advice window in schedule 2s 612ms

And Click button cancel in advice form 15s 291ms

And Go to "TRANSPORT_TABLE" 211ms

When Go to transport details "DELIVERY" 4s 527ms

And Fill transport form 1m 1s 921ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 616ms

And Go to transport details "DELIVERY" 4s 431ms

Then Check are transport values equals 24s 658ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3400	40	91	0	0	3531	346	41	387	5h 49m 10s 583ms	Failed

Tag Report