制定移动应用发布测试清单
围绕本次版本变更和风险生成分级测试清单,覆盖升级、权限、弱网、设备兼容与发布监控。
完整提示词
<context>
A mobile release cannot be rolled back like a web deploy: users keep old versions for months, store review adds days to a hotfix, and a crash on launch after an update hits every user who auto-updates. The defects that escape are rarely in the new feature's happy path. They come from upgrading over an older version with existing local data and logged-in sessions, permission prompts denied or revoked, the app being backgrounded or killed mid-flow (calls, notifications, low memory, process death on Android), poor or no connectivity, small screens, large text and dark mode, the oldest supported OS, and store requirements such as privacy declarations, required SDK targets and account deletion. A useful checklist is specific to this release's changes and risks, and ordered so the most important checks happen if time runs short.
</context>
<task>
Write a release test checklist for:
{{app}}
{{#risk_areas}}
Risk areas: {{risk_areas}}
{{/risk_areas}}
{{#time_available}}
Time available: {{time_available}}
{{/time_available}}
1. Start with release-specific checks derived from what changed: the new or changed flows, their edge states (empty, error, loading, long content), and anything touching data models, authentication, payments or push notifications.
2. Upgrade and data: install the previous store version, use it to create data and stay signed in, then upgrade to the release build. Check migrations of local storage, preserved sessions, settings and cached content, and a fresh install. Include a forced-update or minimum-version path if the app has one.
3. Permissions and privacy: first-run prompts, denial, later revocation in system settings, limited or approximate grants where the OS offers them, and that the app explains and recovers. Check that new data collection or SDKs are reflected in the store privacy declarations.
4. Interruptions and lifecycle: background and resume mid-flow, incoming call or notification, screen rotation where supported, low memory or process death (Android "don't keep activities"), and returning from a deep link or push into the right screen.
5. Network and offline: offline at launch, connection lost mid-request, slow network, retries without duplicate submissions, and behaviour when the backend returns errors.
6. Devices and OS: the oldest and newest supported OS, a small and a large screen, tablet if supported, large text or font scaling, dark mode, a screen reader pass on the changed flows, and right-to-left if localised.
7. Store submission: version and build numbers, release notes, screenshots if UI changed, target SDK or minimum OS rules, privacy and account deletion requirements, and review notes with a demo account if sign-in is needed.
8. Post-release: phased rollout settings, crash and ANR monitoring thresholds that pause the rollout, and who watches the first hours.
9. Mark each item P1 (must do), P2 or P3, and if time is limited, say which P1 items fit.
</task>
<constraints>
- Tailor the list to the stated release; do not pad with checks irrelevant to its platforms or features.
- Do not state current store policy details as fact unless given; phrase them as checks against the current store guidelines.
- Do not invent supported OS versions or device names; use the ones given or placeholders.
</constraints>
<output_format>
One section per heading in the output contract, each a checklist of "- [ ] P1 ..." items with the expected result in a few words. End with a short "If time runs short" list under Post-release.
</output_format>可替换内容
- {{app}}
- {{#risk_areas}}
- {{risk_areas}}
- {{/risk_areas}}
- {{#time_available}}
- {{time_available}}
- {{/time_available}}
- [ ]
分类与标签
编程开发、移动应用测试、版本发布、升级验证、弱网测试、测试优先级