Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.404	30 kwi 2021, 06:11

	Steps	Scenarios	Features
@deleteTransportAfterTest	3426	30	49	0	0	3505	353	32	385	5h 45m 13s 886ms	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 213ms

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

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

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

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

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

And Fill advice form 16s 095ms

And Click advice save button to check error message 068ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 323ms

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

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

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

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

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

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

And Fill advice form 8s 307ms

And Click advice save button to check error message 070ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

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

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

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

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

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

And Fill advice form 8s 355ms

And Click advice save button to check error message 080ms

Then Check if possible advice alert is displayed 021ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

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

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

And Fill advice form 13s 130ms

And Click advice save button to check error message 080ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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

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

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

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

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

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

And Fill advice form 13s 038ms

And Click advice save button to check error message 069ms

Then Check if possible advice alert is displayed 011ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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

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

And Show all transport types 1s 042ms

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

And Go to "TRANSPORT_TABLE" 222ms

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

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

And Fill transport form 4s 678ms

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

And Expand advice panel 106ms

And Edit advice in transport details 12s 244ms

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

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

And Expand advice panel 101ms

Then Check are advice values equals after edition 189ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

And Show all transport types 1s 036ms

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

And Go to "TRANSPORT_TABLE" 262ms

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

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

And Fill transport form 1m 1s 850ms

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

And Expand advice panel 105ms

And Edit advice in transport details 6s 511ms

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

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

And Expand advice panel 094ms

Then Check are advice values equals after edition 085ms

Hooks

After Hooks.deleteTransportAfterTest() 255ms

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

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

And Show all transport types 1s 042ms

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

And Go to "TRANSPORT_TABLE" 173ms

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

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

And Fill transport form 56s 786ms

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

And Expand advice panel 092ms

And Edit advice in transport details 6s 544ms

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

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

And Expand advice panel 110ms

Then Check are advice values equals after edition 085ms

Hooks

After Hooks.deleteTransportAfterTest() 213ms

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

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

And Show all transport types 1s 039ms

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

And Go to "TRANSPORT_TABLE" 195ms

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

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

And Fill transport form 24s 532ms

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

And Expand advice panel 095ms

And Edit advice in transport details 18s 412ms

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

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

And Expand advice panel 102ms

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

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 040ms

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

And Go to "TRANSPORT_TABLE" 153ms

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

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

And Fill transport form 24s 528ms

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

And Expand advice panel 101ms

And Edit advice in transport details 18s 350ms

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

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

And Expand advice panel 100ms

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

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 406ms

And Fill advice form 12s 283ms

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

And Go to "TRANSPORT_TABLE" 172ms

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

Then Check are advice values equals 286ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 6s 467ms

And Fill advice form 11s 665ms

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

And Go to "TRANSPORT_TABLE" 165ms

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

Then Check are advice values equals 2s 256ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

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

When Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 585ms

And Fill advice form 8s 199ms

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

And Go to "TRANSPORT_TABLE" 207ms

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

Then Check are advice values equals 182ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 613ms

And Fill advice form 8s 204ms

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

And Go to "TRANSPORT_TABLE" 179ms

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

Then Check are advice values equals 183ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 446ms

And Fill advice form 13s 036ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

Then Check are advice values equals 2s 305ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 441ms

And Fill advice form 12s 901ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

Then Check are advice values equals 2s 288ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

And Accept transferred transport by Api 407ms

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

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

When Show all transport types 1s 288ms

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

And Set advice window in schedule 2s 449ms

And Fill advice form 11s 696ms

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

And Go to "TRANSPORT_TABLE" 224ms

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

Then Check are advice values equals 2s 260ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

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

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

And Accept transferred transport by Api 131ms

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

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

When Show all transport types 1s 096ms

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

And Set advice window in schedule 2s 693ms

And Fill advice form 14s 349ms

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

And Go to "TRANSPORT_TABLE" 165ms

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

Then Check are advice values equals 2s 278ms

Hooks

After Hooks.deleteTransportAfterTest() 169ms

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

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

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

And Accept transferred transport by Api 120ms

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

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

When Show all transport types 1s 111ms

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

And Set advice window in schedule 2s 677ms

And Fill advice form 14s 333ms

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

And Go to "TRANSPORT_TABLE" 175ms

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

Then Check are advice values equals 2s 269ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

And Accept transferred transport by Api 103ms

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

When Show all transport types 1s 077ms

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

And Set week view 1s 510ms

And Show yesterday 1s 076ms

Then Check if advice restriction blockade windows are visible 018ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Accept transferred transport by Api 094ms

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

When Show all transport types 1s 100ms

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

And Set week view 1s 992ms

And Show yesterday 1s 109ms

Then Check if advice restriction blockade windows are visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Accept transferred transport by Api 102ms

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

When Show all transport types 1s 106ms

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

And Set week view 1s 912ms

And Show yesterday 1s 108ms

Then Check if advice restriction blockade windows are visible 022ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 023ms

And Click on time window date 1s 282ms

And Select view "DAYS_4" 2s 053ms

And Move advice window "3" 1s 301ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

And Show all transport "false" 013ms

And Click on time window date 15s 683ms

And Select view "DAYS_4" 2s 058ms

And Move advice window "3" 1s 432ms

Then Check if advice window is in new location 031ms

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 "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 290ms

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

And Show all transport "false" 015ms

And Click on time window date 15s 535ms

And Select view "DAYS_4" 2s 059ms

And Move advice window "3" 1s 362ms

Then Check if advice window is in new location 025ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 410ms

And Select view "DAYS_4" 2s 047ms

And Move advice window "3" 1s 339ms

Then Check if advice window is in new location 021ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

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

And Show all transport "false" 017ms

And Click on time window date 1s 264ms

And Select view "DAYS_4" 2s 069ms

And Move advice window "3" 1s 301ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

And Show all transport "true" 078ms

And Click on time window date 1s 317ms

And Select view "DAYS_4" 2s 056ms

And Move advice window "3" 1s 344ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

When Show all transport types 1s 032ms

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

And Set advice window in schedule 2s 594ms

And Fill advice form 8s 196ms

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

And Go to "TRANSPORT_TABLE" 208ms

And Click on time window date 1s 398ms

And Select view "DAYS_4" 2s 051ms

And Move advice window "3" 1s 381ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

And Go to "TRANSPORT_TABLE" 115ms

And Show all transport types 1s 027ms

And Click on time window date 1s 262ms

And Scroll to time window "adviceWindow" 040ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

And Go to "TRANSPORT_TABLE" 107ms

And Show all transport types 1s 037ms

And Click on time window date 1s 384ms

And Scroll to time window "adviceWindow" 029ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

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

And Go to "TRANSPORT_TABLE" 110ms

And Show all transport types 1s 026ms

And Click on time window date 1s 320ms

And Scroll to time window "adviceWindow" 026ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 283ms

And Show all transport types 15s 042ms

And Click on time window date 15s 763ms

And Scroll to time window "adviceWindow" 034ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 608ms

And Fill advice form 8s 241ms

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

And Go to "TRANSPORT_TABLE" 182ms

And Click on time window date 1s 372ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

And Go to "WAREHOUSE_TAB" 818ms

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

When Go to new transport "DELIVERY" 334ms

And Fill transport form 39s 355ms

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

And Click previous page button in browser 017ms

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

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

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

And Go to "WAREHOUSE_TAB" 766ms

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

When Go to new transport "DELIVERY" 341ms

And Fill transport form 39s 315ms

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

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

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

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

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

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

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

And Fill advice form 11s 579ms

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

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

And Open statuses popup 097ms

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

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

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

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

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

And Go to "WAREHOUSE_TAB" 649ms

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

And Set week view 2s 231ms

And Move cursor over time window element 386ms

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

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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

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

And Fill transport form 34s 195ms

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

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

And Set advice window in schedule 2s 159ms

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

Then Go to "OWN_COMPANY_TAB" 225ms

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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

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

And Fill transport form 16s 128ms

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

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

And Set advice window in schedule 2s 130ms

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

Then Go to "OWN_COMPANY_TAB" 275ms

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

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

When Go to "TRANSPORT_TABLE" 188ms

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

And Show all transport types 1s 069ms

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

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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

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

When Go to "TRANSPORT_TABLE" 171ms

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

And Show all transport types 1s 072ms

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

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 110ms

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

And Show all transport types 1s 080ms

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

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 129ms

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

And Show all transport types 1s 088ms

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

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

And Delete created transport by API 112ms

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

When Go to "ARCHIVE_TAB" 204ms

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

And Show "SMALLS_IMPORT" 087ms

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

And Delete created transport by API 122ms

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

When Go to "ARCHIVE_TAB" 194ms

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

And Show "SMALLS_IMPORT" 076ms

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

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

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

And Delete created transport by API 107ms

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

When Go to "ARCHIVE_TAB" 243ms

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

And Show "SMALLS_IMPORT" 085ms

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

And Delete created transport by API 091ms

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

When Go to "ARCHIVE_TAB" 207ms

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

And Show "SMALLS_IMPORT" 084ms

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

Hooks

After Hooks.deleteTransportAfterTest() 186ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 129ms

And Show all transport "true" 073ms

And Select transportType "TRANSPORT_ORDER" 1s 136ms

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

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 234ms

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

And Toggle transport table days limit filter 093ms

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

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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

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

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

When Go to "TRANSPORT_TABLE" 116ms

And Go to auction form 1s 313ms

And Select contractors group "Kraj" 079ms

Then Verify that carrier "PSKZA1" is selected 022ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.removeContractorsGroup() 082ms

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

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

When Go to "TRANSPORT_TABLE" 135ms

And Go to auction form 1s 205ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Grouping of carriers

@deleteTransportAfterTest

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 117ms

And Go to auction form 1s 220ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 014ms

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

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

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

And Expand index panel 108ms

And Click add index button 127ms

And Fill index form 10s 495ms

And Click ok button in index form 15s 142ms

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

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

And Expand index panel 112ms

Then Check are transport values equals 103ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteProductAfterTest() 076ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Show all transport "true" 082ms

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

And Expand index panel 096ms

And Click add index button 118ms

And Fill index form 7s 473ms

And Click ok button in index form 15s 118ms

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

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

And Expand index panel 125ms

Then Check are transport values equals 2s 136ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

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

And Add index to transport 25s 895ms

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

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

And Expand index panel 111ms

And Click delete index button 081ms

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

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

And Expand index panel 090ms

Then Verify that transport has no indexes 15s 055ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteProductAfterTest() 030ms

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

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

And Show all transport "true" 092ms

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 Add index to transport 22s 906ms

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

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

And Expand index panel 118ms

And Click delete index button 059ms

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

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

And Expand index panel 105ms

Then Verify that transport has no indexes 15s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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

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

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

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

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

And Add index to transport 24s 590ms

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

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

When Click on index details icon 095ms

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.deleteProductAfterTest() 040ms

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

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 446ms

And Fill advice form 11s 814ms

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

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

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

After Hooks.cleanUserDetailsAfterTest() 147ms

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

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

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 666ms

And Fill advice form 8s 332ms

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

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

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

After Hooks.cleanUserDetailsAfterTest() 124ms

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

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

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

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

And Show all transport types 1s 069ms

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

And Set advice window in schedule 2s 505ms

And Fill advice form 13s 165ms

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

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

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

After Hooks.cleanUserDetailsAfterTest() 146ms

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

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

And Show all transport types 1s 041ms

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

And Go to "TRANSPORT_TABLE" 199ms

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

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

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

And Fill transport form 4s 717ms

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

And Expand advice panel 114ms

And Edit advice in transport details 12s 367ms

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

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

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

