Cucumber-JVM Reports - Feature: Advice transport

Project	Number	Date
ApolloFullRunnerReport	kapibary.19	27 maj 2021, 08:37

	Steps	Scenarios	Features
Advice transport	398	6	33	0	0	437	35	6	41	35m 9s 222ms	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" 6s 168ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 286ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 8s 524ms

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

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

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

And Fill advice form 19s 844ms

And Click advice save button to check error message 201ms

Then Check if possible advice alert is displayed 064ms

Hooks

After Hooks.deleteTransportAfterTest() 591ms

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 002ms

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

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

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

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

And Fill advice form 10s 576ms

And Click advice save button to check error message 201ms

Then Check if possible advice alert is displayed 080ms

Hooks

After Hooks.deleteTransportAfterTest() 562ms

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

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

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

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

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

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

And Fill advice form 10s 615ms

And Click advice save button to check error message 202ms

Then Check if possible advice alert is displayed 071ms

Hooks

After Hooks.deleteTransportAfterTest() 639ms

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 005ms

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

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

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

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

And Fill advice form 16s 576ms

And Click advice save button to check error message 200ms

Then Check if possible advice alert is displayed 070ms

Hooks

After Hooks.deleteTransportAfterTest() 585ms

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 2s 041ms

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

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

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

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

And Fill advice form 16s 312ms

And Click advice save button to check error message 198ms

Then Check if possible advice alert is displayed 068ms

Hooks

After Hooks.deleteTransportAfterTest() 531ms

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

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

And Show all transport types 1s 171ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 56s 597ms

And Go to "TRANSPORT_TABLE" 454ms

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

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

And Fill transport form 5s 232ms

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

And Expand advice panel 283ms

And Edit advice in transport details 15s 536ms

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

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

And Expand advice panel 247ms

Then Check are advice values equals after edition 678ms

Hooks

After Hooks.deleteTransportAfterTest() 841ms

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

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

And Show all transport types 1s 161ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 47s 653ms

And Go to "TRANSPORT_TABLE" 511ms

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

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

And Fill transport form 1m 8s 892ms

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

And Expand advice panel 268ms

And Edit advice in transport details 8s 189ms

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

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

And Expand advice panel 279ms

Then Check are advice values equals after edition 328ms

Hooks

After Hooks.deleteTransportAfterTest() 882ms

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

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

And Show all transport types 1s 137ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-piast" 47s 356ms

And Go to "TRANSPORT_TABLE" 452ms

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

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

And Fill transport form 1m 3s 251ms

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

And Expand advice panel 268ms

And Edit advice in transport details 8s 137ms

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

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

And Expand advice panel 262ms

Then Check are advice values equals after edition 315ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

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

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

And Show all transport types 1s 170ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 53s 156ms

And Go to "TRANSPORT_TABLE" 425ms

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

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

And Fill transport form 27s 133ms

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

And Expand advice panel 220ms

And Edit advice in transport details 21s 473ms

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

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

And Expand advice panel 269ms

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

Hooks

After Hooks.deleteTransportAfterTest() 847ms

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

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

And Show all transport types 1s 163ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-keeeper" 53s 108ms

And Go to "TRANSPORT_TABLE" 462ms

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

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

And Fill transport form 27s 013ms

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

And Expand advice panel 248ms

And Edit advice in transport details 21s 548ms

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

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

And Expand advice panel 248ms

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

Hooks

After Hooks.deleteTransportAfterTest() 774ms

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

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

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

When Show all transport types 1s 165ms

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

And Set advice window in schedule 3s 223ms

And Fill advice form 15s 898ms

And Click advice save button and wait for advice form to disappear 32s 868ms

And Go to "TRANSPORT_TABLE" 425ms

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

Then Check are advice values equals 901ms

Hooks

After Hooks.deleteTransportAfterTest() 824ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 137ms

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

And Set advice window in schedule 7s 597ms

And Fill advice form 14s 687ms

And Click advice save button and wait for advice form to disappear 33s 335ms

