When does a migration pipeline need rich prompt context instead of just retries?
Retries handle files where the fix is small and local — a wrong import, a renamed assertion. Files with deep indirection, custom test utilities, or non-standard setups need the model to understand project-specific conventions it can't infer from the failing file alone. That's when injecting sibling test files, high-quality examples, and the component's own source code becomes necessary — context, not more attempts, closes that gap.
Answered in
How to Migrate Thousands of Legacy Test Files With LLMs, Not RewritesA step-based pipeline, retry loops instead of perfect prompts, and rich context injection turn a year-long manual migration into a six-week automated one.
Read the full analysisOther questions this article answers
More development best practices questions
- What did OpenAI’s Habitat team change?
- Does the reported 12× read improvement mean another team should copy the design?
- Does the Python Typing Survey measure all Python developers?
- Do Python type hints enforce types at runtime?
- What is interactive refactoring in gopls?
- Is interactive refactoring already part of the official LSP standard?
- What does Meta mean by human-on-the-loop software engineering?
- Does Meta's Forum project prove that AI can replace a software team?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.