Interview Bank

Build an AI Short-Drama Production Pipeline With Agents in 14 Days

D1 What an AI Short-Drama Production Pipeline Looks Like: Breaking Down the Stages, a Task-Graph Architecture, and Choosing Among Four Categories of Generation Models

• For a system that depends heavily on paid third-party generation APIs, how do you make it developable and testable without keys — and how do you prove the offline mode is not fooling you?一个重度依赖付费第三方生成接口的系统，怎么做到没有密钥也能开发和测试？怎么证明这套离线模式没有骗自己？

  Common in ChinaCommon overseasDeep dive#offline-testing#test-strategy

  How to reason about it · think before answering

  1. All the signal is in the second half. Everyone says mock it; only people who have done it can say how they prove the mock is honest, because most mocks only guarantee the program does not crash.
  2. Break it down by first fixing where the stub goes: only at the network egress, inside each provider's one method. No environment check belongs in business code — the moment business logic branches, offline runs a different program and your testing says nothing about production.
  3. Then fix the quality of the stub: the offline implementation should emit artifacts of the real shape rather than a constant. For a media pipeline, actually generate placeholder files locally (solid-color frames, a test pattern with an audio track, a sine-wave clip); for retrieval, return well-formed fake documents; for streaming, emit chunks with realistic pacing. The point is to force downstream parsing, state machines, and timeline math to execute.
  4. The one test that proves it is honest: change an input and the output must change. Placeholder color tracks the shot description, placeholder audio length tracks the line length, total runtime tracks shot count. If every input yields identical artifacts, you only verified that nothing crashed.
  5. State the payoff too: a real run costs tens of minutes and real money, so an off-by-one takes half an hour to surface. Offline collapses that loop to seconds, which is what makes continued refactoring affordable. This is an engineering requirement, not a toy.
  6. Likely follow-up: who then covers the real path? Layer it — offline covers business logic and regression, while a small set of smoke tests exercises the real vendors on a schedule. They verify different things and do not substitute for each other.

  分析过程 · 先想清楚再作答

  1. 这题的区分度全在后半句。前半句人人都会答「打 mock」，能答出「怎么证明它没骗自己」的才是真做过——因为绝大多数 mock 的实际效果是「保证程序不崩」，而不是「保证逻辑正确」。
  2. 怎么拆：先定桩的位置。桩只打在网络出口上，也就是每个 provider 的那一个方法里；业务代码里一个环境变量判断都不该有。一旦业务逻辑分叉，离线跑的就是另一个程序，你验的东西和线上没关系。
  3. 再定桩的质量：离线实现要产出真实形态的产物，而不是返回一个常量。做媒体流水线就用本地工具真的生成占位文件（纯色图、测试画面加音轨、正弦波音频），做检索就返回结构完整的假文档，做流式就按节奏一段段吐。目的是让下游的解析、状态机、时间轴计算真的被执行一遍。
  4. 证明它没骗自己的判据只有一条：**改一个输入，输出必须跟着变**。占位图的颜色随镜头描述变、占位音频时长随台词字数变、总时长随分镜数变——这说明中间的业务逻辑跑过了。如果换什么输入产物都一样，你验的只是没崩。
  5. 还要说收益：一次真跑几十分钟、上百块钱，一个下标写错就要等半小时才看得到；离线把这个反馈循环压到几秒，团队才会愿意持续重构这段代码。这是工程要求，不是玩具。
  6. 可预期的追问：那真实路径谁来保证？答案是分层——离线模式覆盖业务逻辑与回归测试，真实路径靠少量的冒烟用例定期跑，两者验的是不同的东西，不能互相替代。

  Key points

  • Stub only at the network egress; business code contains no offline branch
  • The offline implementation must emit real-shaped artifacts so downstream parsing, state machines, and timeline math actually run
  • The single acceptance test is that changing an input changes the output; otherwise you only verified it did not crash
  • The payoff is collapsing a tens-of-minutes, real-money feedback loop into seconds, which is what makes refactoring affordable
  • Cover the real path with a small scheduled smoke suite; it verifies something different from the offline mode

  答题要点

  • 桩只打在网络出口，业务代码里不出现任何离线判断分支
  • 离线实现要产出真实形态的产物，让下游解析、状态机、时间轴计算真的执行
  • 唯一的验收判据是「改一个输入，输出跟着变」，做不到就只验了没崩
  • 收益是把几十分钟上百块的反馈循环压到几秒，团队才敢持续重构
  • 真实路径靠少量定期冒烟用例覆盖，与离线模式验的是不同的东西