After Hooks.cleanUserDetailsAfterTest() 127ms

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

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

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

And Show all transport types 1s 044ms

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

And Go to "TRANSPORT_TABLE" 222ms

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

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

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

And Fill transport form 1m 2s 317ms

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

And Expand advice panel 097ms

And Edit advice in transport details 6s 584ms

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

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

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

After Hooks.cleanUserDetailsAfterTest() 112ms

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

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

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

And Show all transport types 1s 048ms

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

And Go to "TRANSPORT_TABLE" 174ms

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

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

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

And Fill transport form 24s 733ms

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

And Expand advice panel 119ms

And Edit advice in transport details 18s 580ms

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

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

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

After Hooks.cleanUserDetailsAfterTest() 136ms

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

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 154ms

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

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

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

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

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

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.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:76)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test"(file:Features/Atom/Mail/AdviceMail.feature:67)

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

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.putObjectToApolloApi(RestUtil.java:92)
	at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:304)
	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() 006ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 178ms

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

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

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

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

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

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 "Nie otrzymano zlecenia" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 092ms

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 197ms

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 113ms

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

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

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 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.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() 095ms

After Hooks.cleanUserDetailsAfterTest() 115ms

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

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

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" 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() 086ms

After Hooks.cleanUserDetailsAfterTest() 104ms

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 106ms

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 121ms

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

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

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

And Go to "TRANSPORT_TABLE" 142ms

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

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

And Fill transport form 35s 864ms

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

And Fill discrepancy report section 35s 633ms

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

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

And Generate discrepancy report 18s 796ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

After Hooks.cleanUserDetailsAfterTest() 191ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 839ms

And Select warehouse "Serownia" 1s 424ms

And Set week view 1s 096ms

And Show yesterday 1s 066ms

And Move window into the past 301ms

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

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

After Hooks.cleanUserDetailsAfterTest() 303ms

After Hooks.rollbackAddedAuthorities() 045ms

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 195ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 181ms

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

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 123ms

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

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 122ms

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

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 258ms

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

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

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

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

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

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

Then If user is login then logout 077ms

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

And Go to auction details 1s 193ms

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

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

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

After Hooks.cleanUserDetailsAfterTest() 169ms

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

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 172ms

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

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

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

And Fill transport form 40s 950ms

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

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

And Set advice window in schedule 2s 208ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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

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

And Go to "TRANSPORT_TABLE" 255ms

And Show all transport "false" 007ms

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

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

And Click "save-transport" save button 694ms

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

Hooks

After Hooks.deleteTransportAfterTest() 135ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 068ms

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

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

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

And Go to "TRANSPORT_TABLE" 216ms

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

And Set advice window in schedule 2s 868ms

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

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.deleteModeOfTransportationAfterTest() 085ms

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

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

And Set status of MOT to "DISABLED" 075ms

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

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

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

And Go to "TRANSPORT_TABLE" 216ms

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

And Set advice window in schedule 2s 877ms

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

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.deleteModeOfTransportationAfterTest() 086ms

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

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

And Set status of MOT to "ACCEPTED" 078ms

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

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

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

And Go to "TRANSPORT_TABLE" 254ms

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

And Set advice window in schedule 2s 810ms

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteModeOfTransportationAfterTest() 086ms

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

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

And Set status of MOT to "UPDATED" 075ms

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

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

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

And Go to "TRANSPORT_TABLE" 207ms

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

And Set advice window in schedule 2s 846ms

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

And Set status of MOT to "REJECTED" 079ms

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

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

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

And Go to "TRANSPORT_TABLE" 226ms

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

And Set advice window in schedule 2s 816ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteModeOfTransportationAfterTest() 082ms

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

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

And Set status of MOT to "BLOCKED" 067ms

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

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

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

And Go to "TRANSPORT_TABLE" 208ms

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

And Set advice window in schedule 2s 818ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.deleteModeOfTransportationAfterTest() 090ms

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

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

And Add transport by SKApi in "MGW" 222ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 21s 126ms

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

And Set advice window in schedule 2s 668ms

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

And Fill advice form 14s 617ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 140ms

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

Then Check are transport values equals 357ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 136ms

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

Then Check are transport values equals 398ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 52s 045ms

And Go to "TRANSPORT_TABLE" 136ms

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

Then Check are transport values equals 379ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 120ms

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

Then Check are transport values equals 378ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 121ms

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

Then Check are transport values equals 357ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 003ms

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

And Go to "TRANSPORT_TABLE" 146ms

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

Then Check are transport values equals 397ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "" 003ms

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

And Go to "TRANSPORT_TABLE" 144ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

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 54s 427ms

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

And Set advice window in schedule 2s 700ms

And Fill advice form 14s 607ms

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

And Go to "TRANSPORT_TABLE" 213ms

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

Then Check are advice values equals 2s 306ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

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

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

And Set advice window in schedule 2s 568ms

And Fill advice form 14s 641ms

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

And Go to "TRANSPORT_TABLE" 199ms

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

Then Check are advice values equals 2s 334ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

And Set advice window in schedule 2s 613ms

And Fill advice form 14s 613ms

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

And Go to "TRANSPORT_TABLE" 253ms

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

Then Check are advice values equals 2s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

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

And Set advice window in schedule 2s 600ms

And Fill advice form 14s 593ms

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

And Go to "TRANSPORT_TABLE" 219ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Set advice window in schedule 2s 617ms

And Fill advice form 14s 629ms

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

And Go to "TRANSPORT_TABLE" 190ms

Then Check advice data in SK API database "CONTAINER" 4s 138ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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

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

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

And Set advice window in schedule 2s 642ms

And Fill advice form 14s 543ms

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

And Go to "TRANSPORT_TABLE" 228ms

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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 9s 375ms

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

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

And Fill advice form 14s 650ms

And Click advice save button to check error message 098ms

Then Check if possible advice alert is displayed 016ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 39s 519ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

And Expand advice panel 107ms

And Edit advice in transport details 14s 109ms

And Fill arrival date field 2s 301ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

And Go to "TRANSPORT_TABLE" 214ms

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

And Expand advice panel 107ms

And Edit advice in transport details 13s 990ms

And Fill arrival date field 2s 287ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 237ms

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

And Expand advice panel 111ms

And Edit advice in transport details 14s 005ms

And Fill arrival date field 2s 296ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

When Go to "WAREHOUSE_TAB" 826ms

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

And Select view "DAYS_2" 2s 071ms

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

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

And Select view "DAYS_2" 2s 047ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 150ms

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

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

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

When Go to "WAREHOUSE_TAB" 858ms

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

And Select view "DAYS_2" 2s 081ms

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

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

And Select view "DAYS_2" 2s 054ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 204ms

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

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

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

When Go to "WAREHOUSE_TAB" 736ms

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

And Select view "DAYS_2" 2s 095ms

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

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

And Select view "DAYS_2" 2s 051ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 177ms

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

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

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

When Go to "WAREHOUSE_TAB" 444ms

And Select warehouse "MGW" 1s 154ms

And Select view "DAYS_2" 2s 074ms

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

And Select warehouse "HRL" 1s 397ms

And Select view "DAYS_2" 2s 055ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 171ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

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

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

Then Check if transport has "departed" 029ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

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

And Set advice window in schedule 2s 780ms

And Fill advice form 14s 630ms

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

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

And Go to "TRANSPORT_TABLE" 196ms

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

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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

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

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

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

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

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

And Set advice window in schedule 2s 755ms

And Fill advice form 14s 518ms

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

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

And Go to "TRANSPORT_TABLE" 230ms

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

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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

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

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

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

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

And Confirm statuses until reach "arrived" 3s 819ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.rollbackAddedActionAuthorities() 061ms

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

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

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

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

And Confirm statuses until reach "arrived" 3s 832ms

And Check if transport row is "green" 3s 070ms

And Confirm statuses until reach "during-unload" 3s 749ms

Then Check if transport row is "orange" 3s 083ms

And Confirm statuses until reach "unloaded" 3s 779ms

Then Check if transport row is "darkgoldenrod" 3s 060ms

And Confirm statuses until reach "process-ended" 4s 255ms

Then Check if transport row is "silver" 3s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

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

And Show all transport types 1s 071ms

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

And Set advice window in schedule 2s 610ms

And Fill advice form 8s 315ms

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

And Go to "TRANSPORT_TABLE" 247ms

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

And Confirm statuses until reach "left-the-area" 17s 418ms

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

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 588ms

And Fill advice form 8s 319ms

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

And Go to "TRANSPORT_TABLE" 201ms

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

And Confirm statuses until reach "left-the-area" 17s 476ms

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

And Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 582ms

And Fill advice form 8s 304ms

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

And Go to "TRANSPORT_TABLE" 213ms

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

When Add file to transport by API 717ms

And Confirm statuses until reach "process-ended" 35s 216ms

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 602ms

And Fill advice form 8s 344ms

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

And Go to "TRANSPORT_TABLE" 215ms

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

When Add file to transport by API 290ms

And Confirm statuses until reach "process-ended" 35s 170ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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

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

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

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

And Login as "swiss-krono-delivery-guard" 1s 223ms

And Go to "TRANSPORT_TABLE" 184ms

When Confirm "Departure" status in transport row 3s 096ms

Then Verify that "Departure" has been confirmed 036ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 447ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 806ms

And Login as "bausch-admin" 1s 152ms

And Go to "TRANSPORT_TABLE" 223ms

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

When Confirm statuses until reach "on-the-way" 9s 816ms

And Open statuses popup 058ms

And Toggle status date confirmation checkbox 279ms

And Confirm statuses until reach "process-ended" 18s 754ms

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

After Hooks.deleteModeOfTransportationAfterTest() 101ms

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 306ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 275ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 768ms

And Login as "bausch-admin" 1s 111ms

And Go to "TRANSPORT_TABLE" 204ms

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

When Confirm statuses until reach "on-the-way" 9s 276ms

And Open statuses popup 065ms

And Toggle status date confirmation checkbox 277ms

And Change status execution date to "1" days from today 2s 228ms

Then Verify that status cannot be confirmed 1s 084ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.deleteModeOfTransportationAfterTest() 078ms

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 294ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 255ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 759ms

And Login as "bausch-admin" 1s 107ms

And Go to "TRANSPORT_TABLE" 195ms

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

When Confirm statuses until reach "on-the-way" 9s 910ms

And Open statuses popup 065ms

And Toggle status date confirmation checkbox 274ms

And Change status execution date to "-1" days from today 2s 199ms

Then Verify that status cannot be confirmed 1s 088ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

After Hooks.deleteModeOfTransportationAfterTest() 095ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 781ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 032ms

When Login as "farmacol-admin" 1s 626ms

And Go to "TRANSPORT_TABLE" 183ms

And Confirm statuses until reach "during-unload" 9s 901ms

And Set actual confirmed transport status list 1s 357ms

And Disable task by API 049ms

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

And Edit transport hours and recalculate statuses 16s 324ms

Then Verify that all confirmed statuses are still on transport status list 190ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

After Hooks.rollbackTaskChanges() 044ms

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

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 340ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 753ms

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

And Check if reject date is not visible 15s 049ms

When Reject status: Book of disinfection 085ms

And Check if reject date is visible 313ms

Then If user is login then logout 092ms

And Login as "lantmannen-admin" 1s 062ms

And Check if note was added to transport after status rejection 1s 292ms

And Check if history note was added to transport after status rejection - "LOAD" 5s 485ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 9s 409ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.cleanUserDetailsAfterTest() 166ms

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

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 312ms

And Check if reject date is not visible 15s 022ms

When Reject status: Book of disinfection 077ms

And Check if reject date is visible 146ms

