System Integration Testing Process

System Integration Testing (SIT) is to make sure that the intercommunication between your system and the Deliveries PH platform works seamlessly.

SIT Steps:

Set up the logo (optional) and email (required) – where you want to receive partner invitations, by going to Settings → App Settings.
Set up the ‘Business Hours’ and ‘Capacity’ in your Deliveries PH account by going to Settings → Business Hours & Capacity. (optional)
Note that there is no need to fill out the capacity field as you can leave it blank.
Go to Settings → My Partners to see the list of providers. You can choose who you want to be partnered with by clicking the ‘Invite’ button. Once your invites have been accepted by the providers, they will be tagged as your ‘Preferred Partners’.
For our SIT, you need to send invites to the following providers (these are our test accounts):
- SANDBOX_ONDEMAND_PROVIDER
- SANDBOX_PROVIDER
Once done with steps 1 – 3, let us know immediately. We will be accepting the partner invites you sent. Again, once accepted, our test accounts will be tagged as two of your ‘Preferred Partners’.
Next, 24 posts (basic scenarios) should be created to cover the test scenarios displayed below.
All of these posts should be assigned to the provider SANDBOX_ONDEMAND_PROVIDER for On-demand and SANDBOX_PROVIDER for Scheduled.

Post creation type:

Post creation type:

Through SHOPIFY

Once checked out, access your Deliveries PH account and check if the details of the post you’ve created through Shopify are correct.

Through API

Once created, access your Deliveries PH account and check if the details of the post you’ve created through your system are correct.

Notes: Partners displayed in your getPartners API are your preferred partners in your Deliveries PH web account (which can be found in the Web App → Settings → My Partners).

If there are no partners displayed, you must first send invites to providers you wished to be partnered with. Once invites are accepted by the providers, they will be tagged as your ‘Preferred Partners’.

Through WEB (Manual Encoding/Import)

Once created, access your Deliveries PH account and check if the details of the post you’ve created through manual encoding or ‘Import Posts’ are correct.

You can always review post details in Step 6 – Post Summary, when creating posts through manual encoding or when finalizing posts in the ‘Drafts’ menu.

Our automated tool will be the one to update the status of the post/s created based on the scenarios displayed below. With this, you will be checking if our status updates are aligned on your end.

Test Scenarios:

Our Deliveries PH SIT tool will act as your partner provider and all statuses will be auto-updated to it’s expected status upon post creation. Please check if all status updates are aligned on your end.

Note: In order for you to choose a scenario, you MUST FILL IN the scenario code in one of the following Deliveries PH’s fields (in order of priority): Reference number, Pickup remarks, Delivery remarks, Sender name and Recipient name per scenario. Example: • SIT-001 • SIT002 • SIT-003-lorem • Mark Doe SIT-001

Scenario code	Scenario	Status Flow
SIT-001	Scenario 1: ACCEPT then CANCEL	FROM ACCEPTED Update to CANCELLED
SIT-002	Scenario 2: ASSIGNING_RIDER	FROM ACCEPTED Update to ASSIGNING RIDER
SIT-003	Scenario 3: START_PICKUP	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP
SIT-004	Scenario 4: DONE_PICKUP	FROM ACCEPTED Update to ASSIGNING RIDER Update to START_PICKUP Update to DONE_PICKUP
SIT-005	Scenario 5: START_DELIVERY	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to DONE PICKUP Update to STARTED DELIVERY
SIT-006	Scenario 6: START_DELIVERY then CANCEL	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to DONE PICKUP Update to STARTED DELIVERY Update to CANCEL (Expectation: should have an error and should proceed on the next scenario)
SIT-007	Scenario 7: DONE	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to DONE PICKUP Update to STARTED DELIVERY Update to DONE
SIT-008	Scenario 8: FAILED_PICKUP	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to FAILED PICKUP
SIT-009	Scenario 9: FAILED_DELIVERY	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to DONE PICKUP Update to STARTED DELIVERY Update to FAILED DELIVERY
SIT-010	Scenario 10: IN_TRANSIT_FOR_RETURN	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to FAILED PICKUP Update to STARTED PICKUP Update to DONE PICKUP Update to STARTED DELIVERY Update to FAILED DELIVERY Update to IN TRANSIT FOR RETURN
SIT-011	Scenario 11: RETURNED	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to FAILED PICKUP Update to STARTED PICKUP Update to DONE PICKUP Update to STARTED DELIVERY Update to FAILED DELIVERY Update to IN TRANSIT FOR RETURN Update to RETURNED
SIT-012	Scenario 12: FAILED RETURN	FROM ACCEPTED Update to ASSIGNING RIDER Update to STARTED PICKUP Update to FAILED PICKUP Update to STARTED PICKUP Update to DONE PICKUP Update to STARTED DELIVERY Update to FAILED DELIVERY Update to IN TRANSIT FOR RETURN Update to FAILED RETURNED

