Cucumber-JVM Reports - Feature: Status confirmation

Project	Number	Date
ApolloFullRunnerReport	develop.371	07 kwi 2021, 19:36

	Steps	Scenarios	Features
Status confirmation	389	15	45	0	0	449	22	15	37	28m 14s 499ms	Failed

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

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

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

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

Then Check if transport has "departed" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

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

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

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

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

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

And Set advice window in schedule 2s 740ms

And Fill advice form 14s 610ms

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

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

And Go to "TRANSPORT_TABLE" 193ms

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

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

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

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

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

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

And Set advice window in schedule 2s 649ms

And Fill advice form 14s 610ms

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

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

And Go to "TRANSPORT_TABLE" 199ms

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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

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

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

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

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

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

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

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

Hooks

After Hooks.rollbackAddedActionAuthorities() 119ms

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

@deleteTransportAfterTest

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

Steps

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

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

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

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 574ms

And Fill advice form 8s 398ms

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

And Go to "TRANSPORT_TABLE" 250ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 576ms

And Fill advice form 8s 384ms

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

And Go to "TRANSPORT_TABLE" 207ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 573ms

And Fill advice form 8s 416ms

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

And Go to "TRANSPORT_TABLE" 226ms

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

When Add file to transport by API 474ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 570ms

And Fill advice form 8s 407ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

When Add file to transport by API 235ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 147ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

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

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

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

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

And Login as "hochland-admin" 2s 821ms

And Show all transport types 1s 063ms

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

And Set advice window in schedule 6s 450ms

And Fill advice form 11s 899ms

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

And Go to "TRANSPORT_TABLE" 185ms

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

And Confirm statuses until reach "during-load" 6s 590ms

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:127)

Hooks

After Hooks.rollbackCustomFieldSettings() 091ms

After Hooks.deleteTransportAfterTest() 123ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

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

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

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

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

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

And Show all transport types 1s 136ms

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

And Set advice window in schedule 2s 388ms

And Fill advice form 13s 267ms

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

And Go to "TRANSPORT_TABLE" 177ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:127)

Hooks

After Hooks.rollbackCustomFieldSettings() 048ms

After Hooks.deleteTransportAfterTest() 119ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

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

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

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

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

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

And Show all transport types 1s 067ms

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

And Set advice window in schedule 2s 473ms

And Fill advice form 13s 245ms

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

And Go to "TRANSPORT_TABLE" 208ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:127)

Hooks

After Hooks.rollbackCustomFieldSettings() 052ms

After Hooks.deleteTransportAfterTest() 105ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 052ms

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

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

And Go to "TRANSPORT_TABLE" 116ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:144)

Hooks

After Hooks.rollbackCustomFieldSettings() 045ms

After Hooks.deleteTransportAfterTest() 109ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 042ms

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

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

And Go to "TRANSPORT_TABLE" 109ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:144)

Hooks

After Hooks.rollbackCustomFieldSettings() 036ms

After Hooks.deleteTransportAfterTest() 153ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 023ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 140ms

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

And Login as "hochland-admin" 2s 401ms

And Go to "TRANSPORT_TABLE" 192ms

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

And Confirm statuses until reach "during-unload" 6s 531ms

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:144)

Hooks

After Hooks.rollbackCustomFieldSettings() 115ms

After Hooks.deleteTransportAfterTest() 108ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

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

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

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

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

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

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

And Show all transport types 1s 148ms

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

And Set advice window in schedule 2s 382ms

And Fill advice form 13s 247ms

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

And Go to "TRANSPORT_TABLE" 218ms

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

When Confirm statuses until reach "arrived" 3s 843ms

And Check if next status is not possible to confirm 106ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:167)

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

And Go to transport details "LOAD" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

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

And Go to transport details "LOAD" 000ms

And Open section: "advice-panel" 000ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 000ms

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 045ms

After Hooks.deleteTransportAfterTest() 104ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

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

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

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

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

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

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

And Show all transport types 1s 060ms

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

And Set advice window in schedule 2s 381ms

And Fill advice form 13s 167ms

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

And Go to "TRANSPORT_TABLE" 211ms

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

When Confirm statuses until reach "arrived" 3s 812ms

And Check if next status is not possible to confirm 107ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:167)

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

And Go to transport details "CONTAINER" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

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

And Go to transport details "CONTAINER" 000ms

And Open section: "advice-panel" 000ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 000ms

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 066ms

After Hooks.deleteTransportAfterTest() 103ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

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

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

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

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

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

And Login as "hochland-admin" 2s 357ms

And Show all transport types 1s 059ms

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

And Set advice window in schedule 6s 431ms

And Fill advice form 11s 865ms

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

And Go to "TRANSPORT_TABLE" 219ms

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

When Confirm statuses until reach "during-load" 7s 094ms

And Check if next status is not possible to confirm 103ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:167)

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 000ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill "warehouseman-(u)" in transport form 000ms

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 104ms

After Hooks.deleteTransportAfterTest() 096ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

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

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

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 040ms

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

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

And Go to "TRANSPORT_TABLE" 134ms

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

When Confirm statuses until reach "arrived" 3s 790ms

And Check if next status is not possible to confirm 097ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:195)

And Go to transport details "UNLOAD" 000ms

And Fill transport form 000ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 046ms

After Hooks.deleteTransportAfterTest() 093ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

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

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

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 048ms

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

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

And Go to "TRANSPORT_TABLE" 111ms

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

When Confirm statuses until reach "arrived" 3s 814ms

And Check if next status is not possible to confirm 106ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:195)

And Go to transport details "TANKER_GRANULATE_DELIVERY" 000ms

And Fill transport form 000ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 047ms