And Get rejection date 024ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 066ms

Then Check if reject date has changed 1s 080ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 113ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 327ms

And Go to transport details "LOAD" 4s 302ms

And Check if reject date is not visible 15s 025ms

When Reject status: Book of disinfection 076ms

Then Check if reject date is visible 136ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 019ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 314ms

And Open statuses popup 106ms

And Check if reject date is not visible 15s 022ms

When Reject status: Book of disinfection 081ms

Then Open statuses popup 048ms

And Check if reject date is visible 10s 109ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

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 437ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 458ms

And Confirm to the last status by API 238ms

When Find statuses for transport in table 2s 020ms

And Revoke statuses until reach "advice-added" 6s 809ms

Then Check if transport has "advice-added" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 088ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 339ms

And Confirm to the last status by API 237ms

When Find statuses for transport in table 1s 664ms

And Revoke statuses until reach "planned" 6s 664ms

Then Check if transport has "planned" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 059ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 190ms

When Find transport in table with status "new" 3s 183ms

And Open statuses popup 089ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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 049ms

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 002ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 205ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 131ms

And Set advice window in schedule 2s 740ms

And Fill advice form 12s 010ms

And Click advice save button and wait for advice form to disappear 30s 703ms

And Go to "TRANSPORT_TABLE" 247ms

When Find transport in table with status "advice-added" 3s 206ms

And Open statuses popup 092ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 062ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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" 104ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 186ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 654ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 028ms

When Login as "farmacol-admin" 1s 040ms

And Go to "TRANSPORT_TABLE" 208ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 6s 563ms

And Disable task by API 050ms

And Find transport pencil button in transports table 1s 234ms

And Click pencil and move transport to next day in schedule 18s 252ms

And Go to "TRANSPORT_TABLE" 200ms

Then Verify that "START_OF_UNLOADING" is not visible 119ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.rollbackTaskChanges() 043ms

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 474ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 454ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 277ms

When Go to "WAREHOUSE_TAB" 782ms

And Select warehouse "Serownia" 1s 382ms

And Set week view 1s 122ms

And Show yesterday 1s 053ms

And Move window into the past 292ms

Then Check if window is "red" 2s 024ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

After Hooks.rollbackAddedAuthorities() 037ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 007ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 389ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 055ms

When Go to "WAREHOUSE_TAB" 616ms

And Select warehouse "Magazyn - Nowa Sól" 2s 178ms

And Set week view 1s 111ms

And Show yesterday 1s 058ms

And Move window into the past 412ms

Then Check if window is "red" 2s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

After Hooks.rollbackAddedAuthorities() 031ms

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 099ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 194ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 045ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 003ms

When Show all transport types 1s 043ms

And Click button advice in transport table "DELIVERY" 087ms

And Set advice window in schedule 2s 619ms

And Fill advice form 8s 268ms

And Click advice save button and wait for advice form to disappear 30s 716ms

And Select warehouse "Magazyn Hala A" 1s 186ms

And Set week view 2s 037ms

And Show yesterday 1s 193ms

And Move window into the past 530ms

Then Check if window is "red" 2s 073ms

Hooks

After Hooks.deleteTransportAfterTest() 161ms

After Hooks.rollbackAddedAuthorities() 031ms

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 455ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 442ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 436ms

When Go to "WAREHOUSE_TAB" 752ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 698ms

And Set week view 1s 119ms

And Check if time window length is correct after "CREATE" 026ms

And Change number of pallets in transport 51s 082ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 143ms

And Check if time window length is correct after "EDIT" 029ms

Hooks

After Hooks.deleteTransportAfterTest() 165ms

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 167ms

And Get "UNLOAD" settings from "keeeper" 028ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 131ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 147ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 315ms

When Go to "WAREHOUSE_TAB" 320ms

And Select warehouse "Magazyn Surowców" 1s 187ms

And Set week view 1s 105ms

Then Check if time window has proper "60" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackTransportTypeSettings() 064ms

After Hooks.clearAlgorithmSettings() 151ms

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 084ms

And Get "UNLOAD" settings from "keeeper" 027ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 101ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 053ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 311ms

When Go to "WAREHOUSE_TAB" 305ms

And Select warehouse "Magazyn Surowców" 1s 169ms

And Set week view 1s 094ms

Then Check if time window has proper "60" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.rollbackTransportTypeSettings() 059ms

After Hooks.clearAlgorithmSettings() 114ms

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 123ms

And Get "LOAD" settings from "keeeper" 052ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 111ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 066ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 243ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 003ms

And Show all transport types 1s 046ms

And Click button advice in transport table "LOAD" 100ms

And Set advice window in schedule 2s 464ms

And Fill advice form 13s 188ms

And Click advice save button and wait for advice form to disappear 30s 675ms

Then Check if time window has proper "30" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.rollbackTransportTypeSettings() 087ms

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 114ms

And Get "CONTAINER" settings from "keeeper" 037ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 096ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "20;false" 059ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 194ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 003ms

And Show all transport types 1s 045ms

And Click button advice in transport table "CONTAINER" 104ms

And Set advice window in schedule 2s 475ms

And Fill advice form 13s 139ms

And Click advice save button and wait for advice form to disappear 30s 727ms

Then Check if time window has proper "60" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

After Hooks.rollbackTransportTypeSettings() 058ms

After Hooks.clearAlgorithmSettings() 104ms

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" 108ms

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" 115ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 303ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 1s 272ms

When Go to transport details "DELIVERY" 32s 682ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 350ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 168ms

And Go to "WAREHOUSE_TAB" 786ms

And Select warehouse "Serownia" 1s 400ms

And Set week view 1s 088ms

Then Check if time window has proper "60" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.clearAlgorithmSettings() 172ms

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 161ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 044ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 232ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 541ms

And Check if time window counter value equals "1" 075ms

And Select view "DAYS_2" 2s 080ms

And Move advice window "2" 1s 329ms

And Select view "DAY" 2s 076ms

Then Check if time window counter value equals "0" 063ms

And Delete created transport by API 155ms

And Check if time window counter value equals "0" 044ms

And Click in free spot in schedule page to create gray window 184ms

And Check if time window counter value equals "0" 048ms

And Click in free spot in schedule page to create dedicated window 055ms

And Check if time window counter value equals "0" 043ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 117ms

When Go to new transport "DELIVERY" 293ms

And Fill transport form 11s 376ms

And Click "save-transport" save button and wait for form to disappear 15s 621ms

And Set advice window in schedule 2s 159ms

And Check is transport created in schedule and set transport id 567ms

And Go to "TRANSPORT_TABLE" 254ms

When Click on time window date 1s 316ms

And Open transport form when in schedule 1s 167ms

Then Check are transport values equals 118ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 665ms

When Go to new transport "DELIVERY" 387ms

And Fill transport form 38s 830ms

And Click "save-transport" save button and wait for form to disappear 15s 623ms

And Set advice window in schedule 2s 163ms

And Check is transport created in schedule and set transport id 670ms

And Go to "TRANSPORT_TABLE" 277ms

When Click on time window date 1s 253ms

And Open transport form when in schedule 1s 263ms

Then Check are transport values equals 19s 422ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 504ms

When Go to new transport "CISTERN_DELIVERY" 390ms

And Fill transport form 34s 844ms

And Click "save-transport" save button and wait for form to disappear 15s 955ms

And Set advice window in schedule 2s 212ms

And Check is transport created in schedule and set transport id 602ms

And Go to "TRANSPORT_TABLE" 201ms

When Click on time window date 1s 395ms

And Open transport form when in schedule 1s 172ms

Then Check are transport values equals 21s 386ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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 513ms

When Go to new transport "CISTERN_COLLECTION" 352ms

And Fill transport form 28s 341ms

And Click "save-transport" save button and wait for form to disappear 15s 875ms

And Set advice window in schedule 2s 200ms

And Check is transport created in schedule and set transport id 546ms

And Go to "TRANSPORT_TABLE" 177ms

When Click on time window date 1s 402ms

And Open transport form when in schedule 1s 188ms

Then Check are transport values equals 21s 346ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 378ms

When Go to new transport "DELIVERY" 303ms

And Fill transport form 37s 950ms

And Click "save-transport" save button and wait for form to disappear 15s 612ms

And Set advice window in schedule 2s 171ms

And Check is transport created in schedule and set transport id 607ms

And Go to "TRANSPORT_TABLE" 203ms

When Click on time window date 1s 371ms

And Open transport form when in schedule 1s 173ms

Then Check are transport values equals 19s 312ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 657ms

When Go to new transport "LOAD" 305ms

And Fill transport form 37s 914ms

And Click "save-transport" save button and wait for form to disappear 15s 688ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 544ms

And Go to "TRANSPORT_TABLE" 252ms

When Click on time window date 1s 315ms

And Open transport form when in schedule 1s 136ms

Then Check are transport values equals 19s 338ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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" 100ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 076ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 071ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 076ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 173ms

And Login as "farmacol-admin" 1s 510ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 693ms

And Go to "TRANSPORT_TABLE" 313ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 422ms

And Add step "unload" 138ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 442ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 352ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 355ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 317ms

Then Click "save-transport" save button 178ms

And Set advice window in schedule in "2" days 4s 951ms

And Click advice save button and wait for advice form to disappear 30s 954ms

And Go to "TRANSPORT_TABLE" 249ms

And Check if transport has "2" time windows 013ms

Hooks

After Hooks.deleteTransportAfterTest() 157ms

After Hooks.rollbackTransportTypeSettings() 061ms

After Hooks.rollbackAddedActionAuthorities() 056ms

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" 108ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 033ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 050ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 191ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 660ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 876ms

And Go to "TRANSPORT_TABLE" 330ms

And Get checkpoint colors for transport 005ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 42s 563ms

Hooks

After Hooks.deleteTransportAfterTest() 154ms

After Hooks.rollbackTransportTypeSettings() 092ms

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" 104ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 034ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 060ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 250ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 046ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 786ms

And Go to "TRANSPORT_TABLE" 338ms

And Get checkpoint colors for transport 005ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 42s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 193ms

After Hooks.rollbackTransportTypeSettings() 068ms

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" 111ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 039ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 061ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 246ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 058ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 305ms

And Get checkpoint colors for transport 006ms

And Go to "TRANSPORT_TABLE" 304ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 5s 153ms

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() 125ms

After Hooks.rollbackTransportTypeSettings() 124ms

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" 111ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 041ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 100ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 209ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 079ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 006ms

And Get checkpoint colors for transport 004ms

And Go to "TRANSPORT_TABLE" 300ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 31s 362ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

After Hooks.rollbackTransportTypeSettings() 071ms

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" 109ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 237ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 674ms

And Login as "super-admin-farmacol" 1s 925ms

And Show all transport types 1s 154ms

And Click on time window date 1s 625ms

Then Open transport form when in schedule 1s 257ms

And Click create similar button 15s 115ms

And Click cancel button in transport form 106ms

And Open transport form when in schedule 1s 200ms

Then Check if transport form modal is visible 049ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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 069ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 002ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 040ms

And Set proper delay time to move order to archive after task timeout 054ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 361ms

And Go to "WAREHOUSE_TAB" 635ms

And Change warehouse in schedule to: "Katowice" 1s 070ms

And Wait "60" seconds 1m

And Verify that transport window is grey 034ms

And Verify that transport is in archive 1s 140ms

Then Restore transport from archive 1s 099ms

And Verify that transport has been successfully restored 15s 273ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.rollbackSettings() 028ms

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 131ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 209ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 034ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 005ms

When Go to "TRANSPORT_TABLE" 125ms

And Click button advice in transport table "OWN_COLLECTION" 2s 012ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 239ms

And Go to "TRANSPORT_TABLE" 197ms

And Find transport in table with status "planned-magazyn-tychy" 3s 235ms

