So… let’s solve some of these challenges, shall we?!
What can I do with it?
For example, you can use AppMap to:
- Document and explain your code – AppMap automatically documents end-to-end code and data flows, web services catalogs and your app’s database schema as you work. You can also record interactive maps of any piece of code and share it with other devs via a URL or by attaching it to a ticket in Jira or GitHub to clearly communicate your code’s behavior, logic and design.
- Understand how new-to-you code works – Instead of trying to decipher an entirely new codebase, you can use AppMaps to learn and read just the code that’s relevant to your task. Source code is just a click away, so you can easily move back and forth between high-level code design views, code execution traces and source code details.
- Debug code – Since AppMap provides interactive maps of all the factors that might be contributing to a bug, you can figure out where things are going wrong. You can quickly navigate around source code, and see parameter values, HTTP server and client requests and complete SQL queries.
What are the requirements?
- An application that has mocha tests, mocha >= 8.0.0 (older versions are not supported)
- An application that uses the Express.js framework 4.x
- A git repository
- An application that uses one of these DB drivers: mysql, pg or sqlite3
How do I get started?
Where can I find more info?