// ET test execution and failure debugging workflow for WOW. Use when building before tests, cleaning Logs, running server or Hotfix tests through ET.App Test commands, running Unity Editor tests through UnityBridge UnityTestRunRequest, reading Logs/All.log, judging results, and diagnosing failed or unmatched tests.
ET async and EntityRef safety workflow. Use when adding, modifying, or reviewing async/await, ETTask, generic ETTask results, ETCancellationToken, NewContext, concurrent waits, handler Run async safety, or any Entity access after await in WOW/ET code or tests.
ET build, analyzer, proto export, server startup, and publish workflow. Use when compiling WOW with dotnet build ET.sln, exporting Proto to C#, starting ET.App, publishing, or validating analyzer/build results.
ET framework C# code authoring and review workflow. Use when creating or modifying Entity, Component, System, Helper, message handlers, package dependencies, assemblies, module analyzer boundaries, C# file placement, .meta handling, ECS layering, or component contract logic in WOW/ET packages.
ET Excel MCP workflow for reading, writing, styling, transforming, and inspecting xlsx data. Use when operating Excel cells, ranges, sheets, formulas, charts, merges, batch data import/export, or editing Luban source spreadsheets before export.
ET git workflow for preparing commits and reviewing changes. Use when checking git status or diff, filtering unrelated files, staging task-scoped changes, writing Chinese commit messages, or synchronizing with remotes using rebase instead of merge.
ET Luban export workflow. Use when exporting generated C# config/data code, refreshing aggregated luban.conf, validating CodeMode outputs, or troubleshooting ET.ExcelExporter, LubanGen.ps1, table definitions, beans, enums, Defines, and Luban export failures.
| name | et-test-run |
| description | ET test execution and failure debugging workflow for WOW. Use when building before tests, cleaning Logs, running server or Hotfix tests through ET.App Test commands, running Unity Editor tests through UnityBridge UnityTestRunRequest, reading Logs/All.log, judging results, and diagnosing failed or unmatched tests. |
et-test-write。et-build。dotnet build ET.sln 编译，除非用户明确只要看日志或已经完成编译。Logs/，避免旧日志干扰。Test 命令到 dotnet ./Bin/ET.App.dll --SceneName=Test。UnityTestRunRequest，按 Name 正则匹配测试类名执行。Filter、ExecutionSettings 或 Test Runner。Logs/All.log，Editor 测试看 response 里的 Message 与 Results[].Message。Logs/All.log，确认没有隐藏异常或错误日志。dotnet build ET.sln
Remove-Item ./Logs -Recurse -Force -ErrorAction SilentlyContinue
"Test" | dotnet ./Bin/ET.App.dll --SceneName=Test
"Test --Name=CreateRobot" | dotnet ./Bin/ET.App.dll --SceneName=Test
dotnet ./Bin/ET.UnityBridge.dll '{"_t":"Ping"}'
dotnet ./Bin/ET.UnityBridge.dll '{"_t":"UnityTestRunRequest","Name":".*"}'
Get-Content ./Logs/All.log -Tail 200
| 现象 | 优先检查 |
|---|---|
| Entity 已失效 | await 后是否通过 EntityRef 重新获取 |
| 数据不一致 | 测试准备与配置链路 |
| 消息超时 | 网络消息发送、事件是否真的发布 |
| Fiber 未找到 | 场景或 Fiber 名称 |
| 未找到测试 | 类名、PackageType 前缀、测试目录 |
| Editor 测试未匹配 | Name 正则、类是否继承 ET.Test.ATestHandler、是否在 Scripts/Editor/Test/ |
找不到 UnityTestRunRequest | Unity Editor 是否打开、UnityBridge 是否在线、是否执行过 Refresh |
| 配置不存在 | 测试是否自己用代码构造最小 Config 数据 |