And Confirm statuses until reach "process-ended" 24s 224ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 239ms

And Show "OWN_COLLECTION" 074ms

And Verify that created transport is "true" in transport table 15s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.rollbackSettings() 035ms

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 037ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 271ms

When Fill auction form 15s 456ms

Then Verify that the auction has been added to transport 055ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 270ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 235ms

When Fill auction form 15s 438ms

Then Verify that the auction has been added to transport 039ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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 051ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 230ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 121ms

When If user is login then logout 125ms

And Login as "paa1-carrier@qa.qa-test" 1s 780ms

And Go to auction offer 1s 231ms

And Accept transport with minimum rate 15s 632ms

Then Check if carrier is assigned to transport 020ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 011ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 199ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 116ms

When If user is login then logout 096ms

And Login as "paa1-carrier@qa.qa-test" 1s 328ms

And Go to auction offer 1s 225ms

And Reject auction offer 15s 613ms

Then Verify that offer has been removed from transport 15s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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 234ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 249ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 114ms

When If user is login then logout 105ms

And Login as "pskza1-carrier@qa.qa-test" 1s 156ms

And Go to auction offer 1s 241ms

And Reject auction offer 15s 601ms

Then Verify that offer has been removed from transport 15s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 171ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 261ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 115ms

When If user is login then logout 102ms

And Login as "paa1-carrier@qa.qa-test" 1s 704ms

And Go to auction offer 1s 242ms

And Offer prize above maximum - "20000" 138ms

Then Verify that is not possible to add offer 143ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 145ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 232ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 109ms

When If user is login then logout 101ms

And Login as "pskza1-carrier@qa.qa-test" 1s 098ms

And Go to auction offer 1s 219ms

And Offer prize above maximum - "20000" 130ms

Then Verify that is not possible to add offer 149ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 235ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 191ms

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 020ms

Then Verify that is possible to add auction 041ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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 217ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 289ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 124ms

And Wait till auction end 1m 58s 019ms

Then Verify that is possible to add auction 051ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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 483ms

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 126ms

And Go to auction offer 1s 216ms

When Offer "1000" 144ms

Then Verify that offer with "1000" has been added to auction 3s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 339ms

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 179ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 282ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 119ms

And Go to auction offer 1s 197ms

When Offer "1000" 125ms

Then Verify that offer with "1000" has been added to auction 3s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 105ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 263ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 118ms

And Go to auction offer 1s 177ms

When Offer "1000" 107ms

And Verify that offer with "1000" has been added to auction 3s 033ms

Then Go to auction offer 1s 180ms

And Revoke current offer 581ms

And Verify that offer has been revoked 30s 635ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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 260ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 251ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 122ms

And Go to auction offer 1s 199ms

When Offer "1000" 134ms

And Verify that offer with "1000" has been added to auction 3s 039ms

Then Go to auction offer 1s 161ms

And Offer "1500" 111ms

And Verify that offer with "1500" has been added to auction 3s 024ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 061ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 265ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 119ms

And Go to auction offer 1s 182ms

When Offer "1000" 126ms

And Verify that offer with "1000" has been added to auction 3s 033ms

Then Login as "swisskrono-admin" 1s 052ms

And Go to auction details 1s 175ms

And Finish active auction 041ms

And Verify that the transport has no active auction 137ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 249ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 210ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 104ms

And Go to auction offer 1s 194ms

When Offer "1000" 147ms

Then Verify that carrier can see current place in auction depending on the "true" role 138ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 100ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 276ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 111ms

And Go to auction offer 1s 190ms

When Offer "1000" 131ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 192ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 239ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 103ms

And Go to auction offer 1s 211ms

When Offer "300" 124ms

And Verify that carrier can't add offer to auction 027ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 027ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 188ms

And Show all transport "false" 012ms

When Go to auction form 1s 238ms

Then Verify carrier selection value "false" 033ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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" 980ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 234ms

And Show all transport "true" 084ms

When Go to auction form 1s 188ms

Then Verify carrier selection value "true" 033ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 009ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 218ms

When Open transport auction form 179ms

And Select all companies checkbox in transport auction form 072ms

And Unselect company "PAA2" in transport auction form 072ms

And Put transport on auction 15s 191ms

And Open transport auction history 095ms

And Open participants section in transport auction history 060ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 259ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 200ms

When Open transport auction form 199ms

And Select all companies checkbox in transport auction form 064ms

And Unselect company "PSKZA2" in transport auction form 068ms

And Put transport on auction 15s 202ms

And Open transport auction history 079ms

And Open participants section in transport auction history 046ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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" 003ms

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 069ms

When Go to new transport "UNLOAD" 15s 271ms

And Fill transport form 16s 180ms

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.gNZW5P}, 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: 55fa49cc20e69a7dd1e102d5368875c9
*** 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" 003ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 165ms

When Go to new transport "DELIVERY" 287ms

And Fill transport form 11s 389ms

And Click "save-transport" save button and wait for form to disappear 15s 622ms

And Set advice window in schedule 2s 173ms

And Check is transport created in schedule and set transport id 662ms

And Go to "TRANSPORT_TABLE" 265ms

And Go to transport details "DELIVERY" 4s 313ms

Then Check are transport values equals 112ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 135ms

When Go to new transport "OWN_COLLECTION" 291ms

And Fill transport form 17s 980ms

And Click "save-transport" save button and wait for form to disappear 15s 631ms

And Set advice window in schedule 2s 179ms

And Check is transport created in schedule and set transport id 419ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "OWN_COLLECTION" 4s 321ms

Then Check are transport values equals 171ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 456ms

When Go to new transport "DELIVERY" 346ms

And Fill transport form 38s 710ms

And Click "save-transport" save button and wait for form to disappear 15s 620ms

And Set advice window in schedule 2s 187ms

And Check is transport created in schedule and set transport id 757ms

And Go to "TRANSPORT_TABLE" 258ms

And Go to transport details "DELIVERY" 4s 663ms

Then Check are transport values equals 19s 388ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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 467ms

When Go to new transport "CISTERN_DELIVERY" 342ms

And Fill transport form 34s 884ms

And Click "save-transport" save button and wait for form to disappear 15s 928ms

And Set advice window in schedule 2s 212ms

And Check is transport created in schedule and set transport id 582ms

And Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "CISTERN_DELIVERY" 4s 362ms

Then Check are transport values equals 21s 382ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 439ms

When Go to new transport "CISTERN_COLLECTION" 354ms

And Fill transport form 28s 271ms

And Click "save-transport" save button and wait for form to disappear 15s 912ms

And Set advice window in schedule 2s 232ms

And Check is transport created in schedule and set transport id 610ms

And Go to "TRANSPORT_TABLE" 205ms

And Go to transport details "CISTERN_COLLECTION" 4s 392ms

Then Check are transport values equals 21s 373ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

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 508ms

When Go to new transport "OWN_COLLECTION" 363ms

And Fill transport form 32s 764ms

And Click "save-transport" save button and wait for form to disappear 15s 684ms

And Set advice window in schedule 2s 155ms

And Check is transport created in schedule and set transport id 738ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "OWN_COLLECTION" 4s 498ms

Then Check are transport values equals 19s 350ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 463ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 359ms

And Fill transport form 32s 797ms

And Click "save-transport" save button and wait for form to disappear 15s 660ms

And Set advice window in schedule 2s 173ms

And Check is transport created in schedule and set transport id 593ms

And Go to "TRANSPORT_TABLE" 194ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 450ms

Then Check are transport values equals 4s 316ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

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 443ms

When Go to new transport "EXPORT" 418ms

And Fill transport form 40s 698ms

And Click "save-transport" save button and wait for form to disappear 15s 579ms

And Set advice window in schedule 2s 160ms

And Check is transport created in schedule and set transport id 610ms

And Go to "TRANSPORT_TABLE" 209ms

And Go to transport details "EXPORT" 5s 117ms

Then Check are transport values equals 4s 390ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-skd" 001ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 336ms

When Go to new transport "DELIVERY" 15s 227ms

And Fill transport form 28s 339ms

And Click "save-transport" save button and wait for form to disappear 15s 626ms

And Set advice window in schedule 2s 161ms

And Check is transport created in schedule and set transport id 766ms

And Go to "TRANSPORT_TABLE" 237ms

And Go to transport details "DELIVERY" 32s 247ms

Then Check are transport values equals 36s 337ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 003ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 171ms

When Go to new transport "DELIVERY" 279ms

And Fill transport form 37s 965ms

And Click "save-transport" save button and wait for form to disappear 15s 639ms

And Set advice window in schedule 2s 166ms

And Check is transport created in schedule and set transport id 595ms

And Go to "TRANSPORT_TABLE" 199ms

And Go to transport details "DELIVERY" 4s 300ms

Then Check are transport values equals 19s 300ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 130ms

When Go to new transport "LOAD" 293ms

And Fill transport form 37s 922ms

And Click "save-transport" save button and wait for form to disappear 15s 677ms

And Set advice window in schedule 2s 171ms

And Check is transport created in schedule and set transport id 545ms

And Go to "TRANSPORT_TABLE" 238ms

And Go to transport details "LOAD" 4s 301ms

Then Check are transport values equals 19s 299ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 125ms

When Go to new transport "UNLOAD" 289ms

And Fill transport form 37s 567ms

And Click "save-transport" save button and wait for form to disappear 15s 588ms

And Set advice window in schedule 2s 148ms

And Check is transport created in schedule and set transport id 593ms

And Go to "TRANSPORT_TABLE" 207ms

And Go to transport details "UNLOAD" 4s 363ms

Then Check are transport values equals 21s 445ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

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 159ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 312ms

And Fill transport form 37s 507ms

And Click "save-transport" save button and wait for form to disappear 15s 612ms

And Set advice window in schedule 2s 145ms

And Check is transport created in schedule and set transport id 532ms

And Go to "TRANSPORT_TABLE" 178ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 361ms

Then Check are transport values equals 21s 437ms

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_DELIVERY" "super-admin-alrec" 003ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 237ms

When Go to new transport "DELIVERY" 285ms

And Fill transport form 22s 827ms

And Click "save-transport" save button and wait for form to disappear 15s 595ms

And Set advice window in schedule 2s 145ms

And Check is transport created in schedule and set transport id 763ms

And Go to "TRANSPORT_TABLE" 199ms

And Go to transport details "DELIVERY" 4s 329ms

Then Check are transport values equals 17s 259ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_WEIGHING" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 512ms

When Go to new transport "WEIGHING" 283ms

And Fill transport form 13s 505ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 627ms

And Show all transport "false" 014ms

And Go to "TRANSPORT_TABLE" 159ms

And Go to transport details "WEIGHING" 4s 394ms

And Check are transport values equals 2s 174ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 189ms

When Go to new transport "TRANSPORT" 358ms

And Fill transport form 26s 785ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 635ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "TRANSPORT" 4s 421ms

And Check are transport values equals 6s 231ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 146ms

When Go to new transport "CONTAINER" 323ms

And Fill transport form 11s 148ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 633ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 125ms

And Go to transport details "CONTAINER" 4s 351ms

And Check are transport values equals 077ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 461ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 311ms

And Fill transport form 12s 916ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 622ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 105ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 575ms

And Check are transport values equals 4s 189ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-piast" 002ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 653ms

When Go to new transport "DELIVERY" 314ms

And Fill transport form 22s 512ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 614ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 142ms

And Go to transport details "DELIVERY" 4s 587ms

And Check are transport values equals 17s 177ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-piast" 002ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 224ms

When Go to new transport "LOAD" 375ms

And Fill transport form 26s 360ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 623ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 134ms

And Go to transport details "LOAD" 4s 618ms

And Check are transport values equals 2s 132ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 145ms

When Go to new transport "LOAD" 290ms

