Changes that affect the architecture and design of a project are among the most important changes that can be made. However, design changes can also be some of the most difficult changes to understand. AppLand’s visualizations of code design and behavior are a powerful way to review design changes, because they depict the code behavior directly, rather than requiring a developer to imagine how code might work by analyzing diffs of source code text files. With branch-specific recordings of code behavior, AppLand enables development teams to quickly and effectively review code behavior and design changes across development branches. This is particularly useful for reviewing pull/merge requests. With recordings of application behavior loaded into AppLand, you can use AppLand’s powerful filters to find and highlight exactly the code behaviors that are proposed in a new branch. Focus on commands, responses, the data model, SQL, and changes to key classes in order to help a reviewer understand how you propose to change the design of the code.
This tutorial uses a variety of open-source applications as examples. You can record and upload test cases of your own applications using the AppMap client tools.