Cucumber-JVM Reports - Feature: Status confirmation

Project	Number	Date
ApolloFullRunnerReport	develop.372	08 kwi 2021, 05:40

	Steps	Scenarios	Features
Status confirmation	389	15	45	0	0	449	22	15	37	29m 1s 945ms	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 502ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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

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

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

Then Check if transport has "departed" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

@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_DELIVERY" by JSON file as "super-admin-keeeper" 1s 340ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

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

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

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

And Set advice window in schedule 2s 744ms

And Fill advice form 14s 758ms

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

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

And Go to "TRANSPORT_TABLE" 211ms

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

Hooks

After Hooks.deleteTransportAfterTest() 157ms

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

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

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

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

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

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

And Set advice window in schedule 2s 655ms

And Fill advice form 14s 678ms

And Click advice save button and wait for advice form to disappear 34s 971ms

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

And Go to "TRANSPORT_TABLE" 188ms

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

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

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

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

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

Hooks

After Hooks.rollbackAddedActionAuthorities() 065ms

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

And Show all transport types 1s 028ms

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

And Set advice window in schedule 2s 555ms

And Fill advice form 8s 398ms

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

And Go to "TRANSPORT_TABLE" 228ms

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

And Confirm statuses until reach "left-the-area" 21s 541ms

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

Hooks

After Hooks.deleteTransportAfterTest() 212ms

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

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

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

And Show all transport types 1s 051ms

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

And Set advice window in schedule 2s 621ms

And Fill advice form 8s 444ms

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

And Go to "TRANSPORT_TABLE" 223ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 509ms

And Fill advice form 8s 449ms

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

And Go to "TRANSPORT_TABLE" 242ms

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

When Add file to transport by API 662ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 192ms

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 534ms

And Fill advice form 8s 412ms

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

And Go to "TRANSPORT_TABLE" 183ms

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

When Add file to transport by API 316ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

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

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

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

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

And Show all transport types 1s 067ms

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

And Set advice window in schedule 6s 456ms

And Fill advice form 11s 934ms

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

And Go to "TRANSPORT_TABLE" 202ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 066ms

After Hooks.deleteTransportAfterTest() 103ms

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

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

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

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

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

And Login as "keeeper-admin" 5s 872ms

And Show all transport types 1s 137ms

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

And Set advice window in schedule 2s 446ms

And Fill advice form 13s 263ms

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

And Go to "TRANSPORT_TABLE" 172ms

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

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

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

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

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

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

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

And Show all transport types 1s 068ms

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

And Set advice window in schedule 2s 439ms

And Fill advice form 13s 213ms

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

And Go to "TRANSPORT_TABLE" 204ms

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

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

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

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 133ms

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

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

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

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

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 107ms

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

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

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

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-hochland" 092ms

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

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

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

And Login as "hochland-admin" 6s 003ms

And Go to "TRANSPORT_TABLE" 197ms

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

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

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

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

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

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

And Show all transport types 1s 121ms

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

And Set advice window in schedule 2s 422ms

And Fill advice form 13s 230ms

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

And Go to "TRANSPORT_TABLE" 179ms

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

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

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

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

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

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

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

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

And Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 381ms

And Fill advice form 13s 236ms

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

And Go to "TRANSPORT_TABLE" 200ms

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

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

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

After Hooks.deleteTransportAfterTest() 094ms

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

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

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

And Login as "hochland-admin" 6s 342ms

And Show all transport types 1s 068ms

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

And Set advice window in schedule 6s 506ms

And Fill advice form 11s 895ms

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

And Go to "TRANSPORT_TABLE" 216ms

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

When Confirm statuses until reach "during-load" 6s 606ms

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

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

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 136ms

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

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

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: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() 048ms

After Hooks.deleteTransportAfterTest() 098ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 104ms

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

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

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

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 184ms

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

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

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

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

After Hooks.deleteTransportAfterTest() 164ms

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

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

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

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

And Login as "swiss-krono-delivery-guard" 5s 640ms

And Go to "TRANSPORT_TABLE" 201ms

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

Then Verify that "Departure" has been confirmed 034ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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

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

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

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

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

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

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

And Fill transport form 37s 939ms

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

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

After Hooks.deleteTransportAfterTest() 113ms

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

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

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

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

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

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

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

And Fill transport form 36s 468ms

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

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

After Hooks.deleteTransportAfterTest() 108ms

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

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

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

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

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

And Confirm statuses until reach "during-unload" 7s 547ms

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

And Fill transport form 36s 020ms

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

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

After Hooks.deleteTransportAfterTest() 082ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 200ms

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

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

And Open statuses popup 063ms

And Toggle status date confirmation checkbox 293ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

After Hooks.deleteModeOfTransportationAfterTest() 098ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 222ms

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

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

And Open statuses popup 048ms

And Toggle status date confirmation checkbox 275ms

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

Then Verify that status cannot be confirmed 1s 091ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.deleteModeOfTransportationAfterTest() 076ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 218ms

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

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

And Open statuses popup 052ms

And Toggle status date confirmation checkbox 265ms

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

Then Verify that status cannot be confirmed 1s 087ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.deleteModeOfTransportationAfterTest() 079ms

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

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

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

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

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

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

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

And Set advice window in schedule 2s 762ms

And Fill advice form 14s 667ms

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

And If user is login then logout 113ms

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

And Show all transport types 1s 068ms

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

And Go to "SETTINGS_TAB" 295ms

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

And Delete created transport by API 183ms

Then If user is login then logout 338ms

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

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

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

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

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

And Set advice window in schedule 2s 707ms

And Fill advice form 14s 723ms

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

And If user is login then logout 107ms

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

And Show all transport types 1s 057ms

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

Hooks

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

After Hooks.deleteAllAddedStatus() 2s 244ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 1s 030ms

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

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

And Go to "TRANSPORT_TABLE" 209ms

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

And Set actual confirmed transport status list 1s 371ms

And Disable task by API 2s 984ms

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

And Edit transport hours and recalculate statuses 16s 335ms

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

Hooks

After Hooks.deleteTransportAfterTest() 177ms

After Hooks.rollbackTaskChanges() 044ms

	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	29m 1s 945ms	Failed

Feature Report