And Fill transport form 24s 629ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 569ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 140ms

And Go to transport details "LOAD" 4s 376ms

And Check are transport values equals 19s 227ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 157ms

When Go to new transport "CONTAINER" 281ms

And Fill transport form 24s 631ms

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" 139ms

And Go to transport details "CONTAINER" 4s 401ms

And Check are transport values equals 19s 236ms

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_SMALLS_IMPORT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 264ms

When Go to new transport "SMALLS_IMPORT" 386ms

And Fill transport form 36s 396ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 664ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "SMALLS_IMPORT" 4s 439ms

And Check are transport values equals 10s 402ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 211ms

When Go to new transport "SMALLS_EXPORT" 396ms

And Fill transport form 36s 323ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 598ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "SMALLS_EXPORT" 4s 419ms

And Check are transport values equals 10s 374ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 136ms

When Go to new transport "TRANSPORT_ORDER" 385ms

And Fill transport form 30s 041ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 639ms

And Show all transport "true" 090ms

And Go to "TRANSPORT_TABLE" 137ms

And Go to transport details "TRANSPORT_ORDER" 4s 402ms

And Check are transport values equals 19s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 179ms

When Go to new transport "TRANSPORT" 367ms

And Fill transport form 37s 637ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 619ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 146ms

And Go to transport details "TRANSPORT" 4s 431ms

And Check are transport values equals 4s 229ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_INBOUND_WITHOUT_WAREHOUSES" "super-admin-alrec" 003ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 162ms

When Go to new transport "INBOUND" 375ms

And Fill transport form 41s 047ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 658ms

And Show all transport "true" 078ms

And Go to "TRANSPORT_TABLE" 147ms

And Go to transport details "INBOUND" 4s 440ms

And Check are transport values equals 2s 306ms

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_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 003ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 310ms

When Go to new transport "EXTERNAL_DELIVERY" 339ms

And Fill transport form 53s 645ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 586ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 446ms

And Check are transport values equals 4s 471ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "dfa1-supplier" 003ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 1s 932ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 275ms

And Fill transport form 47s 282ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 658ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 170ms

And Go to transport details "EXTERNAL_DELIVERY" 32s 375ms

And Check are transport values equals 4s 485ms

Hooks

After Hooks.deleteTransportAfterTest() 017ms

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:175)
	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 060ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 645ms

And Show all transport "false" 008ms

When Go to transport details "UNLOAD" 32s 529ms

And Fill transport form 30s 354ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 155ms

And Go to transport details "UNLOAD" 32s 383ms

Then Check are transport values equals 4s 264ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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 135ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 240ms

And Show all transport "false" 013ms

When Go to transport details "TRANSPORT" 4s 463ms

And Fill transport form 10s 259ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 642ms

And Go to transport details "TRANSPORT" 4s 439ms

Then Check are transport values equals 4s 136ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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 162ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 002ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 201ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 356ms

And Fill transport form 4s 715ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 646ms

And Go to transport details "CONTAINER" 4s 378ms

Then Check are transport values equals 043ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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 030ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 296ms

And Show all transport "false" 012ms

When Go to transport details "DELIVERY" 4s 382ms

And Fill transport form 11s 615ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 623ms

And Go to transport details "DELIVERY" 4s 335ms

Then Check are transport values equals 149ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 113ms

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 309ms

And Show all transport "false" 005ms

When Go to transport details "OWN_COLLECTION" 4s 338ms

And Fill transport form 21s 487ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 645ms

And Go to transport details "OWN_COLLECTION" 4s 341ms

Then Check are transport values equals 2s 185ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 482ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 494ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 794ms

And Fill transport form 35s 877ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 118ms

And Go to transport details "DELIVERY" 4s 486ms

Then Check are transport values equals 10s 540ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 506ms

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 344ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION" 4s 693ms

And Fill transport form 36s 536ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 151ms

And Go to transport details "OWN_COLLECTION" 4s 437ms

Then Check are transport values equals 6s 356ms

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 495ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 466ms

And Show all transport "false" 010ms

When Go to transport details "EXPORT" 5s 635ms

And Fill transport form 47s 853ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 138ms

And Go to transport details "EXPORT" 4s 465ms

Then Check are transport values equals 8s 472ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 501ms

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 174ms

And Show all transport "false" 011ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 826ms

And Fill transport form 36s 058ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 670ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 456ms

Then Check are transport values equals 12s 465ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 464ms

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 281ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 496ms

And Fill transport form 27s 181ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 621ms

And Go to transport details "CISTERN_DELIVERY" 4s 391ms

Then Check are transport values equals 6s 307ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 472ms

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 328ms

And Show all transport "false" 011ms

When Go to transport details "CISTERN_COLLECTION" 4s 464ms

And Fill transport form 25s 798ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 616ms

And Go to transport details "CISTERN_COLLECTION" 4s 359ms

Then Check are transport values equals 6s 275ms

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 487ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 214ms

And Show all transport "false" 010ms

When Go to transport details "WEIGHING" 4s 378ms

And Fill transport form 12s 310ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 617ms

And Go to transport details "WEIGHING" 4s 337ms

Then Check are transport values equals 2s 146ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 626ms

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 416ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 525ms

And Fill transport form 35s 114ms

And Click "save-transport-and-close" save button and wait for form to disappear 693ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 406ms

Then Check are transport values equals 6s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 130ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 289ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 32s 334ms

And Fill transport form 25s 593ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 605ms

And Go to transport details "DELIVERY" 32s 327ms

Then Check are transport values equals 2s 205ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 212ms

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 190ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 726ms

And Fill transport form 57s 241ms

And Click "save-transport-and-close" save button and wait for form to disappear 700ms

And Go to transport details "LOAD" 4s 441ms

Then Check are transport values equals 24s 806ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 098ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 331ms

And Show all transport "false" 006ms

When Go to transport details "DELIVERY" 4s 364ms

And Fill transport form 16s 445ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 628ms

And Go to transport details "DELIVERY" 4s 308ms

Then Check are transport values equals 074ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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 108ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 002ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 309ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 313ms

And Fill transport form 28s 191ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 152ms

And Go to transport details "LOAD" 4s 279ms

Then Check are transport values equals 2s 231ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 144ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 364ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 4s 418ms

And Fill transport form 37s 821ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 135ms

And Go to transport details "UNLOAD" 4s 367ms

Then Check are transport values equals 6s 363ms

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 160ms

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 321ms

And Show all transport "false" 012ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 413ms

And Fill transport form 36s 178ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 629ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 352ms

Then Check are transport values equals 6s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 122ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 002ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 223ms

And Show all transport "false" 012ms

When Go to transport details "LOAD" 4s 384ms

And Fill transport form 24s 732ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 649ms

And Go to transport details "LOAD" 4s 354ms

Then Check are transport values equals 4s 204ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 165ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 247ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 345ms

And Fill transport form 24s 697ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 632ms

And Go to transport details "CONTAINER" 4s 338ms

Then Check are transport values equals 4s 196ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 280ms

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 232ms

And Show all transport "false" 011ms

When Go to transport details "SMALLS_EXPORT" 4s 528ms

And Fill transport form 32s 920ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 637ms

And Go to transport details "SMALLS_EXPORT" 4s 420ms

Then Check are transport values equals 8s 319ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 282ms

And Show all transport "true" 074ms

When Go to transport details "DELIVERY" 4s 334ms

And Fill transport form 19s 518ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Go to transport details "DELIVERY" 4s 322ms

Then Check are transport values equals 204ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 148ms

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 307ms

And Show all transport "true" 076ms

When Go to transport details "TRANSPORT_ORDER" 4s 464ms

And Fill transport form 26s 685ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 621ms

And Go to transport details "TRANSPORT_ORDER" 4s 388ms

Then Check are transport values equals 2s 236ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-warehouseman" and set token of apiUsername "super-admin-keeeper" 1s 950ms

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 163ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 383ms

And Fill transport form 8s 892ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 615ms

And Go to transport details "CONTAINER" 4s 378ms

Then Check are transport values equals 4s 120ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 409ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 394ms

And Show all transport "false" 014ms

When Delete transport 17s 969ms

Then Transport not displayed in table of transports 15s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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 221ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 170ms

And Show all transport "false" 010ms

When Delete transport 17s 164ms

Then Transport not displayed in table of transports 15s 012ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 092ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 332ms

And Show all transport "false" 011ms

When Delete transport 17s 502ms

Then Transport not displayed in table of transports 15s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 206ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 196ms

And Show all transport "false" 010ms

When Delete transport 16s 997ms

Then Transport not displayed in table of transports 15s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 288ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 228ms

And Show all transport "false" 010ms

When Delete transport 17s 668ms

Then Transport not displayed in table of transports 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 289ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 262ms

And Show all transport "false" 010ms

When Delete transport 17s 697ms

Then Transport not displayed in table of transports 15s 057ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 205ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 323ms

And Show all transport "true" 089ms

When Delete transport 19s 079ms

Then Transport not displayed in table of transports 15s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 189ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 243ms

And Show all transport "true" 084ms

When Delete transport 17s 140ms

Then Transport not displayed in table of transports 15s 055ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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 069ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 602ms

And Show all transport "false" 008ms

When Go to transport details "UNLOAD" 32s 454ms

And Fill transport form 30s 325ms

And Click "save-transport" save button 1s 244ms

And Click cancel button in transport form 086ms

And Go to transport details "UNLOAD" 32s 350ms

Then Check are transport values equals 4s 292ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 161ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 234ms

And Show all transport "false" 007ms

When Go to transport details "TRANSPORT" 4s 488ms

And Fill transport form 10s 334ms

And Click "save-transport" save button 724ms

And Click cancel button in transport form 071ms

And Go to transport details "TRANSPORT" 4s 308ms

Then Check are transport values equals 4s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 124ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 179ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 370ms

And Fill transport form 4s 714ms

And Click "save-transport" save button 705ms

And Click cancel button in transport form 067ms

And Go to transport details "CONTAINER" 4s 257ms

Then Check are transport values equals 035ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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 043ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 300ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 366ms

And Fill transport form 11s 542ms

And Click "save-transport" save button 724ms

And Click cancel button in transport form 067ms

And Go to transport details "DELIVERY" 4s 250ms

Then Check are transport values equals 110ms

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 "adama-admin" and set token of apiUsername "super-admin-adama" 1s 147ms

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 301ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION" 4s 340ms

And Fill transport form 21s 625ms

And Click "save-transport" save button 702ms

And Click cancel button in transport form 086ms

And Go to transport details "OWN_COLLECTION" 4s 313ms

Then Check are transport values equals 2s 216ms

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 489ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 438ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 785ms

And Fill transport form 35s 861ms

And Click "save-transport" save button 1s 233ms

And Click cancel button in transport form 084ms

And Go to transport details "DELIVERY" 4s 362ms

Then Check are transport values equals 10s 511ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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 536ms

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 349ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 673ms

And Fill transport form 36s 566ms

And Click "save-transport" save button 1s 240ms

And Click cancel button in transport form 211ms

And Go to transport details "OWN_COLLECTION" 4s 341ms

Then Check are transport values equals 6s 391ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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 537ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 002ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 398ms

And Show all transport "false" 009ms

When Go to transport details "EXPORT" 5s 699ms

And Fill transport form 48s 009ms

And Click "save-transport" save button 863ms

And Click cancel button in transport form 080ms

And Go to transport details "EXPORT" 4s 429ms

Then Check are transport values equals 8s 464ms

Hooks

After Hooks.deleteTransportAfterTest() 159ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 478ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 171ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 714ms

And Fill transport form 36s 070ms

And Click "save-transport" save button 895ms

And Click cancel button in transport form 086ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 402ms

Then Check are transport values equals 12s 476ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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 447ms

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 393ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 513ms

And Fill transport form 27s 175ms

And Click "save-transport" save button 780ms