And Go to "TRANSPORT_TABLE" 449ms

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

Then Check are advice values equals 2s 826ms

Hooks

After Hooks.deleteTransportAfterTest() 982ms

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

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

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

When Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 510ms

And Fill advice form 10s 589ms

And Click advice save button and wait for advice form to disappear 32s 673ms

And Go to "TRANSPORT_TABLE" 474ms

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

Then Check are advice values equals 592ms

Hooks

After Hooks.deleteTransportAfterTest() 845ms

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

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

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

When Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 501ms

And Fill advice form 10s 518ms

And Click advice save button and wait for advice form to disappear 33s 275ms

And Go to "TRANSPORT_TABLE" 482ms

And Go to transport details "LOAD" 5s 001ms

Then Check are advice values equals 577ms

Hooks

After Hooks.deleteTransportAfterTest() 839ms

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

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

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

When Show all transport types 1s 167ms

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

And Set advice window in schedule 3s 316ms

And Fill advice form 16s 273ms

And Click advice save button and wait for advice form to disappear 32s 768ms

And Go to "TRANSPORT_TABLE" 464ms

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

Then Check are advice values equals 2s 914ms

Hooks

After Hooks.deleteTransportAfterTest() 838ms

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

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

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

When Show all transport types 1s 173ms

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

And Set advice window in schedule 3s 258ms

And Fill advice form 16s 103ms

And Click advice save button and wait for advice form to disappear 32s 859ms

And Go to "TRANSPORT_TABLE" 453ms

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

Then Check are advice values equals 2s 913ms

Hooks

After Hooks.deleteTransportAfterTest() 841ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 090ms

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

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

And Accept transferred transport by Api 6s 663ms

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

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

When Show all transport types 1s 358ms

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

And Set advice window in schedule 3s 283ms

And Fill advice form 14s 622ms

And Click advice save button and wait for advice form to disappear 33s 247ms

And Go to "TRANSPORT_TABLE" 520ms

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

Then Check are advice values equals 2s 727ms

Hooks

After Hooks.deleteTransportAfterTest() 766ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 191ms

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

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

And Accept transferred transport by Api 709ms

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

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

When Show all transport types 1s 210ms

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

And Set advice window in schedule 3s 673ms

And Fill advice form 17s 911ms

And Click advice save button and wait for advice form to disappear 33s 279ms

And Go to "TRANSPORT_TABLE" 436ms

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

Then Check are advice values equals 2s 859ms

Hooks

After Hooks.deleteTransportAfterTest() 831ms

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 163ms

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

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

And Accept transferred transport by Api 622ms

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

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

When Show all transport types 1s 227ms

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

And Set advice window in schedule 3s 496ms

And Fill advice form 17s 985ms

And Click advice save button and wait for advice form to disappear 33s 340ms

And Go to "TRANSPORT_TABLE" 428ms

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

Then Check are advice values equals 2s 911ms

Hooks

After Hooks.deleteTransportAfterTest() 810ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 032ms

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

And Accept transferred transport by Api 014ms

Error message

java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:117)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getLongResult(ApolloSelectDbService.java:107)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findIdBy(ApolloSelectDbService.java:19)
	at CucumberTests.Transport.CarrierTransportAction.acceptTransferredTransportByApi(CarrierTransportAction.java:77)
	at ✽.Accept transferred transport by Api(file:Features/Atom/Advice/AdviceTransport.feature:117)

And Login as "paa1-carrier@qa.qa-test" 000ms

When Show all transport types 000ms

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

And Set week view 000ms

And Show yesterday 000ms

Then Check if advice restriction blockade windows are visible 000ms

Hooks

After Hooks.deleteTransportAfterTest() 714ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 114ms

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

And Accept transferred transport by Api 012ms

Error message