After Hooks.deleteTransportAfterTest() 095ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 023ms

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

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 117ms

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

And Login as "hochland-admin" 2s 222ms

And Go to "TRANSPORT_TABLE" 198ms

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

When Confirm statuses until reach "during-unload" 6s 550ms

And Check if next status is not possible to confirm 114ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:195)

And Go to transport details "DELIVERY" 000ms

And Fill transport form 000ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 103ms

After Hooks.deleteTransportAfterTest() 098ms

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

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

And Confirm status "REPORTING" by Public API "v1" 086ms

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

And Login as "swiss-krono-delivery-guard" 1s 574ms

And Go to "TRANSPORT_TABLE" 157ms

When Confirm "Departure" status in transport row 3s 081ms

Then Verify that "Departure" has been confirmed 038ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

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

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

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

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 045ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 15s 295ms

When Login as "keeeper-admin" 2s 004ms

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

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

And Go to transport details "UNLOAD" 4s 387ms

And Fill transport form 38s 007ms

Then Check if next status is not possible to confirm in transport details 067ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusInTransportDetailsIsNotPossibleToConfirm(ConfirmStatuses.java:119)
	at ✽.Check if next status is not possible to confirm in transport details(file:Features/Atom/Statuses/ConfirmStatuses.feature:236)

Hooks

After Hooks.rollbackCustomFieldSettings() 048ms

After Hooks.deleteTransportAfterTest() 099ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

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

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

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 045ms

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

When Login as "keeeper-admin" 1s 893ms

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

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

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

And Fill transport form 36s 369ms

Then Check if next status is not possible to confirm in transport details 069ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusInTransportDetailsIsNotPossibleToConfirm(ConfirmStatuses.java:119)
	at ✽.Check if next status is not possible to confirm in transport details(file:Features/Atom/Statuses/ConfirmStatuses.feature:236)

Hooks

After Hooks.rollbackCustomFieldSettings() 053ms

After Hooks.deleteTransportAfterTest() 097ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 023ms

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

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 104ms

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

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

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

And Confirm statuses until reach "during-unload" 6s 562ms

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

And Fill transport form 36s 054ms

Then Check if next status is not possible to confirm in transport details 067ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusInTransportDetailsIsNotPossibleToConfirm(ConfirmStatuses.java:119)
	at ✽.Check if next status is not possible to confirm in transport details(file:Features/Atom/Statuses/ConfirmStatuses.feature:236)

Hooks

After Hooks.rollbackCustomFieldSettings() 127ms

After Hooks.deleteTransportAfterTest() 083ms

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 454ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 208ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 693ms

And Login as "bausch-admin" 2s 103ms

And Go to "TRANSPORT_TABLE" 210ms

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

When Confirm statuses until reach "on-the-way" 9s 366ms

And Open statuses popup 066ms

And Toggle status date confirmation checkbox 287ms

And Confirm statuses until reach "process-ended" 18s 738ms

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

After Hooks.deleteModeOfTransportationAfterTest() 095ms

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 310ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 266ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 701ms

And Login as "bausch-admin" 1s 167ms

And Go to "TRANSPORT_TABLE" 214ms

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

When Confirm statuses until reach "on-the-way" 9s 305ms

And Open statuses popup 059ms

And Toggle status date confirmation checkbox 278ms

And Change status execution date to "1" days from today 2s 223ms

Then Verify that status cannot be confirmed 1s 100ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.deleteModeOfTransportationAfterTest() 069ms

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 279ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 228ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 728ms

And Login as "bausch-admin" 1s 103ms

And Go to "TRANSPORT_TABLE" 197ms

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

When Confirm statuses until reach "on-the-way" 9s 861ms

And Open statuses popup 071ms

And Toggle status date confirmation checkbox 271ms

And Change status execution date to "-1" days from today 2s 185ms

Then Verify that status cannot be confirmed 1s 088ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

After Hooks.deleteModeOfTransportationAfterTest() 099ms

@deleteAllTransportsAfterTest @deleteAllAddedStatus

Scenario Outline Check if statuses in new orders are created based on current status scheme [A-6867]

Steps

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

And Create task with new status by JSON file "NEW_STATUS_SMALLS_IMPORT" as "super-admin-skz" 167ms

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

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

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

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

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

And Set advice window in schedule 2s 675ms

And Fill advice form 14s 607ms

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

And If user is login then logout 120ms

And Login as "swisskrono-admin" 2s 498ms

And Show all transport types 1s 063ms

Then Check if transport has "testowy-różoffy-statusik" 028ms

And Go to "SETTINGS_TAB" 291ms

When Disable status "testowy-różoffy-statusik" for transport "SMALLS_IMPORT" 1s 616ms

And Delete created transport by API 154ms

Then If user is login then logout 079ms

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

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

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

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

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

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

And Set advice window in schedule 2s 724ms

And Fill advice form 14s 689ms

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

And If user is login then logout 129ms

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

And Show all transport types 1s 052ms

Then Check if transport has disabled status "testowy-różoffy-statusik" 15s 018ms

Hooks

After Hooks.deleteAllTransports() 1m 16s 352ms

After Hooks.deleteAllAddedStatus() 2s 248ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 652ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 024ms

When Login as "farmacol-admin" 2s 645ms

And Go to "TRANSPORT_TABLE" 150ms

And Confirm statuses until reach "during-unload" 9s 461ms

And Set actual confirmed transport status list 1s 378ms

And Disable task by API 048ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 458ms

And Edit transport hours and recalculate statuses 15s 789ms

Then Verify that all confirmed statuses are still on transport status list 189ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.rollbackTaskChanges() 039ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Status confirmation	389	15	45	0	0	449	22	15	37	28m 14s 499ms	Failed

Feature Report