And Click cancel button in transport form 075ms

And Go to transport details "CISTERN_DELIVERY" 4s 300ms

Then Check are transport values equals 6s 294ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 519ms

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 326ms

And Show all transport "false" 009ms

When Go to transport details "CISTERN_COLLECTION" 4s 460ms

And Fill transport form 25s 826ms

And Click "save-transport" save button 730ms

And Click cancel button in transport form 072ms

And Go to transport details "CISTERN_COLLECTION" 4s 350ms

Then Check are transport values equals 6s 277ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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 523ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 207ms

And Show all transport "false" 010ms

When Go to transport details "WEIGHING" 4s 399ms

And Fill transport form 12s 301ms

And Click "save-transport" save button 715ms

And Click cancel button in transport form 057ms

And Go to transport details "WEIGHING" 4s 297ms

Then Check are transport values equals 2s 162ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 398ms

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 364ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 539ms

And Fill transport form 35s 054ms

And Click "save-transport" save button 880ms

And Click cancel button in transport form 082ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 402ms

Then Check are transport values equals 6s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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 081ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 252ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 32s 389ms

And Fill transport form 25s 630ms

And Click "save-transport" save button 692ms

And Click cancel button in transport form 081ms

And Go to transport details "DELIVERY" 32s 318ms

Then Check are transport values equals 2s 204ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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 150ms

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 200ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 678ms

And Fill transport form 57s 223ms

And Click "save-transport" save button 1s 246ms

And Click cancel button in transport form 067ms

And Go to transport details "LOAD" 4s 444ms

Then Check are transport values equals 24s 769ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 088ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 316ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 374ms

And Fill transport form 16s 447ms

And Click "save-transport" save button 716ms

And Click cancel button in transport form 074ms

And Go to transport details "DELIVERY" 4s 308ms

Then Check are transport values equals 074ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 048ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 296ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 302ms

And Fill transport form 28s 183ms

And Click "save-transport" save button 1s 234ms

And Click cancel button in transport form 079ms

And Go to transport details "LOAD" 4s 315ms

Then Check are transport values equals 2s 225ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 163ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 312ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 4s 397ms

And Fill transport form 37s 809ms

And Click "save-transport" save button 767ms

And Click cancel button in transport form 086ms

And Go to transport details "UNLOAD" 4s 323ms

Then Check are transport values equals 6s 377ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 101ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 298ms

And Show all transport "false" 010ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 415ms

And Fill transport form 36s 207ms

And Click "save-transport" save button 725ms

And Click cancel button in transport form 072ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 346ms

Then Check are transport values equals 6s 367ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

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 161ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 196ms

And Show all transport "false" 009ms

When Go to transport details "LOAD" 4s 382ms

And Fill transport form 24s 767ms

And Click "save-transport" save button 717ms

And Click cancel button in transport form 071ms

And Go to transport details "LOAD" 4s 306ms

Then Check are transport values equals 4s 209ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 089ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 182ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 391ms

And Fill transport form 24s 753ms

And Click "save-transport" save button 717ms

And Click cancel button in transport form 066ms

And Go to transport details "CONTAINER" 4s 344ms

Then Check are transport values equals 4s 193ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 255ms

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 243ms

And Show all transport "false" 011ms

When Go to transport details "SMALLS_IMPORT" 4s 499ms

And Fill transport form 33s 007ms

And Click "save-transport" save button 752ms

And Click cancel button in transport form 082ms

And Go to transport details "SMALLS_IMPORT" 4s 318ms

Then Check are transport values equals 8s 343ms

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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 263ms

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 226ms

And Show all transport "false" 008ms

When Go to transport details "SMALLS_EXPORT" 4s 507ms

And Fill transport form 33s 086ms

And Click "save-transport" save button 734ms

And Click cancel button in transport form 065ms

And Go to transport details "SMALLS_EXPORT" 4s 360ms

Then Check are transport values equals 8s 335ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 148ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 304ms

And Show all transport "true" 088ms

When Go to transport details "DELIVERY" 4s 326ms

And Fill transport form 19s 585ms

And Click "save-transport" save button 710ms

And Click cancel button in transport form 091ms

And Go to transport details "DELIVERY" 4s 317ms

Then Check are transport values equals 158ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 130ms

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 247ms

And Show all transport "true" 066ms

When Go to transport details "TRANSPORT_ORDER" 4s 459ms

And Fill transport form 26s 696ms

And Click "save-transport" save button 720ms

And Click cancel button in transport form 073ms

And Go to transport details "TRANSPORT_ORDER" 4s 331ms

Then Check are transport values equals 2s 265ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 152ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 208ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 310ms

And If user is login then logout 081ms

Then Login as "dka1-supplier" 1s 934ms

And Click button advice in transport table "LOAD" 149ms

And Check if moved to first possible start date in schedule 442ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 510ms

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" 101ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 008ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 256ms

Then Go to new transport "LOAD" 387ms

And Fill transport form 23s 383ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

And Go to "COMPANIES_TAB" 442ms

And Go to company "Dostawca Piast Automat 1" details 193ms

And Check if new address with "Adresat" is visible in company details 131ms

And Go to "TRANSPORT_TABLE" 256ms

And Go to transport details "LOAD" 4s 620ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteAddressAfterTest() 087ms

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 169ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 215ms

When Go to "TRANSPORT_TABLE" 113ms

And Show all transport types 1s 036ms

And Verify that transport has "0" files 038ms

Then Add file to transport by API 482ms

And Verify that transport has "1" files 598ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 123ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 209ms

When Go to "TRANSPORT_TABLE" 121ms

And Show all transport types 1s 037ms

And Verify that transport has "0" files 025ms

Then Add file to transport by API 228ms

And Verify that transport has "1" files 540ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 411ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 421ms

When Go to "TRANSPORT_TABLE" 134ms

And Show all transport types 1s 038ms

And Verify that transport has "0" files 045ms

Then Add file to transport by API 228ms

And Verify that transport has "1" files 318ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 214ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 210ms

When Go to "TRANSPORT_TABLE" 130ms

And Show all transport types 1s 040ms

And Verify that transport has "0" files 038ms

Then Add file to transport by API 230ms

And Verify that transport has "1" files 937ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 076ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 192ms

And Delete transport 17s 719ms

When Go to "ARCHIVE_TAB" 256ms

And Show "DELIVERY" 069ms

And Verify that transport has "0" files 662ms

Then Add file to transport 166ms

And Verify that transport has "1" files 396ms

Hooks

After Hooks.deleteTransportAfterTest() 061ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 180ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 213ms

And Delete transport 17s 291ms

When Go to "ARCHIVE_TAB" 254ms

And Show "LOAD" 100ms

And Verify that transport has "0" files 1s 134ms

Then Add file to transport 154ms

And Verify that transport has "1" files 334ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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 435ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 413ms

And Delete transport 17s 888ms

When Go to "ARCHIVE_TAB" 270ms

And Show "DELIVERY" 062ms

And Verify that transport has "0" files 909ms

Then Add file to transport 157ms

And Verify that transport has "1" files 361ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 152ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 202ms

And Delete transport 17s 514ms

When Go to "ARCHIVE_TAB" 237ms

And Show "CONTAINER" 079ms

And Verify that transport has "0" files 980ms

Then Add file to transport 131ms

And Verify that transport has "1" files 376ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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" 113ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 203ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 132ms

And Accept transferred transport by Api 151ms

And Login as "paa1-carrier@qa.qa-test" 1s 186ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 277ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 357ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 253ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 113ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 302ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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" 099ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 202ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 185ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 353ms

And Login as "paa1-carrier@qa.qa-test" 1s 248ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 15s 492ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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 179ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 222ms

When Go to "TRANSPORT_TABLE" 126ms

And Show all transport "true" 068ms

Then Verify that transport has "1" CMR file 1s 172ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR documents are added to transport after creation

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 058ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 272ms

When Go to "TRANSPORT_TABLE" 125ms

And Show all transport "true" 064ms

Then Verify that transport has "2" CMR file 1s 181ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 958ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 257ms

When Go to "TRANSPORT_TABLE" 142ms

And Show all transport "true" 066ms

Then Verify that "CMR" document can be downloaded 17s 585ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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 083ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 268ms

And Show all transport "true" 076ms

And Delete transport 17s 138ms

When Go to "ARCHIVE_TAB" 239ms

And Show "TRANSPORT_ORDER" 052ms

Then Verify that "CMR" document can be downloaded 16s 925ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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" 1s 772ms

And Create default accepted mode of transportation by API with "pba1-carrier" 494ms

And If user is login then logout 295ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 251ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 270ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 126ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 009ms

And Click button advice in transport table "LOAD_PL" 1s 813ms

And Set advice window in schedule 2s 877ms

And Fill advice form 9s 268ms

And Click advice save button and wait for advice form to disappear 30s 891ms

And Find transport in table with status "advice-added" 3s 352ms

When Confirm statuses until reach "on-the-way" 9s 312ms

Then Verify that "delivery_document" document can be downloaded 16s 324ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.deleteModeOfTransportationAfterTest() 085ms

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 586ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 432ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 226ms

And Click pencil and move transport to next day in schedule 16s 893ms

Then Check if transport is in new location in schedule 2s 119ms

And Check if dates in transport form are correct 3s 429ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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 153ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 298ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 244ms

And Click pencil and move transport to next day in schedule 16s 709ms

Then Check if transport is in new location in schedule 2s 121ms

And Check if dates in transport form are correct 3s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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 111ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 348ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 254ms

And Click pencil and move transport to next day in schedule 16s 904ms

Then Check if transport is in new location in schedule 2s 151ms

And Check if dates in transport form are correct 3s 373ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 166ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 350ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 251ms

And Click pencil and move transport to next day in schedule 16s 364ms

Then Check if transport is in new location in schedule 2s 103ms

And Check if dates in transport form are correct 3s 355ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 316ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 247ms

And Click pencil and move transport to next day in schedule 16s 368ms

Then Check if transport is in new location in schedule 2s 118ms

And Check if dates in transport form are correct 3s 373ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 141ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 371ms

And Show all transport "true" 078ms

When Find transport pencil button in transports table 1s 229ms

And Click pencil and move transport to next day in schedule 16s 454ms

Then Check if transport is in new location in schedule 2s 116ms

And Check if dates in transport form are correct 3s 370ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 192ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 202ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 041ms

And Click button advice in transport table "DELIVERY" 111ms

And Set advice window in schedule 2s 603ms

And Fill advice form 8s 352ms

And Click advice save button and wait for advice form to disappear 30s 709ms

And Go to "TRANSPORT_TABLE" 235ms

And Find transport pencil button in transports table 1s 241ms

And Click pencil and move transport to next day in schedule 17s 836ms

Then Check if transport is in new location in schedule 2s 120ms

And Check if dates in transport form are correct 3s 427ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 524ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 470ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 312ms

And Click pencil and move transport to next day in schedule 16s 328ms

And Move advice window "3" 1s 329ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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 140ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 287ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 255ms

And Click pencil and move transport to next day in schedule 16s 752ms

And Move advice window "3" 1s 368ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 019ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 343ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 219ms

And Click pencil and move transport to next day in schedule 16s 912ms

And Move advice window "3" 1s 575ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 188ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 313ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 263ms

And Click pencil and move transport to next day in schedule 16s 291ms

And Move advice window "3" 1s 355ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 220ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 314ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 248ms

And Click pencil and move transport to next day in schedule 16s 326ms

And Move advice window "3" 1s 319ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 167ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 300ms

And Show all transport "true" 067ms

When Find transport pencil button in transports table 1s 210ms

And Click pencil and move transport to next day in schedule 16s 441ms

And Move advice window "3" 1s 369ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 589ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 457ms

And Go to transport details "DELIVERY" 4s 759ms

When Open section: "discrepancy-report-panel" 1s 062ms

