Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.145	04 wrz 2021, 06:09

	Steps	Scenarios	Features
@rollbackSettings	132	1	3	0	0	136	14	1	15	6m 19s 729ms	Failed

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 270ms

And Set token of apiUsername "super-admin-piast" 244ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 107ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 228ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 710ms

Then Login as "super-admin-piast" 8s 835ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 544ms

After Hooks.rollbackSettings() 195ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 247ms

And Set token of apiUsername "super-admin-piast" 239ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 158ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 171ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 766ms

Then Login as "super-admin-piast" 2s 471ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 660ms

After Hooks.rollbackSettings() 123ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 239ms

And Set token of apiUsername "super-admin-piast" 236ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 163ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 120ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 733ms

Then Login as "super-admin-piast" 2s 537ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 654ms

After Hooks.rollbackSettings() 105ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 133ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 144ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 251ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 686ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 807ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 672ms

After Hooks.rollbackSettings() 149ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 374ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 143ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 257ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 647ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 885ms

Then Check if response status code equals "422" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 631ms

After Hooks.rollbackSettings() 136ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 145ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 242ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 699ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 369ms

Then Check if response status code equals "404" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 656ms

After Hooks.rollbackSettings() 158ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 244ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 235ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 682ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 028ms

Then Check if response status code equals "401" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 695ms

After Hooks.rollbackSettings() 123ms

View Feature API Transport

@deleteApiTransportsAfterTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api with non unique erpIdentifier [A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 135ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 665ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 664ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY_WITH_FILLED_ERP_IDENTIFIER" as "super-admin-piast" for api version "v1" by identifier "5345467712" 350ms

Then Check if response status code equals "422" 000ms

Hooks

After Hooks.deleteApiTransportsAfterTest() 1s 345ms

After Hooks.rollbackSettings() 097ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if custom fields map is correct after creating a transport by Public API [A-7508]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 271ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 130ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 256ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 685ms

And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 267ms

Hooks

After Hooks.deleteTransportAfterApiTest() 664ms

After Hooks.rollbackSettings() 134ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it possible to edit transport by API [A-4167]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 230ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 720ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 713ms

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

And Show all transport types 1s 178ms

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

And Set advice window in schedule 3s 888ms

And Fill advice form 13s 350ms

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

When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 645ms

And Check if response status code equals "200" 000ms

And Go to "TRANSPORT_TABLE" 511ms

And Go to transport details "DELIVERY" 3s 016ms

And Expand advice panel 744ms

Then Check are transport values equals 2s 386ms

Hooks

After Hooks.deleteTransportAfterApiTest() 827ms

After Hooks.rollbackSettings() 141ms

View Feature Filters

@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if sorting by "Finished" status is working correctly [A-7517]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 239ms

And Get custom field settings for "DELIVERY" transport type and "neuca" company 110ms

And Mark custom fields as not obligatory 006ms

And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 137ms

And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 130ms

When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 261ms

Then Login as "neuca-admin" 2s 401ms

And Go to "TRANSPORT_TABLE" 503ms

And Confirm statuses until reach "process-ended" 22s 516ms

Then Check if sorting by 'Finished' status is working correctly 302ms

Hooks

After Hooks.deleteTransportsAfterTest() 4s 451ms

After Hooks.rollbackAllCustomFieldsSettings() 365ms

After Hooks.rollbackSettings() 110ms

View Feature Invitation

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Delete invitations with email "automaty31415@test.pl" 089ms

And If user is login then logout 232ms

Given Set token of apiUsername "super-admin-piast" 290ms

And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 135ms

Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 197ms

And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 427ms

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

Then Go to "INVITATIONS_TAB" 508ms

And Go to "EXPIRED_TAB" invitation status tab 227ms

Then Invitation is displayed on list "automaty31415@test.pl" 430ms

Hooks

After Hooks.deleteInvitationAfterTest() 132ms

After Hooks.rollbackSettings() 126ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 133ms

And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 344ms

And Prepare setting for automatic time window delete with "super-admin-skz" 263ms

When Login as "swisskrono-admin" 7s 962ms

And Go to "WAREHOUSE_TAB" 918ms

Then Check if dedicated window is deleted from schedule 48s 353ms

Hooks

After Hooks.rollbackSettings() 197ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 7s 340ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 020ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 139ms

And Set proper delay time to move order to archive after task timeout 134ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 958ms

And Go to "WAREHOUSE_TAB" 1s 004ms

And Change warehouse in schedule to: "Katowice" 1s 306ms

And Wait "60" seconds 1m

And Verify that transport window is grey 088ms

Error message

java.lang.AssertionError: Okno zlecenia nie zrobiło się szare
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Warehouse.WarehouseTest.verifyThatTransportWindowIsGrey(WarehouseTest.java:118)
	at ✽.Verify that transport window is grey(file:Features/Atom/Transport/Archive.feature:13)

And Verify that transport is in archive 000ms

Then Restore transport from archive 000ms

And Verify that transport has been successfully restored 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 775ms

After Hooks.rollbackSettings() 133ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if confirming transport status removed it to the archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 218ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 130ms

And Mark custom fields as not obligatory 006ms

And Login as "dayco-admin" 2s 187ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 075ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 130ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 186ms

When Go to "TRANSPORT_TABLE" 398ms

And Click button advice in transport table "OWN_COLLECTION" 1s 285ms

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 613ms

And Go to "TRANSPORT_TABLE" 389ms

And Find transport in table with status "planned-magazyn-tychy" 3s 685ms

And Confirm statuses until reach "process-ended" 16s 689ms

And Wait until transport disappear from transport table 40s 392ms

Then Go to "ARCHIVE_TAB" 555ms

And Show "OWN_COLLECTION" 176ms

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

Hooks

After Hooks.deleteTransportAfterTest() 778ms

After Hooks.rollbackAllCustomFieldsSettings() 604ms

After Hooks.rollbackSettings() 119ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	132	1	3	0	0	136	14	1	15	6m 19s 729ms	Failed

Tag Report