AppMap Analysis

AppMap Analysis scans your AppMaps to find software design flaws that impact performance, stability, security and maintainability. This runtime code analysis can find the problems that static code analyzers miss - and that cause 90% of today’s most serious production issues.

Currently available for early access for Ruby on Rails and Java Spring applications. Contact us if you would like to join the early access program.

Demo

Highlights

  • Identifies design flaws and anti-patterns before they’re merged.
  • Runs in your local dev environment, and/or in CI.
  • Automatically checks each pull request and reports new findings.
  • Ensures that software design flaws are fixed before code is merged.
  • Integrated with VSCode and JetBrains code editors.
  • Customizable, per-repo configuration.
  • Write custom rules in TypeScript, according your own needs.

How does it work?

Capturing data for analysis

The process starts by recording AppMaps of your test cases.

Performing a scan

AppMap Analysis examines AppMaps using a set of defined software quality rules. There are many useful built-in rules, and you can write your own. You can use the default settings, or define your own custom configuration.

Automation with CI

To guarantee that each code change is checked before merging, AppMap Analysis can be executed as part of your CI job. Run your tests in the normal manner, with AppMap recording enabled to create AppMap files. Then run the AppMap Analysis scan as a follow-on build stage. AppMap Analysis is fully paralellizable - each AppMap scan is independent from all others.

To prevent design flaws from being merged, AppMap Analysis can be configured to fail the build job, or to reject a commit in GitHub. This ensures that every finding is appropriately addressed before changes are accepted into the main branch.

Requirements

Next steps


Was this page helpful? thumb_up Yes thumb_down No
Thank you for your feedback!