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