[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:mobile-app-cross-region-large-file-upload-testing":3,"blog-article:\u002Fblog\u002Fmobile-app-cross-region-large-file-upload-testing":584,"blog-related:\u002Fblog\u002Fmobile-app-cross-region-large-file-upload-testing":585,"blog-translations:\u002Fblog\u002Fmobile-app-cross-region-large-file-upload-testing":586},{"available":4,"article":5,"relatedArticles":125,"translations":508},true,{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":18,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":23,"bodyHtml":124},"strapi",3794,"emb3kuqwrn6m64fp9iffivs0","zh","mobile-app-cross-region-large-file-upload-testing","\u002Fblog\u002Fmobile-app-cross-region-large-file-upload-testing","App 大文件上传：断点续传与完整性测试","移动 App 跨地区上传出现失败时，如何区分网络中断、续传行为与文件完整性问题？本文介绍合成样本、恢复条件、哈希核验和服务端分片检查。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_app_cover_1e29cdb614.webp","2026-10-28T02:00:34.509Z","2026-10-28T02:00:34.488Z","Global Proxies Team",[],false,0,1,"blocks",[24,30,34,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"大文件上传出问题，第一件事是分清三种失败：文件没传完、传完但内容损坏、传完但服务端没收到完整对象。三种用的证据完全不同——字节进度、校验和、服务端分片记录——混在一起记，就会把产品缺陷记成网络抖动。","text",{"type":25,"children":31},[32],{"text":33,"type":29},"测试自有 App 上传时，先用固定内容的合成文件建立基线，再按产品支持的方式制造网络中断。地区出口用于观察链路差异，不能代替上传完整性检查；本文聚焦自有 App 与存储服务。",{"type":35,"level":36,"children":37},"heading",2,[38],{"text":39,"type":29},"准备可重复的上传样本",{"type":25,"children":41},[42],{"text":43,"type":29},"准备几种大小的合成文件，使用可重复生成的内容，并在上传前计算哈希。样本大小应覆盖产品实际支持的路径；是否分片由产品实现决定，不预设所有大文件都必须分片。文件名可带用例编号，便于查找服务端对象。",{"type":25,"children":45},[46],{"text":47,"type":29},"不要用真实用户文件。先在基准网络下确认样本可正常上传，再比较其他网络条件。",{"type":35,"level":36,"children":49},[50],{"text":51,"type":29},"检查中断后的恢复行为",{"type":25,"children":53},[54],{"text":55,"type":29},"飞行模式可直接切断网络；切后台和锁屏则不保证中断上传，有些系统会继续执行任务。记录设备实际状态、任务是否暂停，以及恢复从何处继续。预期应以产品对后台传输和续传的承诺为准：承诺续传却无法恢复，才按相应契约判断；没有续传承诺时，从头重传本身不一定是缺陷。最终核对文件大小、源文件与目标文件哈希，以及产品使用分片时的分片清单。",{"type":25,"children":57},[58],{"text":59,"type":29},"若上传超时，记录发生阶段和网络条件，再在其他条件不变时复测。换出口可帮助判断现象是否随网络条件变化，但不能单独确定根因。",{"type":35,"level":36,"children":61},[62],{"text":63,"type":29},"校验完整性：哈希、分片与重复",{"type":25,"children":65},[66],{"text":67,"type":29},"上传完成后核对源文件与服务端对象的大小、哈希；使用分片时再检查分片内容、序号和合并清单。若结果不一致，结合客户端和服务端记录定位，不能仅凭哈希差异断定责任环节。",{"type":25,"children":69},[70],{"text":71,"type":29},"界面显示成功不等于服务端对象完整。记录校验结果和服务端确认状态，区分内容损坏与对象不完整。",{"type":35,"level":36,"children":73},[74],{"text":75,"type":29},"检查失败清理与重试",{"type":25,"children":77},[78],{"text":79,"type":29},"还要检查失败清理和重试：临时文件及未完成分片是否按策略过期，重试是否有上限与退避，避免反复失败造成存储、流量或电量异常。",{"type":25,"children":81},[82],{"text":83,"type":29},"记录这些条件和观察结果，才便于比较不同网络下的表现。",{"type":25,"children":85},[86],{"text":87,"type":29},"每轮记录文件大小、网络条件、中断时的系统状态、恢复位置、哈希和适用的分片证据。验收依据是产品对续传、完整性和重复提交的约定。",{"type":35,"level":36,"children":89},[90],{"text":91,"type":29},"常见问题",{"type":25,"children":93},[94],{"text":95,"type":29},"**能用真实用户文件做测试吗？**",{"type":25,"children":97},[98],{"text":99,"type":29},"优先使用合成文件，便于重复生成和核对哈希，也可避免暴露用户内容。确需使用真实文件时，应先取得授权并做好脱敏。",{"type":25,"children":101},[102],{"text":103,"type":29},"**上传显示成功，但服务端文件损坏，怎么判断？**",{"type":25,"children":105},[106],{"text":107,"type":29},"先比对源文件与目标对象的哈希，再查看分片内容、合并清单及服务端日志。把异常记录下来后，再根据各阶段证据定位。同一上传会话的重试与新建上传要分开判断；清理策略不能删除仍有效续传所需的数据。",{"type":25,"children":109},[110],{"text":111,"type":29},"**断点续传和分片上传是一回事吗？**",{"type":25,"children":113},[114],{"text":115,"type":29},"不是。续传靠服务端记录已接收的偏移量，分片是传输方式；两者常一起用，但可以单独成立，验收时要分别检查。",{"type":25,"children":117},[118],{"text":119,"type":29},"**换地区一定要用代理 IP 吗？**",{"type":25,"children":121},[122],{"text":123,"type":29},"不一定。测试上传逻辑可用本地弱网条件；比较地区链路则需一个可确认的目标地区出口，可以是代理或目标地区测试机。","",[126,246,412],{"source":6,"id":127,"documentId":128,"translationKey":128,"locale":9,"slug":129,"path":130,"_path":130,"title":131,"description":132,"excerpt":132,"image":133,"publishedAt":134,"updatedAt":135,"author":17,"tags":136,"featured":19,"sortOrder":20,"readingTime":36,"bodyType":22,"bodyBlocks":137,"bodyHtml":124},3797,"lw08jq304om4xm0qdbam6996","mobile-app-network-egress-compatibility-testing","\u002Fblog\u002Fmobile-app-network-egress-compatibility-testing","移动 App 网络兼容测试：五个失败阶段定位法","同一个 App 构建，直连正常、换到某地区出口就失败，问题可能落在域名解析、连接建立、证书校验、鉴权或超时任一环。按阶段记录域名、信号和错误码，才能分清兼容缺陷与出口质量。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_app_cover_bab910e122.webp","2026-10-28T02:01:27.065Z","2026-10-28T02:01:27.051Z",[],[138,142,146,150,154,158,162,166,171,175,179,183,187,191,195,199,203,207,211,214,218,222,226,230,234,238,242],{"type":25,"children":139},[140],{"text":141,"type":29},"同一个 App 构建，直连时正常，换到某个地区的出口就失败，这种问题最容易被一句\"网络差\"带过去。实际上失败点可能落在五处：域名没解析出来、TCP 连接没建立、TLS 握手被拒、鉴权请求被拦、或者响应超时。",{"type":25,"children":143},[144],{"text":145,"type":29},"对自有或明确授权的 App，先固定构建与设备，再列出实际请求域名。代理出口用于控制请求发起地区，不会替代真实用户网络或服务端数据。",{"type":35,"level":36,"children":147},[148],{"text":149,"type":29},"先把 App 请求的域名列全",{"type":25,"children":151},[152],{"text":153,"type":29},"列出首屏接口、图片 CDN 和第三方 SDK 等实际请求域名，并标明哪些影响核心功能、哪些可以降级。这样可避免主接口正常、某个 SDK 不可达却被误判为整条链路正常。",{"type":25,"children":155},[156],{"text":157,"type":29},"以域名清单作为测试范围，逐项记录请求阶段和结果。",{"type":35,"level":36,"children":159},[160],{"text":161,"type":29},"按请求阶段记录失败",{"type":25,"children":163},[164],{"text":165,"type":29},"请求阶段不同，检查方式也不同：",{"type":167,"children":168},"code",[169],{"text":170,"type":29},"| 阶段 | 可观测信号 | 记录方式 |\n| --- | --- | --- |\n| 域名解析 | NXDOMAIN、解析超时、返回地址与预期不符等 | 记录错误码、解析器、返回地址与耗时；内网地址也可能是合法配置 |\n| TCP 连接 | SYN 无响应、建连超时 | 记录目标端口与建连耗时，区分本地到代理、代理到目标及服务端监听\u002F路由 |\n| TLS 握手 | 证书校验失败、握手重置或超时 | 记录证书链、服务身份、系统时间与握手日志；单一信号不定根因 |\n| 鉴权\u002F拒绝 | 返回 401 或 403 | 识别响应来自目标站、WAF 还是中间层，并记录错误码与响应特征 |\n| 超时 | 解析、建连、TLS 或传输阶段超时 | 记录失败阶段与耗时分布；重复结果用于确认现象，不单独证明根因 |",{"type":25,"children":172},[173],{"text":174,"type":29},"单一信号可能对应多种原因。例如解析失败可能来自解析策略或目标站可达性；TLS 失败可能与客户端校验或链路有关。先记录信号，再结合对照组定位。",{"type":25,"children":176},[177],{"text":178,"type":29},"记录请求停在哪个阶段，以及错误码和耗时。再用相同构建与请求条件比较直连和地区出口；差异只说明相关性，仍需结合服务端或供应商证据。",{"type":35,"level":36,"children":180},[181],{"text":182,"type":29},"对照直连与地区出口",{"type":25,"children":184},[185],{"text":186,"type":29},"对照时固定构建、设备、系统、语言、账号和请求参数，只改变出口。重复运行以观察结果是否稳定，并记录执行时段。",{"type":25,"children":188},[189],{"text":190,"type":29},"记录时间戳、出口地区和实际检测结果。先确认直连基线稳定；否则加入地区出口后难以区分问题来源。",{"type":35,"level":36,"children":192},[193],{"text":194,"type":29},"判断出口相关性与待查项",{"type":25,"children":196},[197],{"text":198,"type":29},"多次结果可帮助判断现象是否稳定，但单一出口失败只能说明与该出口条件相关。要判断责任层，还需补同地区其他出口、不同时间和服务端证据。",{"type":25,"children":200},[201],{"text":202,"type":29},"TLS 失败可能涉及证书链、系统时间、目标站策略或中间链路；多个出口结果随机波动也不能单凭现象确定为网络质量问题。应保留证据继续核对。",{"type":25,"children":204},[205],{"text":206,"type":29},"工单写清已验证的条件、失败阶段和仍缺的证据；证据不足时标为“待确认”，再决定由客户端、服务端或网络人员继续排查。",{"type":25,"children":208},[209],{"text":210,"type":29},"记录时可用简表列出请求域名、失败阶段、直连与地区出口的实际结果、错误码\u002F耗时及仍缺的证据。示例域名和结果不代表真实测试数据。",{"type":35,"level":36,"children":212},[213],{"text":91,"type":29},{"type":25,"children":215},[216],{"text":217,"type":29},"**Android 和 iOS 的网络栈差异会影响结论吗？**",{"type":25,"children":219},[220],{"text":221,"type":29},"会。两端的解析、连接复用和证书校验实现可能不同，应分别执行相同用例。",{"type":25,"children":223},[224],{"text":225,"type":29},"**DNS 解析失败和连接超时怎么区分？**",{"type":25,"children":227},[228],{"text":229,"type":29},"DNS 失败要核对错误码、解析器和策略；TCP 超时还要区分本地到代理、代理到目标及服务端监听\u002F路由。TLS 失败需核证书链、服务身份、系统时间与握手日志；401\u002F403 要识别由目标、WAF 还是中间层返回。每种现象都记录阶段和证据，不仅凭单一信号归因。",{"type":25,"children":231},[232],{"text":233,"type":29},"**启用了证书固定（pinning），还能测试吗？**",{"type":25,"children":235},[236],{"text":237,"type":29},"能做，但要看固定的是哪一层。只固定叶子证书的实现，换出口后证书不变，通常仍能建立连接；固定中间证书或整条链的实现，遇到地区链路上的中间设备改写就容易失败，这本身也是要记录的现象。这里不提供绕过证书校验的方法，测试应在授权的调试构建上进行。",{"type":25,"children":239},[240],{"text":241,"type":29},"**只在某个地区连不上，一定是代理 IP 的问题吗？**",{"type":25,"children":243},[244],{"text":245,"type":29},"单一出口失败不能直接说明是代理问题或 App 缺陷。结合失败阶段，补同地区多出口、供应商、时段、直连与服务端证据；DNS、TLS、401\u002F403 和超时都应先核实具体响应来源与路径，再决定是否换出口复测。",{"source":6,"id":247,"documentId":248,"translationKey":248,"locale":9,"slug":249,"path":250,"_path":250,"title":251,"description":252,"excerpt":252,"image":253,"publishedAt":254,"updatedAt":255,"author":17,"tags":256,"featured":19,"sortOrder":20,"readingTime":36,"bodyType":22,"bodyBlocks":257,"bodyHtml":124},3796,"y64gki0k633wq4rop2v89b94","website-third-party-script-regional-fallback-testing","\u002Fblog\u002Fwebsite-third-party-script-regional-fallback-testing","国际站第三方脚本测试：降级与告警验证","第三方脚本在部分地区加载失败时，如何判断页面降级是否符合设计？本文说明如何盘点页面依赖、在自有测试环境模拟阻断与超时，并检查核心流程、恢复行为和告警。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_af12243bd0.webp","2026-10-28T02:01:10.949Z","2026-10-28T02:01:10.933Z",[],[258,262,266,270,274,278,295,299,303,317,321,325,329,333,337,341,345,349,353,357,361,365,369,373,377,380,384,388,392,396,400,404,408],{"type":25,"children":259},[260],{"text":261,"type":29},"第三方脚本在部分地区被阻断或超时，页面往往\"看起来还是正常的\"：布局没塌、图片还在，但表单提交不了、埋点全丢、支付卡在最后一步。这类第三方资源加载失败通常不抛错，因此比白屏更难发现，也更难排查。",{"type":25,"children":263},[264],{"text":265,"type":29},"按依赖影响安排测试：先检查阻断核心流程的脚本，再看非核心组件。地区出口用于观察资源是否可达；降级逻辑则在自有测试环境中通过故障注入验证。",{"type":35,"level":36,"children":267},[268],{"text":269,"type":29},"盘点页面依赖",{"type":25,"children":271},[272],{"text":273,"type":29},"先按页面列出第三方脚本、来源域名、用途和失败影响。同一脚本在不同页面可能有不同优先级；例如验证码脚本可能阻断注册流程，在内容页却只是增强功能。记录来源域名，便于把单个资源不可达与整页故障区分开。",{"type":25,"children":275},[276],{"text":277,"type":29},"可按影响分为三类，具体等级应由产品路径确认：",{"type":279,"format":280,"children":281},"list","unordered",[282,287,291],{"type":283,"children":284},"list-item",[285],{"text":286,"type":29},"阻断：核心动作做不了，比如登录、支付、提交表单，先测。",{"type":283,"children":288},[289],{"text":290,"type":29},"降级：功能变弱但可完成，比如推荐位不显示，其次测。",{"type":283,"children":292},[293],{"text":294,"type":29},"无感：埋点、AB 实验这类，最后测。",{"type":35,"level":36,"children":296},[297],{"text":298,"type":29},"在授权环境模拟常见失败",{"type":25,"children":300},[301],{"text":302,"type":29},"在自有测试环境模拟失败，不针对生产流量或第三方真实服务。可分别测试：",{"type":279,"format":280,"children":304},[305,309,313],{"type":283,"children":306},[307],{"text":308,"type":29},"阻断：在自有测试环境对指定请求做拦截或拒绝连接；不要改生产 DNS。",{"type":283,"children":310},[311],{"text":312,"type":29},"超时：让请求挂起不返回，观察页面的等待上限。",{"type":283,"children":314},[315],{"text":316,"type":29},"错误响应：返回 5xx 或格式错误的脚本内容，看是否抛异常并中断后续脚本。",{"type":25,"children":318},[319],{"text":320,"type":29},"分开测试后，才能看出页面对网络阻断、等待超时和错误响应的处理差异。",{"type":25,"children":322},[323],{"text":324,"type":29},"用出口去复现\"某些地区加载不了\"，拿到的是现象：代理 IP 能证明这个问题在你关注的出口上真实存在，但证明不了你的降级逻辑对不对。两件事要分开做，前者用观测，后者用模拟。若需检查代理连通性，可参考[智能检测助手](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FSmart-check)，再回到自有环境的故障注入验证。",{"type":35,"level":36,"children":326},[327],{"text":328,"type":29},"检查失败时页面如何响应",{"type":25,"children":330},[331],{"text":332,"type":29},"降级策略按依赖等级、已批准的安全设计与产品契约验收。核心安全依赖失败时，明确提示并受控阻断可能是正确设计；替代验证必须经安全审查且不得降低校验强度。非核心组件是否需要提示，也按产品体验要求判断。",{"type":25,"children":334},[335],{"text":336,"type":29},"**页面布局**",{"type":25,"children":338},[339],{"text":340,"type":29},"检查脚本未加载时布局是否跳动、核心控件是否被遮挡。是否构成缺陷按产品体验要求判断。",{"type":25,"children":342},[343],{"text":344,"type":29},"**核心流程与安全边界**",{"type":25,"children":346},[347],{"text":348,"type":29},"按已批准的产品方案验证主流程。验证码等安全依赖失败时，可能需要安全阻断并明确提示；不要临时接入未经审核的替代验证，也要确认页面不会误报成功或重复提交。",{"type":25,"children":350},[351],{"text":352,"type":29},"**状态提示**",{"type":25,"children":354},[355],{"text":356,"type":29},"检查失败状态是否清楚可见，避免页面无响应或误报操作成功；提示和后续操作按产品设计验收。",{"type":25,"children":358},[359],{"text":360,"type":29},"对于受影响的流程，检查页面表现、操作结果和数据状态是否一致。",{"type":35,"level":36,"children":362},[363],{"text":364,"type":29},"验证恢复和告警",{"type":25,"children":366},[367],{"text":368,"type":29},"网络恢复后，检查脚本是否重复初始化、用户行为是否重复上报，以及告警是否按配置触发。",{"type":25,"children":370},[371],{"text":372,"type":29},"告警这一项最容易漏测。日志断言只能证明应用记录了事件，不能证明告警规则触发或通知送达。已接入测试通道时，验证规则、观察窗口、通知路由、接收与恢复解除；没有通道时明确标注“告警送达未验证”。",{"type":25,"children":374},[375],{"text":376,"type":29},"记录页面、脚本、模拟方式、用户可见结果和告警状态。日志存在不代表告警送达。",{"type":35,"level":36,"children":378},[379],{"text":91,"type":29},{"type":25,"children":381},[382],{"text":383,"type":29},"**模拟失败会不会影响线上真实用户？**",{"type":25,"children":385},[386],{"text":387,"type":29},"若故障注入严格限定在自有测试环境或隔离会话，并确认规则不会影响生产流量，通常不会影响线上用户。测试前先核对拦截范围；不要对第三方真实服务主动探测或施加阻断。",{"type":25,"children":389},[390],{"text":391,"type":29},"**脚本失败但页面看起来正常，还需要处理吗？**",{"type":25,"children":393},[394],{"text":395,"type":29},"视影响等级和安全设计决定。重点确认用户是否能识别失败、核心流程是否按预期处理，以及数据有没有误报成功或重复提交。",{"type":25,"children":397},[398],{"text":399,"type":29},"**降级做到什么程度算通过？**",{"type":25,"children":401},[402],{"text":403,"type":29},"按依赖等级、安全设计和产品约定判断。受控阻断可能是正确结果；替代流程不得绕过安全校验。日志断言通过也不代表告警已经发送或送达。",{"type":25,"children":405},[406],{"text":407,"type":29},"**用代理 IP 复现脚本失败就够了吗？**",{"type":25,"children":409},[410],{"text":411,"type":29},"不够。出口只能证明\"在这个地区确实加载失败\"，证明不了降级逻辑写对了。降级要单独测，出口只是发现问题的入口。本地请求拦截或 mock 可模拟失败，但不能证明目标地区出口或第三方实际故障；地区可达性观察与本地故障注入要分开记录。",{"source":6,"id":413,"documentId":414,"translationKey":414,"locale":9,"slug":415,"path":416,"_path":416,"title":417,"description":418,"excerpt":418,"image":419,"publishedAt":420,"updatedAt":421,"author":17,"tags":422,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":423,"bodyHtml":124},3795,"gfk97rtcs8x8vegewhqnyala","mobile-app-push-timezone-network-delivery-testing","\u002Fblog\u002Fmobile-app-push-timezone-network-delivery-testing","App 推送时区测试：三层时间与边界用例","推送\"延迟\"常被当成网络问题，实际是触发时间、到达时间、展示时间三层语义混在一起。固定基准时钟，覆盖 UTC 边界与夏令时切换，分别记录三层时间与点击后的落地状态，才能判断问题在哪一层。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_app_cover_2edd2f32cb.webp","2026-10-28T02:00:54.047Z","2026-10-28T02:00:54.036Z",[],[424,428,432,436,440,444,448,452,456,460,464,468,472,476,480,484,488,492,496,500,504],{"type":25,"children":425},[426],{"text":427,"type":29},"推送延迟要先分清服务端调度、推送服务状态、设备接收和屏幕展示。用户反馈的“没收到”可能发生在其中任一环节。",{"type":25,"children":429},[430],{"text":431,"type":29},"先统一测试设备与服务端的时钟，再分别记录调度触发、服务端收到的推送状态、设备实际接收和通知展示时间。设备时区与网络出口是不同变量，应分开测试。系统推送和用户点击后加载页面也可能走不同网络路径；只有实际配置走代理的请求才使用该出口。本文聚焦自有 App 的验证。",{"type":35,"level":36,"children":433},[434],{"text":435,"type":29},"分别记录调度、接收与展示",{"type":25,"children":437},[438],{"text":439,"type":29},"这几个时间点由不同环节产生，记录时应使用同一通知 ID，并区分服务端日志与设备侧观测。",{"type":25,"children":441},[442],{"text":443,"type":29},"**调度触发时间**",{"type":25,"children":445},[446],{"text":447,"type":29},"查看计划触发时间与任务实际执行时间，并记录使用的时区。固定偏移可能来自本地时间与 UTC 转换不一致，不应先归因为地区网络。",{"type":25,"children":449},[450],{"text":451,"type":29},"**设备接收时间**",{"type":25,"children":453},[454],{"text":455,"type":29},"推送服务受理或投递状态不等于设备已经收到。优先记录设备侧通知日志；无法观察设备接收时，标为未知。通知类型、优先级、平台规则和系统状态都可能影响结果，应结合通知 ID 和统一时钟分析。",{"type":25,"children":457},[458],{"text":459,"type":29},"**屏幕展示时间**",{"type":25,"children":461},[462],{"text":463,"type":29},"检查通知实际出现的时间、顺序和分组。系统策略可能造成延迟或摘要展示；先记录现象，再按产品预期、平台规则和同类设备结果判断是否异常。字段缺失、落地错误、延迟、丢失或重复都应有记录。",{"type":25,"children":465},[466],{"text":467,"type":29},"分别比较计划触发、实际执行、服务端状态、设备接收和展示。差异能帮助定位环节，但单一时间差不能直接证明根因。",{"type":35,"level":36,"children":469},[470],{"text":471,"type":29},"测试跨日与夏令时边界",{"type":25,"children":473},[474],{"text":475,"type":29},"覆盖 UTC 跨日、跨月与跨年边界。夏令时测试使用 IANA 时区而非固定偏移量，例如 `Europe\u002FBerlin` 的春季跳时与秋季重复时段。测试前先明确不存在或重复的本地时间应跳过、顺延还是执行多次，并记录计划与实际执行时间。",{"type":25,"children":477},[478],{"text":479,"type":29},"尽量在同一批次执行对照，并记录每条用例的计划与实际触发时间。",{"type":35,"level":36,"children":481},[482],{"text":483,"type":29},"分开测试设备时区与网络出口",{"type":25,"children":485},[486],{"text":487,"type":29},"测试时先固定出口，只改设备时区，观察展示时间和日期文案；再固定时区，只改变出口，检查地区化页面或接口响应。不要把出口变化直接当作推送投递差异的原因。",{"type":35,"level":36,"children":489},[490],{"text":491,"type":29},"检查点击后的落地页面",{"type":25,"children":493},[494],{"text":495,"type":29},"点击行为应与推送投递分开验证。记录冷启动、已登录和链接过期等场景下的落地页面、耗时与回退结果，并注明当时的设备时区和实际网络路径。",{"type":25,"children":497},[498],{"text":499,"type":29},"冷启动时记录首屏耗时和目标页面是否保留；已登录时检查页面状态；链接过期时检查提示与回退页面。",{"type":25,"children":501},[502],{"text":503,"type":29},"实际测试可用一行记录计划时刻与 IANA 时区、对应 UTC、调度和设备侧证据、点击结果。春季跳时和秋季重复时段分别建用例；设备接收无法观测时写“未知”，未实际执行时不要填写通过或失败。",{"type":25,"children":505},[506],{"text":507,"type":29},"推送服务到设备的链路与 App 请求可能不同，应根据实际配置分别观察。代理出口可用于测试配置走该出口的地区化请求；目标地区测试机或云主机也可提供对照。",[509],{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":510,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":511,"bodyHtml":124},[],[512,515,518,521,524,527,530,533,536,539,542,545,548,551,554,557,560,563,566,569,572,575,578,581],{"type":25,"children":513},[514],{"text":28,"type":29},{"type":25,"children":516},[517],{"text":33,"type":29},{"type":35,"level":36,"children":519},[520],{"text":39,"type":29},{"type":25,"children":522},[523],{"text":43,"type":29},{"type":25,"children":525},[526],{"text":47,"type":29},{"type":35,"level":36,"children":528},[529],{"text":51,"type":29},{"type":25,"children":531},[532],{"text":55,"type":29},{"type":25,"children":534},[535],{"text":59,"type":29},{"type":35,"level":36,"children":537},[538],{"text":63,"type":29},{"type":25,"children":540},[541],{"text":67,"type":29},{"type":25,"children":543},[544],{"text":71,"type":29},{"type":35,"level":36,"children":546},[547],{"text":75,"type":29},{"type":25,"children":549},[550],{"text":79,"type":29},{"type":25,"children":552},[553],{"text":83,"type":29},{"type":25,"children":555},[556],{"text":87,"type":29},{"type":35,"level":36,"children":558},[559],{"text":91,"type":29},{"type":25,"children":561},[562],{"text":95,"type":29},{"type":25,"children":564},[565],{"text":99,"type":29},{"type":25,"children":567},[568],{"text":103,"type":29},{"type":25,"children":570},[571],{"text":107,"type":29},{"type":25,"children":573},[574],{"text":111,"type":29},{"type":25,"children":576},[577],{"text":115,"type":29},{"type":25,"children":579},[580],{"text":119,"type":29},{"type":25,"children":582},[583],{"text":123,"type":29},null,[],[]]