Cucumber-JVM Reports - Feature: Advice transport

Project	Number	Date
ApolloFullRunnerReport	develop.317	24 lut 2021, 06:32

	Steps	Scenarios	Features
Advice transport	395	7	6	0	0	408	32	7	39	29m 25s 920ms	Failed

@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 "adama-admin" and set token of apiUsername "super-admin-adama" 1s 649ms

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

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

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

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

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

And Fill advice form 16s 017ms

And Click advice save button to check error message 088ms

Then Check if possible advice alert is displayed 027ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

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

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

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

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

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

And Fill advice form 8s 478ms

And Click advice save button to check error message 105ms

Then Check if possible advice alert is displayed 023ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

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

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

And Fill advice form 8s 460ms

And Click advice save button to check error message 105ms

Then Check if possible advice alert is displayed 030ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

@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 159ms

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

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

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

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

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

And Fill advice form 13s 311ms

And Click advice save button to check error message 100ms

Then Check if possible advice alert is displayed 035ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

@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 212ms

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

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

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

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

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

And Fill advice form 13s 281ms

And Click advice save button to check error message 084ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

@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 035ms

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

And Show all transport types 1s 051ms

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

And Go to "TRANSPORT_TABLE" 170ms

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

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

And Fill transport form 4s 735ms

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

And Expand advice panel 111ms

And Edit advice in transport details 12s 601ms

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

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

And Expand advice panel 124ms

Then Check are advice values equals after edition 235ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

@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 260ms

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

And Show all transport types 1s 056ms

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

And Go to "TRANSPORT_TABLE" 213ms

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

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

And Fill transport form 1m 2s 597ms

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

And Expand advice panel 109ms

And Edit advice in transport details 6s 732ms

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

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

And Expand advice panel 115ms

Then Check are advice values equals after edition 100ms

Hooks

After Hooks.deleteTransportAfterTest() 159ms

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

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

And Show all transport types 1s 048ms

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

And Go to "TRANSPORT_TABLE" 195ms

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

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

And Fill transport form 57s 598ms

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

And Expand advice panel 127ms

And Edit advice in transport details 6s 707ms

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

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

And Expand advice panel 105ms

Then Check are advice values equals after edition 080ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

@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 195ms

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

And Show all transport types 1s 063ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

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

And Fill transport form 24s 815ms

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

And Expand advice panel 104ms

And Edit advice in transport details 18s 708ms

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

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

And Expand advice panel 118ms

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

And Show all transport types 1s 043ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

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

And Fill transport form 24s 807ms

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

And Expand advice panel 128ms

And Edit advice in transport details 18s 702ms

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

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

And Expand advice panel 088ms

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

@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 145ms

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

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

When Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 375ms

And Fill advice form 12s 531ms

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

And Go to "TRANSPORT_TABLE" 208ms

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

Then Check are advice values equals 310ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 6s 449ms

And Fill advice form 11s 917ms

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

And Go to "TRANSPORT_TABLE" 207ms

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

Then Check are advice values equals 2s 369ms

Hooks

After Hooks.deleteTransportAfterTest() 159ms

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

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

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

When Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 537ms

And Fill advice form 8s 492ms

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

And Go to "TRANSPORT_TABLE" 210ms

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

Then Check are advice values equals 229ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 551ms

And Fill advice form 8s 415ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

Then Check are advice values equals 240ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

@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 177ms

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

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

When Show all transport types 1s 052ms

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

And Set advice window in schedule 2s 415ms

And Fill advice form 13s 228ms

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

And Go to "TRANSPORT_TABLE" 191ms

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

Then Check are advice values equals 2s 357ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

@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 184ms

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 390ms

And Fill advice form 13s 314ms

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

And Go to "TRANSPORT_TABLE" 164ms

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

Then Check are advice values equals 2s 326ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 37s 723ms

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

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

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

Then Set advice window in schedule 2s 291ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

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

Error message

org.junit.ComparisonFailure: Transport został poprawnie utworzony w domyślnym magazynie: Ołtarzew expected:<[Katowice]> but was:<[Ołtarzew]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkWarehouseInTransportDetails(Transport.java:272)
	at CucumberTests.Transport.TransportFormTest.checkIfTransportHasWarehouseInStepSection(TransportFormTest.java:210)
	at ✽.Check if transport has warehouse "Ołtarzew" in step section "1"(file:Features/Atom/Advice/AdviceTransport.feature:83)

Hooks

After Hooks.deleteTransportAfterTest() 136ms

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Steps

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

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

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

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

And Accept transferred transport by Api 305ms

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 364ms

And Fill advice form 11s 999ms

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

And Go to "TRANSPORT_TABLE" 223ms

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

Then Check are advice values equals 2s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Steps

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

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

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

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

And Accept transferred transport by Api 106ms

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

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

When Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 617ms

And Fill advice form 14s 696ms

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

