As it stands, testing receiving trip request responses and handling client order confirmations relies on manual data entry on the developer's part--valid JSON data for the various responses must be created, that corresponds to actual rows in the RideSheet.
Create an API_tests.gs that: creates multiple shared trips at a future date, either in trips or outside trips, and runs the tests on that data, then cleans it up and deletes it afterward.
As it stands, testing receiving trip request responses and handling client order confirmations relies on manual data entry on the developer's part--valid JSON data for the various responses must be created, that corresponds to actual rows in the RideSheet.