java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:117)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getLongResult(ApolloSelectDbService.java:107)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findIdBy(ApolloSelectDbService.java:19)
	at CucumberTests.Transport.CarrierTransportAction.acceptTransferredTransportByApi(CarrierTransportAction.java:77)
	at ✽.Accept transferred transport by Api(file:Features/Atom/Advice/AdviceTransport.feature:117)

And Login as "pskza1-carrier@qa.qa-test" 000ms

When Show all transport types 000ms

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

And Set week view 000ms

And Show yesterday 000ms

Then Check if advice restriction blockade windows are visible 000ms

Hooks

After Hooks.deleteTransportAfterTest() 787ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 059ms

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

And Accept transferred transport by Api 015ms

Error message

java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:117)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getLongResult(ApolloSelectDbService.java:107)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findIdBy(ApolloSelectDbService.java:19)
	at CucumberTests.Transport.CarrierTransportAction.acceptTransferredTransportByApi(CarrierTransportAction.java:77)
	at ✽.Accept transferred transport by Api(file:Features/Atom/Advice/AdviceTransport.feature:117)

And Login as "pskza1-carrier@qa.qa-test" 000ms

When Show all transport types 000ms

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

And Set week view 000ms

And Show yesterday 000ms

Then Check if advice restriction blockade windows are visible 000ms

Hooks

After Hooks.deleteTransportAfterTest() 791ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 2s 928ms

And Show all transport "false" 174ms

And Click on time window date 1s 662ms

And Select view "DAYS_4" 2s 164ms

And Move advice window "3" 1s 499ms

Then Check if advice window is in new location 063ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 023ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 319ms

And Show all transport "false" 158ms

And Click on time window date 16s 120ms

And Select view "DAYS_4" 2s 178ms

And Move advice window "3" 1s 709ms

Then Check if advice window is in new location 080ms

Hooks

After Hooks.deleteTransportAfterTest() 416ms

@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" 5s 134ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 443ms

And Show all transport "false" 159ms

And Click on time window date 15s 925ms

And Select view "DAYS_4" 2s 152ms

And Move advice window "3" 1s 596ms

Then Check if advice window is in new location 068ms

Hooks

After Hooks.deleteTransportAfterTest() 845ms

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 584ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 610ms

And Show all transport "false" 158ms

And Click on time window date 1s 872ms

And Select view "DAYS_4" 2s 166ms

And Move advice window "3" 1s 543ms

Then Check if advice window is in new location 073ms

Hooks

After Hooks.deleteTransportAfterTest() 713ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 684ms

And Show all transport "false" 159ms

And Click on time window date 1s 824ms

And Select view "DAYS_4" 2s 162ms

And Move advice window "3" 1s 472ms

Then Check if advice window is in new location 061ms

Hooks

After Hooks.deleteTransportAfterTest() 737ms

@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" 4s 531ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 529ms

And Show all transport "true" 320ms

And Click on time window date 1s 730ms

And Select view "DAYS_4" 2s 162ms

And Move advice window "3" 1s 497ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 399ms

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

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

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

When Show all transport types 1s 149ms

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

And Set advice window in schedule 3s 392ms

And Fill advice form 10s 464ms

And Click advice save button and wait for advice form to disappear 33s 369ms

And Go to "TRANSPORT_TABLE" 489ms

And Click on time window date 1s 837ms

And Select view "DAYS_4" 2s 154ms

And Move advice window "3" 1s 629ms

Then Check if advice window is in new location 066ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 428ms

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 856ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 2s 883ms

And Go to "TRANSPORT_TABLE" 413ms

And Show all transport types 1s 143ms

And Click on time window date 1s 787ms

And Scroll to time window "adviceWindow" 150ms

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

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

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 604ms

And Go to "TRANSPORT_TABLE" 401ms

And Show all transport types 1s 205ms

And Click on time window date 1s 902ms

And Scroll to time window "adviceWindow" 160ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 874ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 673ms

And Go to "TRANSPORT_TABLE" 467ms

And Show all transport types 1s 141ms

And Click on time window date 1s 689ms

And Scroll to time window "adviceWindow" 152ms

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

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

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 16s 738ms