Then Verify that no discrepancies found label is visible in discrepancy report section 067ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 446ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 104ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 324ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 461ms

And Go to transport details "DELIVERY" 4s 745ms

And Fill transport form 35s 851ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 103ms

When Go to transport details "DELIVERY" 4s 435ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 422ms

And Click "save-transport" save button 720ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 030ms

And Verify that discrepancy report section contains validation errors 018ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 519ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 410ms

When Go to transport details "DELIVERY" 4s 766ms

Then Verify that discrepancy report section is available 033ms

And Open section: "discrepancy-report-panel" 1s 056ms

And Verify that generate new discrepancy report button is visible 037ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 338ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 376ms

When Go to transport details "OWN_COLLECTION" 4s 654ms

Then Verify that discrepancy report section is available 032ms

And Open section: "discrepancy-report-panel" 1s 063ms

And Verify that generate new discrepancy report button is visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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 346ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 338ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 515ms

Then Verify that discrepancy report section is available 031ms

And Open section: "discrepancy-report-panel" 1s 060ms

And Verify that generate new discrepancy report button is visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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_EXPORT" by JSON file as "super-admin-hochland" 1s 401ms

When Go to transport details "EXPORT" 5s 582ms

Then Verify that discrepancy report section is available 037ms

And Open section: "discrepancy-report-panel" 1s 055ms

And Verify that generate new discrepancy report button is visible 027ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 308ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 158ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 686ms

Then Verify that discrepancy report section is available 033ms

And Open section: "discrepancy-report-panel" 1s 060ms

And Verify that generate new discrepancy report button is visible 036ms

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 310ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 313ms

When Go to transport details "CISTERN_DELIVERY" 4s 494ms

Then Verify that discrepancy report section is not available 15s 009ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 536ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 315ms

When Go to transport details "CISTERN_COLLECTION" 4s 459ms

Then Verify that discrepancy report section is not available 15s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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 322ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 217ms

When Go to transport details "WEIGHING" 4s 390ms

Then Verify that discrepancy report section is not available 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 941ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 472ms

When Go to "TRANSPORT_TABLE" 139ms

And Go to transport details "DELIVERY" 4s 708ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 518ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 333ms

And Open section: "discrepancy-report-panel" 1s 067ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 35s 854ms

And Fill discrepancy report section without closing the form 19s 524ms

And Generate discrepancy report 16s 716ms

And Download discrepancy report 150ms

Then Verify that discrepancy report file has correct values 15s 132ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/46_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() 105ms

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 503ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 461ms

When Go to "TRANSPORT_TABLE" 122ms

And Go to transport details "DELIVERY" 4s 693ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 003ms

And Fill transport form 35s 826ms

And Open section: "discrepancy-report-panel" 1s 070ms

And Fill discrepancy report section without closing the form 19s 648ms

And Generate discrepancy report 16s 216ms

And Download discrepancy report 156ms

And Verify that discrepancy report file has correct values 15s 143ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/47_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() 111ms

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" 109ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 043ms

And Get "LOAD" settings from "piast" 037ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 089ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 194ms

And Login as "piast-admin" 1s 320ms

And Go to "TRANSPORT_TABLE" 202ms

When Go to transport details "LOAD" 4s 679ms

And Add step "unload" 113ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 519ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 520ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 602ms

And Go to transport details "LOAD" 4s 579ms

And Verify that transport has "3" steps 023ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.rollbackTransportTypeSettings() 049ms

After Hooks.rollbackAddedActionAuthorities() 036ms

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 921ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 275ms

When Go to "TRANSPORT_TABLE" 161ms

And Go to transport details "SMALLS_IMPORT" 17s 097ms

Then Verify that user can't edit time range for load and unload 15s 019ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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" 107ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 397ms

And Login as "neuca-admin" 909ms

And Go to "TRANSPORT_TABLE" 206ms

And Show all transport types 15s 010ms

When Go to transport details "DELIVERY" 32s 513ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 071ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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" 109ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 382ms

And Login as "hochland-admin" 1s 471ms

And Go to "TRANSPORT_TABLE" 133ms

And Show all transport types 1s 045ms

When Go to transport details "EXPORT" 5s 558ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 054ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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" 102ms

And Get "DELIVERY" settings from "neuca" 032ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 092ms

And Login as "neuca-admin" 922ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 308ms

When Go to "TRANSPORT_TABLE" 231ms

And Go to transport details "DELIVERY" 32s 474ms

And Set number of pallets in "load" step in transport - "32" 120ms

And Check if number of pallets check message is not visible in transport form 15s 048ms

And Set number of pallets in "load" step in transport - "34" 106ms

Then Check if number of pallets check message is visible in transport form 047ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackTransportTypeSettings() 095ms

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" 110ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 049ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 056ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 065ms

And Login as "farmacol-admin" 1s 467ms

And Go to new transport "EXTERNAL_DELIVERY" 355ms

And Add step "unload" 103ms

And Click "save-transport-and-close" save button 705ms

Then Verify that "time-range-from-date-2" has validation error 1s 031ms

Then Verify that "time-range-to-date-2" has validation error 1s 032ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 320ms

And Click "save-transport-and-close" save button 706ms

And Verify that "time-range-from-date-2" has no validation error 018ms

And Verify that "time-range-to-date-2" has no validation error 016ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.rollbackTransportTypeSettings() 066ms

After Hooks.rollbackAddedActionAuthorities() 036ms

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" 112ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 037ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 192ms

When Login as "piast-admin" 1s 387ms

And Go to transport details "LOAD" 4s 796ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 118ms

And Fill step data 15s 044ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 125ms

And Fill step data 5s 457ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

Then Go to transport details "LOAD" 4s 563ms

And Check if "unload" step is added as "3" step in transport form 042ms

And Check if "load" step is added as "4" step in transport form 032ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackAddedActionAuthorities() 028ms

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" 110ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 042ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 006ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 198ms

When Login as "super-admin-skz" 2s 071ms

And Go to transport details "SMALLS_EXPORT" 4s 501ms

And Check if step is draggable "LOAD" 029ms

And Check if step is not draggable "UNLOAD" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.rollbackAddedActionAuthorities() 033ms

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" 004ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 528ms

When Go to new transport "SMALLS_IMPORT" 370ms

And Fill transport form 19s 804ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 630ms

And Show all transport "false" 009ms

And Go to transport details "SMALLS_IMPORT" 4s 483ms

And Click create similar button 15s 175ms

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 609ms

And Open similar transport details 261ms

Then Check are transport values equals 2s 118ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.deleteSimilarTransportAfterTest() 078ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created without advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 006ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 550ms

When Go to new transport "TRANSPORT_ORDER" 452ms

And Fill transport form 23s 861ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 637ms

And Show all transport "true" 088ms

And Go to transport details "TRANSPORT_ORDER" 4s 395ms

And Click create similar button 15s 207ms

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 598ms

And Open similar transport details 278ms

Then Check are transport values equals 2s 179ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.deleteSimilarTransportAfterTest() 080ms

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" 003ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 641ms

When Go to new transport "DELIVERY" 15s 317ms

And Fill transport form 35s 844ms

And Click "save-transport" save button and wait for form to disappear 15s 699ms

And Set advice window in schedule 2s 159ms

And Check is transport created in schedule and set transport id 816ms

And Go to "TRANSPORT_TABLE" 233ms

And Go to transport details "DELIVERY" 32s 311ms

And Click create similar button 15s 182ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 454ms

And Click "save-transport" save button and wait for form to disappear 15s 632ms

And Set advice window in schedule in "2" days 4s 211ms

And Go to "TRANSPORT_TABLE" 256ms

And Open similar transport details 453ms

Then Check are transport values equals 23s 456ms

Hooks

After Hooks.deleteTransportAfterTest() 014ms

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:175)
	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() 009ms

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.deleteSimilarTransportAfterTest(Hooks.java:188)
	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 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 104ms

When Go to new transport "DELIVERY" 15s 274ms

And Fill transport form 35s 899ms

