Module 1: Debugging recipes
In this module, you'll learn how to debug recipes with unit tests and with the Moderne CLI.
This module assumes you have already completed Fundamentals Module 1: Recipe development environment. That module covers the environment setup this workshop depends on, including cloning the rewrite-recipe-starter repository, installing the Moderne CLI, and running the starter's tests. Complete it first if you haven't, then return here.
Exercise 1: Debugging recipes
Goals for this exercise
- Debug a recipe against real code by attaching a debugger to a CLI run.
- Understand how to set breakpoints in a recipe class or visitor.
- Use the
TreeVisitingPrinterto see what an LST looks like.
Steps
- Follow Validating recipes at scale. It walks you through setting an active recipe, building LSTs, and attaching a debugger while the CLI runs the recipe against real code.
- Open a test case (e.g.,
FindSpringBeansTest), set breakpoints insidevisit()or the visitor logic, then run the test in debug mode (green bug icon in IntelliJ) and step through to inspect variables and visitor flow. - Configure the TreeVisitingPrinter to see what an LST looks like when your recipe finds a match — a great way to learn the different Java LST elements. You'll need to add
import org.openrewrite.java.TreeVisitingPrinter;to your recipe's imports.
Takeaways
- You can attach any JDWP-capable debugger to a CLI recipe run to debug recipes against real code.
- Logging and breakpoints are helpful tools for troubleshooting recipe behavior.
- The
TreeVisitingPrinteris a great way of understanding what the LST looks like.