And Go to "TRANSPORT_TABLE" 544ms

And Show all transport types 15s 048ms

And Click on time window date 16s 160ms

And Scroll to time window "adviceWindow" 217ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 785ms

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

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

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

When Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 495ms

And Fill advice form 10s 523ms

And Click advice save button and wait for advice form to disappear 32s 810ms

And Go to "TRANSPORT_TABLE" 510ms

And Click on time window date 1s 843ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 474ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 132ms

And Go to "WAREHOUSE_TAB" 1s 254ms

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

When Go to new transport "DELIVERY" 669ms

And Fill transport form 44s 988ms

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

And Click previous page button in browser 062ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 288ms

And Go to "WAREHOUSE_TAB" 1s 274ms

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

When Go to new transport "DELIVERY" 667ms

And Fill transport form 44s 932ms

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

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

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

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

And Create transport "CREATE_TRANSPORT_WITHOUT_WAREHOUSES" by JSON file as "super-admin-adama" 2s 509ms

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

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

When Show all transport types 1s 141ms

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

And Fill advice form 13s 906ms

And Click advice save button and wait for advice form to disappear 32s 630ms

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

And Open statuses popup 196ms

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

Hooks

After Hooks.deleteTransportAfterTest() 619ms

@deleteAllTransportsAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if mode of transportation select is still empty after selecting driver in advice form

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 5s 449ms

And Create default accepted mode of transportation by API with "pba1-carrier" 2s 080ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 2s 145ms

And Set "advice" inputs from JSON file "ADVICE_LOAD_PL" "super-admin-bausch" 003ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "true" confirmation 797ms

And Click button advice in transport table "LOAD_PL" 2s 162ms

And Set advice window in schedule 3s 770ms

And Fill advice form 11s 594ms

And Click advice save button and wait for advice form to disappear 33s 342ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 16s 113ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "true" confirmation 783ms

When Go to "TRANSPORT_TABLE" 514ms

And Show all transport types 1s 170ms

And Click button advice in transport table "LOAD_PL" 2s 343ms

And Set advice window in schedule 3s 589ms

And Select driver "Marek Kanarek" from suggestions 2s 345ms

Then Verify if mode of transportation select is empty 102ms

Hooks

After Hooks.deleteAllTransports() 48s 840ms

After Hooks.deleteModeOfTransportationAfterTest() 452ms

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 507ms

And Login as "farmacol-admin" 7s 030ms

And Go to "WAREHOUSE_TAB" 1s 073ms

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

And Set week view 2s 568ms

And Move cursor over time window element 448ms

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

Hooks

After Hooks.deleteTransportAfterTest() 713ms

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is possible to advice transport after splitting advice data from advice window

- order: advice data => advice window [A-7478]

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 4s 431ms

And Create default accepted mode of transportation by API with "pba1-carrier" 1s 951ms

And Create transport "CREATE_EXW_DELIVERY" by JSON file as "super-admin-bausch" 551ms

Error message

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

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:76)
	at ✽.Create transport "CREATE_EXW_DELIVERY" by JSON file as "super-admin-bausch"(file:Features/Atom/Advice/AdviceTransport.feature:331)

And Set "advice" inputs from JSON file "ADVICE_EXW_DELIVERY" "super-admin-bausch" 000ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "true" confirmation 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Show all transport types 000ms

And Click button advice in transport table "EXW_DELIVERY" 000ms

And Fill advice form 000ms

And Click advice save button and wait for advice form to disappear 000ms

And Click button advice in transport table "EXW_DELIVERY" 000ms

And Set advice window in schedule 000ms

And Change filled value in transport details "rodo-acceptance" "checkbox" "true" "0" 000ms

And Click advice save button and wait for advice form to disappear 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Show all transport types 000ms

And Go to transport details "EXW_DELIVERY" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteModeOfTransportationAfterTest() 388ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Advice transport	398	6	33	0	0	437	35	6	41	35m 9s 222ms	Failed

Feature Report