And Go to "TRANSPORT_TABLE" 180ms

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

Then Check are advice values equals 2s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Steps

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

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

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

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

And Accept transferred transport by Api 105ms

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 581ms

And Fill advice form 14s 668ms

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

And Go to "TRANSPORT_TABLE" 179ms

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

Then Check are advice values equals 2s 387ms

Hooks

After Hooks.deleteTransportAfterTest() 170ms

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 099ms

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

When Show all transport types 1s 046ms

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

And Set week view 1s 522ms

And Show yesterday 1s 121ms

Then Check if advice restriction blockade windows are visible 022ms

Hooks

After Hooks.deleteTransportAfterTest() 192ms

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 100ms

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

When Show all transport types 1s 041ms

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

And Set week view 2s 055ms

And Show yesterday 1s 099ms

Then Check if advice restriction blockade windows are visible 035ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 102ms

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

When Show all transport types 1s 042ms

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

And Set week view 2s 138ms

And Show yesterday 1s 128ms

Then Check if advice restriction blockade windows are visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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

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

And Show all transport "false" 032ms

And Click on time window date 1s 278ms

And Select view "DAYS_4" 2s 067ms

And Move advice window "3" 1s 336ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

@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 021ms

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

And Show all transport "false" 018ms

And Click on time window date 15s 686ms

And Select view "DAYS_4" 2s 080ms

And Move advice window "3" 1s 491ms

Then Check if advice window is in new location 140ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

And Show all transport "false" 016ms

And Click on time window date 15s 569ms

And Select view "DAYS_4" 2s 064ms

And Move advice window "3" 1s 397ms

Then Check if advice window is in new location 029ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 395ms

And Select view "DAYS_4" 2s 070ms

And Move advice window "3" 1s 374ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

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

And Show all transport "false" 018ms

And Click on time window date 1s 304ms

And Select view "DAYS_4" 2s 067ms

And Move advice window "3" 1s 320ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

@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 075ms

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

And Show all transport "true" 087ms

And Click on time window date 1s 340ms

And Select view "DAYS_4" 2s 070ms

And Move advice window "3" 1s 353ms

Then Check if advice window is in new location 019ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

@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 154ms

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 561ms

And Fill advice form 8s 517ms

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

And Go to "TRANSPORT_TABLE" 223ms

And Click on time window date 1s 414ms

And Select view "DAYS_4" 2s 060ms

And Move advice window "3" 1s 430ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

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

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.Transport.TransportUtilTest.checkIfTransportRowIs(TransportUtilTest.java:35)
	at ✽.Check if transport row is "red"(file:Features/Atom/Advice/AdviceTransport.feature:171)

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

And Go to "TRANSPORT_TABLE" 124ms

And Show all transport types 1s 050ms

And Click on time window date 1s 284ms

And Scroll to time window "adviceWindow" 043ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 111ms

And Show all transport types 1s 048ms

And Click on time window date 1s 409ms

And Scroll to time window "adviceWindow" 045ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

@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 082ms

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

And Go to "TRANSPORT_TABLE" 119ms

And Show all transport types 1s 046ms

And Click on time window date 1s 304ms

And Scroll to time window "adviceWindow" 055ms

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

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

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

@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 007ms

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

And Go to "TRANSPORT_TABLE" 242ms

And Show all transport types 15s 030ms

And Click on time window date 15s 910ms

And Scroll to time window "adviceWindow" 043ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 111ms

@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 175ms

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

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 560ms

And Fill advice form 8s 416ms

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

And Go to "TRANSPORT_TABLE" 221ms

And Click on time window date 1s 423ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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

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

And Go to "WAREHOUSE_TAB" 752ms

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

When Go to new transport "DELIVERY" 408ms

And Fill transport form 31s 248ms

Error message

java.lang.AssertionError: Nie można wypełnić pola temperature-[°c], ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Advice/AdviceTransport.feature:219)

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

And Click previous page button in browser 000ms

Then Check if advice window can't be created 000ms

Hooks

After Hooks.deleteTransportAfterTest() 002ms

@deleteTransportAfterTest

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

Steps

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

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

And Go to "WAREHOUSE_TAB" 745ms

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

When Go to new transport "DELIVERY" 416ms

And Fill transport form 31s 176ms

Error message

java.lang.AssertionError: Nie można wypełnić pola temperature-[°c], ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Advice/AdviceTransport.feature:234)

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

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

Then Check if advice window can't be created 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

@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 200ms

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

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

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

When Show all transport types 1s 039ms

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

And Fill advice form 11s 595ms

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

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

And Open statuses popup 124ms

And Wait "2" seconds 2s

Then Check if transport has checkpoints from list "Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta" in "1" 15s 043ms

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Advice transport	395	7	6	0	0	408	32	7	39	29m 25s 920ms	Failed

Feature Report