And Click "save-transport" save button and wait for form to disappear 15s 626ms

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 15s 014ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='slot-114767102-2021-05-01-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.gNZW5P}, 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: 55fa49cc20e69a7dd1e102d5368875c9
*** Element info: {Using=xpath, value=//div[@id='slot-114767102-2021-05-01-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() 001ms

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" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 370ms

When Go to new transport "SMALLS_IMPORT" 372ms

And Fill transport form 32s 984ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 593ms

And Go to transport details "SMALLS_IMPORT" 4s 422ms

And Go to transport print details form 3s 128ms

Then Check are transport values equals 8s 346ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 247ms

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 252ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 176ms

And Go to transport details "SMALLS_IMPORT" 4s 455ms

Then Verify that the transport can be edited 1s 310ms

And Close transport details 15s 135ms

And If user is login then logout 102ms

And Login as "pskza1-carrier@qa.qa-test" 1s 295ms

And Go to transport details "SMALLS_IMPORT" 4s 490ms

And Verify that the transport cannot be edited 46s 338ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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 274ms

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 236ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 100ms

And Go to transport details "SMALLS_EXPORT" 4s 501ms

Then Verify that the transport can be edited 1s 324ms

And Close transport details 15s 117ms

And If user is login then logout 121ms

And Login as "pskza1-carrier@qa.qa-test" 1s 446ms

And Go to transport details "SMALLS_EXPORT" 4s 477ms

And Verify that the transport cannot be edited 46s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 193ms

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 292ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 116ms

And Go to transport details "SMALLS_IMPORT" 4s 459ms

Then Verify that the hidden data in transport are not visible 1s 053ms

And Close transport details 15s 082ms

And If user is login then logout 120ms

And Login as "swisskrono-admin" 1s 418ms

And Go to transport details "SMALLS_IMPORT" 4s 502ms

And Verify that the hidden data in transport are visible 1s 252ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 044ms

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 247ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 179ms

And Go to transport details "SMALLS_EXPORT" 4s 457ms

Then Verify that the hidden data in transport are not visible 1s 041ms

And Close transport details 15s 113ms

And If user is login then logout 124ms

And Login as "swisskrono-admin" 1s 469ms

And Go to transport details "SMALLS_EXPORT" 4s 497ms

And Verify that the hidden data in transport are visible 1s 238ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 415ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 444ms

When Go to transport details "DELIVERY" 4s 711ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 328ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 517ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 493ms

And Fill discrepancy report section without closing the form 19s 599ms

And Click "save-transport" save button 1s 224ms

And Click "save-transport-and-close" save button and wait for form to disappear 639ms

And Check if transport details form is disappeared 15s 049ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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" 109ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 052ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 251ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 433ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 941ms

When Go to "TRANSPORT_TABLE" 128ms

And Go to transport details "DELIVERY" 4s 721ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 350ms

Then Verify that "transport-description" in transport has value "opis" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.rollbackAddedActionAuthorities() 037ms

After Hooks.rollbackWarehousesAccess() 122ms

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" 104ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 406ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 046ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 138ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 708ms

When Go to "TRANSPORT_TABLE" 196ms

And Go to transport details "DELIVERY" 4s 659ms

Then Verify that "transport-description" in transport form is disabled 027ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.rollbackRemovedActionAuthorities() 051ms

After Hooks.rollbackWarehousesAccess() 132ms

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" 103ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 047ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 391ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 691ms

And Show all transport "false" 007ms

When Go to "TRANSPORT_TABLE" 178ms

And Go to transport details "DELIVERY" 4s 669ms

Then Verify that "CARRIER" in transport form is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.rollbackAddedActionAuthorities() 039ms

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" 105ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 044ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 214ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 316ms

And Show all transport "false" 006ms

When Go to "TRANSPORT_TABLE" 102ms

And Go to transport details "TRANSPORT" 4s 489ms

Then Verify that "CARRIER" in transport form is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.rollbackAddedActionAuthorities() 039ms

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" 105ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 041ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 226ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 371ms

And Show all transport "true" 068ms

When Go to "TRANSPORT_TABLE" 133ms

And Go to transport details "TRANSPORT_ORDER" 4s 444ms

Then Verify that "CARRIER" in transport form is visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

After Hooks.rollbackAddedActionAuthorities() 034ms

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" 108ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 043ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 415ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 518ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "DELIVERY" 4s 719ms

Then Verify that "CARRIER" in transport form is not visible 15s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

After Hooks.rollbackRemovedActionAuthorities() 077ms

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" 107ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 038ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 191ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 466ms

And Show all transport "false" 006ms

When Go to "TRANSPORT_TABLE" 139ms

And Go to transport details "TRANSPORT" 4s 467ms

Then Verify that "CARRIER" in transport form is not visible 15s 063ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

After Hooks.rollbackRemovedActionAuthorities() 032ms

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" 099ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 037ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 200ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 518ms

And Show all transport "true" 066ms

When Go to "TRANSPORT_TABLE" 130ms

And Go to transport details "TRANSPORT_ORDER" 4s 477ms

Then Verify that "CARRIER" in transport form is not visible 15s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.rollbackRemovedActionAuthorities() 046ms

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" 101ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 048ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 425ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 757ms

And Show all transport "false" 003ms

When Go to "TRANSPORT_TABLE" 214ms

And Go to transport details "DELIVERY" 4s 717ms

Then Verify that "CARRIER" in transport form is not disabled 033ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackAddedActionAuthorities() 067ms

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" 109ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 044ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 049ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 233ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 416ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 119ms

And Go to transport details "TRANSPORT" 4s 501ms

Then Verify that "CARRIER" in transport form is not disabled 028ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackAddedActionAuthorities() 071ms

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" 111ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 042ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 236ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 384ms

And Show all transport "true" 070ms

When Go to "TRANSPORT_TABLE" 128ms

And Go to transport details "TRANSPORT_ORDER" 4s 467ms

Then Verify that "CARRIER" in transport form is not disabled 026ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.rollbackAddedActionAuthorities() 066ms

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" 112ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 034ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 043ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 416ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 363ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 207ms

And Go to transport details "DELIVERY" 4s 719ms

Then Verify that "CARRIER" in transport form is disabled 028ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.rollbackAddedActionAuthorities() 034ms

After Hooks.rollbackRemovedActionAuthorities() 036ms

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" 107ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 043ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 008ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 228ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 304ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 117ms

And Go to transport details "TRANSPORT" 4s 456ms

Then Verify that "CARRIER" in transport form is disabled 028ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.rollbackAddedActionAuthorities() 052ms

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" 108ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 050ms

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 228ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 406ms

And Show all transport "true" 069ms

When Go to "TRANSPORT_TABLE" 108ms

And Go to transport details "TRANSPORT_ORDER" 4s 443ms

Then Verify that "CARRIER" in transport form is disabled 027ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.rollbackAddedActionAuthorities() 036ms

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 298ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 046ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 042ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 045ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 358ms

When Find transport in table with status "planned" 3s 302ms

And Confirm statuses until reach "process-ended" 21s 559ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 293ms

And Show "DELIVERY" 075ms

And Go to transport details "DELIVERY" 32s 430ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 317ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 589ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 345ms

Then Verify that "transport-description" in transport has value "opis" 032ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.rollbackAddedActionAuthorities() 036ms

After Hooks.rollbackRemovedActionAuthorities() 086ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 899ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 436ms

When Go to transport details "DELIVERY" 4s 710ms

And Fill transport form 35s 875ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 397ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 136ms

And Go to new transport "DELIVERY" 321ms

Then Verify that driver "XXX ZZZ" is in list 670ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 251ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 221ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 245ms

And If user is login then logout 107ms

And Login as "pskza1-carrier@qa.qa-test" 1s 239ms

Then Verify that the transport has been transferred 1s 134ms

And Accept or reject "accept" transferred transport 15s 726ms

And Go to transport details "SMALLS_IMPORT" 4s 534ms

And Verify that "transaction-price" in transport form is visible 037ms

And Verify that transaction price field has correct value 018ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 052ms

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 267ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 217ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 163ms

And If user is login then logout 116ms

And Login as "pskza1-carrier@qa.qa-test" 1s 276ms

Then Verify that the transport has been transferred 1s 148ms

And Accept or reject "accept" transferred transport 15s 784ms

And Go to transport details "SMALLS_EXPORT" 4s 535ms

And Verify that "transaction-price" in transport form is visible 035ms

And Verify that transaction price field has correct value 026ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 114ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 258ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 002ms

When Login as "dayco-admin" 1s 354ms

And Click button advice in transport table "OWN_COLLECTION" 264ms

And Set advice window in schedule 2s 567ms

And Fill advice form 6s 934ms

And Click advice save button and wait for advice form to disappear 30s 663ms

And Go to "TRANSPORT_TABLE" 212ms

And Find transport in table with status "planned" 3s 242ms

And Confirm statuses until reach "on-the-area" 3s 788ms

And Go to transport details "OWN_COLLECTION" 4s 420ms

And Click create similar button 15s 109ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 472ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 608ms

And Open similar transport details 280ms

Then Check if transport form modal is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.deleteSimilarTransportAfterTest() 104ms

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" 118ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 239ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 920ms

And Click button advice in transport table "OWN_COLLECTION" 335ms

And Set advice window in schedule 2s 513ms

And Fill advice form 6s 932ms

And Click advice save button and wait for advice form to disappear 30s 738ms

And Go to "TRANSPORT_TABLE" 210ms

And Find transport in table with status "planned" 3s 261ms

And Confirm statuses until reach "during-load" 6s 564ms

And Go to transport details "OWN_COLLECTION" 4s 475ms

And Click create similar button 15s 121ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 483ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 630ms

And Open similar transport details 321ms

Then Check if transport form modal is visible 025ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.deleteSimilarTransportAfterTest() 076ms

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 353ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 290ms

And Show all transport types 1s 047ms

Then Check if transport number is visible "DELIVERY" 15s 097ms

And Check if transport details is not visible 15s 008ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 964ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 138ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 472ms

When Click on transport row 060ms

Then Verify if transport row is selected 026ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 415ms

And Show all transport "false" 007ms

And Go to "TRANSPORT_TABLE" 114ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 289ms

When Click on transport row 052ms

Then Verify if transport row is selected 029ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 253ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 112ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 295ms

When Click on transport row 056ms

Then Verify if transport row is selected 021ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 217ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 119ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 314ms

When Click on transport row 072ms

Then Verify if transport row is selected 024ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 583ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 115ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 329ms

When Click on transport row 051ms

Then Verify if transport row is selected 020ms

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 410ms

And Show all transport "true" 060ms

And Go to "TRANSPORT_TABLE" 119ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 295ms

When Click on transport row 065ms

Then Verify if transport row is selected 029ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 719ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 326ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 082ms

When Accept or reject "accept" transferred transport 17s 767ms

Then Verify that transport is accept or reject "accept" 011ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 446ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 227ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 086ms

When Accept or reject "reject" transferred transport 17s 004ms

Then Verify that transport is accept or reject "reject" 15s 012ms

Hooks

After Hooks.deleteTransportAfterTest() 057ms

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 855ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 574ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 085ms

When Accept or reject "accept" transferred transport 18s 574ms

Then Verify that transport is accept or reject "accept" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 262ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 301ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 096ms

When Accept or reject "reject" transferred transport 18s 571ms

Then Verify that transport is accept or reject "reject" 15s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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 224ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 304ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 078ms

When Accept or reject "accept" transferred transport 18s 634ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 195ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 320ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 075ms

When Accept or reject "reject" transferred transport 18s 576ms

Then Verify that transport is accept or reject "reject" 15s 059ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 151ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 269ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 127ms

And If user is login then logout 099ms

And Login as "paa1-carrier@qa.qa-test" 1s 480ms

Then Verify that the transport has been transferred with "true" 1s 200ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 012ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 222ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 174ms

And If user is login then logout 094ms

And Login as "paa1-carrier@qa.qa-test" 1s 506ms

Then Verify that the transport has been transferred with "false" 1s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 068ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 206ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 102ms

And If user is login then logout 113ms

And Login as "pskza1-carrier@qa.qa-test" 1s 438ms

Then Verify that the transport has been transferred 1s 146ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 138ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 222ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 162ms

And If user is login then logout 337ms

And Login as "pskza1-carrier@qa.qa-test" 1s 193ms

Then Verify that the transport has been transferred 1s 120ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 041ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 229ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 376ms

And Go to auction offer 1s 228ms

When Offer "1000" 125ms

And Verify that offer with "1000" has been added to auction 3s 034ms

And If user is login then logout 076ms

And Login as "swisskrono-admin" 1s 271ms

Then Go to auction details 1s 195ms

And Pass transport to carrier from auction details 1s 278ms

And If user is login then logout 617ms

And Login as "pskza1-carrier@qa.qa-test" 1s 188ms

And Verify that the transport has been transferred 1s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 067ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 282ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 116ms

And Go to auction offer 1s 181ms

When Offer "1000" 143ms

And Verify that offer with "1000" has been added to auction 3s 039ms

And Wait till auction end 1m 54s 017ms

And If user is login then logout 120ms

Then Login as "swisskrono-admin" 1s 345ms

And Go to auction details 1s 192ms

And Pass transport to carrier from auction details 1s 257ms

And If user is login then logout 600ms

And Login as "pskza1-carrier@qa.qa-test" 1s 159ms

And Verify that the transport has been transferred 1s 133ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 101ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 246ms

And Go to "TRANSPORT_TABLE" 142ms

When Open transport transfer modal 1s 376ms

Then Verify that all enabled companies from "swisskrono" are shown in select 119ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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" 110ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 392ms

And Login as "adama-admin" 902ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 211ms

And Go to "TRANSPORT_TABLE" 128ms

When Open transport transfer modal 1s 238ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 100ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.rollbackRejectedSections() 096ms

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" 990ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 214ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 248ms

And If user is login then logout 118ms

When Login as "paa1-carrier@qa.qa-test" 1s 927ms

And Verify that the transport has been transferred with "true" 1s 324ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 011ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 195ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 339ms

When Go to "TRANSPORT_TABLE" 109ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 396ms

Then Check if new assortment group is disabled in transport form 030ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to advice transport after double cancellation.

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 012ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 178ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 002ms

When Show all transport types 1s 046ms

And Click button advice in transport table "CONTAINER" 105ms

And Set advice window in schedule 2s 426ms

And Click button cancel in advice form 15s 284ms

And Set advice window in schedule 2s 144ms

And Click button cancel in advice form 15s 288ms

And Set advice window in schedule 2s 128ms

And Fill advice form 15s 777ms

And Click advice save button and wait for advice form to disappear 30s 727ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "CONTAINER" 4s 447ms

Then Check are advice values equals 2s 352ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 098ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 001ms

When Go to new transport "TRANSPORT" 368ms

And Fill transport form 26s 769ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 233ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 106ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 457ms

And Accept or reject "reject" transferred transport 15s 795ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 096ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 159ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 296ms

And Accept or reject "accept" transferred transport 15s 838ms

Then Verify that transport is accept or reject "accept" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 189ms

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 227ms

When Show all transport types 1s 045ms

And Click button advice in transport table "DELIVERY" 107ms

And Set advice window in schedule 2s 631ms

And Click button cancel in advice form 15s 342ms

And Go to "TRANSPORT_TABLE" 210ms

When Go to transport details "DELIVERY" 4s 536ms

And Fill transport form 1m 2s 251ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 233ms

And Go to transport details "DELIVERY" 4s 452ms

Then Check are transport values equals 24s 792ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3426	30	49	0	0	3505	353	32	385	5h 45m 13s 886ms	Failed

Tag Report