新增:实际 Next.js 确认链的离线浏览器回归 - #94
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
原有全链回归使用简化确认页,无法发现真实 Next.js 话术弹窗、Chrome Bridge 或结果刷新之间的断链。本次使用当前提交构建后的实际分析页,在隔离 Chromium 中完成取消、确认、扩展派发、后端领取、证据回调与刷新核对。
平台预检和实际副作用仍为合成场景;AI Provider 使用 Mock,Spring 连接随机端口和临时 SQLite。新增静态资源响应器仅在测试响应中替换回环端口,阻止访问正式 6866。临时扩展钩子不会进入生产包。
CI 的 Windows/Linux 浏览器任务复用 Frontend Job 构建产物,缺少产物直接失败。同步文档明确真实网站 Smoke 与已加载扩展仍需单独验收。
验证:pnpm --dir front build 通过;browserRegressionTest 共 6 项通过;git diff --check 通过。无生产代码、数据库或扩展权限变更,不需要正式服务部署。