Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.142	02 wrz 2021, 20:16

	Steps	Scenarios	Features
@rollbackSettings	136	0	0	0	0	136	15	0	15	6m 40s 784ms	Passed

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 581ms

After Hooks.rollbackSettings() 175ms

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) 002ms

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 665ms

After Hooks.rollbackSettings() 138ms

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) 002ms

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 643ms

After Hooks.rollbackSettings() 103ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 668ms

After Hooks.rollbackSettings() 137ms

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) 002ms

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 646ms

After Hooks.rollbackSettings() 130ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 622ms

After Hooks.rollbackSettings() 150ms

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) 002ms

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 663ms

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) 002ms

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteApiTransportsAfterTest() 1s 297ms

After Hooks.rollbackSettings() 093ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 713ms

After Hooks.rollbackSettings() 137ms

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

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

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

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 475ms

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

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

And Show all transport types 1s 161ms

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

And Set advice window in schedule 4s 004ms

And Fill advice form 13s 349ms

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

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

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

And Go to "TRANSPORT_TABLE" 515ms

And Go to transport details "DELIVERY" 2s 975ms

And Expand advice panel 489ms

Then Check are transport values equals 2s 355ms

Hooks

After Hooks.deleteTransportAfterApiTest() 865ms

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

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

And Mark custom fields as not obligatory 007ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 638ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 4s 605ms

After Hooks.rollbackAllCustomFieldsSettings() 343ms

After Hooks.rollbackSettings() 107ms

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

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

And If user is login then logout 240ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 567ms

And Go to "EXPIRED_TAB" invitation status tab 333ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 149ms

After Hooks.rollbackSettings() 131ms

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

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

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

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

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

And Go to "WAREHOUSE_TAB" 914ms

Then Check if dedicated window is deleted from schedule 54s 639ms

Hooks

After Hooks.rollbackSettings() 185ms

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" 8s 803ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 970ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 082ms

And Verify that transport is in archive 7s 610ms

Then Restore transport from archive 2s 739ms

And Verify that transport has been successfully restored 1s 779ms

Hooks

After Hooks.deleteTransportAfterTest() 772ms

After Hooks.rollbackSettings() 125ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 393ms

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

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

And Go to "TRANSPORT_TABLE" 402ms

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

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

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

Then Go to "ARCHIVE_TAB" 533ms

And Show "OWN_COLLECTION" 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 775ms

After Hooks.rollbackAllCustomFieldsSettings() 542ms

After Hooks.rollbackSettings() 130ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	136	0	0	0	0	136	15	0	15	6m 40s 784ms	Passed

Tag Report