31 lines
980 B
Markdown
31 lines
980 B
Markdown
# 10 Sandbox Testing
|
|
|
|
Checklist:
|
|
|
|
- Create a dedicated TESTING app in Uber Developer Dashboard
|
|
- Use sandbox domains in `.env`:
|
|
- `UBER_OAUTH_BASE_URL=https://sandbox-login.uber.com`
|
|
- `UBER_API_BASE_URL=https://test-api.uber.com`
|
|
- Ensure domain pairing is valid:
|
|
- Testing: `sandbox-login.uber.com -> test-api.uber.com`
|
|
- Production: `auth.uber.com -> api.uber.com`
|
|
- Test OAuth connect flow
|
|
- Test menu upload/get
|
|
- Test order lifecycle actions
|
|
- Test webhook receipt and persistence
|
|
- Validate retry and duplicate event handling
|
|
|
|
Validation sequence:
|
|
|
|
1. Authentication token generation and authorized call test
|
|
2. Store status/hours API smoke tests
|
|
3. Full menu replacement test via PUT
|
|
4. Order webhook receipt and lifecycle action tests
|
|
5. Error and retry behavior checks
|
|
|
|
Troubleshooting quick checks:
|
|
|
|
- Verify test credentials belong to TESTING app type
|
|
- Token/API domain mismatch is the most common failure
|
|
- Sandbox data can reset; do not rely on persistence
|