Note: In order for you to choose a scenario, you MUST FILL IN the scenario code in one of the following Deliveries PH’s fields (in order of priority): Reference number, Pickup remarks, Delivery remarks, Sender name and Recipient name per scenario. Example: • SIT-001 • SIT002 • SIT-003-lorem • Mark Doe SIT-001

Scenario Code	Scenario	Status Flow
SIT-001	Scenario 1: ACCEPT then CANCEL	FROM ACCEPTED Update to CANCELLED
SIT-002	Scenario 2: START_PICKUP	FROM ACCEPTED Update to STARTED PICKUP
SIT-003	Scenario 3: DONE_PICKUP	FROM ACCEPTED Update to START_PICKUP Update to DONE_PICKUP
SIT-004	SCENARIO 4: ARRIVED_AT_HUB	FROM ACCEPTED Update to START_PICKUP Update to DONE_PICKUP Update to ARRIVED_AT_HUB
SIT-005	Scenario 5: START_DELIVERY	FROM ACCEPTED Update to STARTED PICKUP Update to DONE PICKUP Update to ARRIVED AT HUB Update to STARTED DELIVERY
SIT-006	Scenario 6: START_DELIVERY then CANCEL	FROM ACCEPTED Update to STARTED PICKUP Update to DONE PICKUP Update to ARRIVED AT HUB Update to STARTED DELIVERY Update to CANCEL (Expectation: Should have an error upon CANCEL status update)
SIT-007	Scenario 7: DONE	FROM ACCEPTED Update to STARTED PICKUP Update to DONE PICKUP Update to ARRIVED AT HUB Update to STARTED DELIVERY Update to DONE
SIT-008	Scenario 8: FAILED_PICKUP	FROM ACCEPTED Update to STARTED PICKUP Update to FAILED PICKUP
SIT-009	Scenario 9: FAILED_DELIVERY	FROM ACCEPTED Update to STARTED PICKUP Update to DONE PICKUP Update to ARRIVED AT HUB Update to STARTED DELIVERY Update to FAILED DELIVERY
SIT-010	Scenario 10: IN_TRANSIT_FOR_RETURN	FROM ACCEPTED Update to STARTED PICKUP Update to FAILED PICKUP Update to STARTED PICKUP Update to DONE PICKUP Update to ARRIVED AT HUB Update to STARTED DELIVERY Update to FAILED DELIVERY Update to IN TRANSIT FOR RETURN
SIT-011	Scenario 11: RETURNED	FROM ACCEPTED Update to STARTED PICKUP Update to FAILED PICKUP Update to STARTED PICKUP Update to DONE PICKUP Update to ARRIVED AT HUB Update to STARTED DELIVERY Update to FAILED DELIVERY Update to IN TRANSIT FOR RETURN Update to RETURNED
SIT-012	Scenario 12: FAILED RETURN	FROM ACCEPTED Update to STARTED PICKUP Update to FAILED PICKUP Update to STARTED PICKUP Update to DONE PICKUP Update to ARRIVED AT HUB Update to STARTED DELIVERY Update to FAILED DELIVERY Update to IN TRANSIT FOR RETURN Update to FAILED RETURNED

Test scenarios provided/listed above are the basic scenarios to be covered for our SIT. Please do take note that the update per status for Basic Scenarios (Ondemand & Scheduled) has a 1 minute interval.

Below are the additional scenarios for both service type (Ondemand & Scheduled) of all providers that have a metafield. (e.g If preferred partner provider has additional details/meta fields → additional test scenario/s).
Note: For the additional scenarios, you may skip the scenario of a provider that you don’t prefer to be partnered with yet.

Note: No scenario code needed to be placed on Deliveries PH’s fields. All posts should automatically be updated up to it’s expected status

Scenario	Status Flow

Scenario	Status Flow
Scenario 1: Create a post and assign it to LALAMOVE	Update to ACCEPTED
Scenario 2: Create a post and assign it to MRSPEEDY	Update to ACCEPTED
Scenario 3: Create a post and assign it to TRANSPORTIFY	Update to ACCEPTED
Scenario 4: Create a post and assign it to GRAB	Update to ACCEPTED

Note: No scenario code needed to be placed on Deliveries PH’s fields. All posts should automatically be updated up to it’s expected status

Scenario	Status Flow

Scenario	Status Flow
Scenario 1: Create a post and assign it to QUADX	Update to ACCEPTED
Scenario 2: Create a post and assign it to NINJAVAN	Update to ACCEPTED
Scenario 3: Create a post and assign it to XDE	Update to ACCEPTED

If you’re already ready to perform the SIT, kindly inform our Customer Success Specialist and make sure to make a copy on your end/download the SIT form (https://docs.google.com/spreadsheets/d/1yh7LHKx5IBukHTSAbHOKrX_L3l6-4u72aqpduA9-UJc/edit#gid=900019135). || The cells with yellow and blue color fill are for your action.

Note: Please check if the HTTP Notification Configuration and/or Notification Triggers on your end were successfully executed during SIT.

Please make sure to share/provide a copy of your duly accomplished SIT form to our Customer Success Specialist once done.