[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2024-11-26 (世界標準時間)。"],[[["After implementing Checkout and Order submit actions for your Ordering End-to-End fulfillment API, thorough testing is crucial to ensure both flows function correctly."],["Before testing, ensure you have the necessary GCP project access, a valid data feed uploaded, updated API code with Checkout and Order submit actions, and a publicly accessible fulfillment URL endpoint."],["You can test your fulfillment API using either automated integration tests (recommended) or manual quick testing within the Actions Center."],["The automated testing tool offers a streamlined approach with faster results and broader coverage, while the quick testing tool allows for manual walkthroughs of the user ordering flow."],["Utilize additional resources like Chrome DevTools Console and Stackdriver logs for in-depth troubleshooting and analysis during the testing process."]]],["After setting up \"Checkout\" and \"Order submit\" in your fulfillment API, prepare for testing by ensuring GCP project access, uploading a valid data feed with restaurant, service, and menu entities, updating the API with the relevant actions code, and making your fulfillment URL publicly accessible. Test via the Actions Center's automated integration tests or quick testing, using your data feed. Automated testing is faster but limited to certain payment methods. Manual testing is also available. Monitor and analyze test results for at least a 95% success rate.\n"]]