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