FAQ from Jazzberry
What makes Jazzberry’s “real-code execution” different from conventional testing?
Jazzberry doesn’t rely on mocks, stubs, or static signatures. It runs *your actual binaries and scripts*—with real dependencies, configuration, and data flow—in ephemeral, instrumented sandboxes. This reveals bugs invisible to static analyzers: timing-dependent race conditions, subtle type coercion failures, or third-party SDK side effects triggered only in specific call sequences.
How does Jazzberry protect sensitive code during execution?
Your code never leaves the sandbox. Each analysis occurs in a firewalled, short-lived container with no outbound internet access unless explicitly permitted (e.g., for public dependency resolution). All artifacts—including logs, memory dumps, and test outputs—are cryptographically erased post-review. Data in transit uses FIPS 140-2 validated TLS; at rest, it’s never persisted.
Can Jazzberry detect non-security bugs that only appear when code runs?
Absolutely. Jazzberry identifies functional anomalies like incorrect state transitions in React components, infinite loops under low-memory conditions, CORS misconfigurations exposed only during fetch calls, or even visual regressions in headless browser sessions—providing screenshots and DOM diffs alongside stack traces.
Does Jazzberry support monorepos, containerized services, or legacy frameworks?
Yes. Jazzberry auto-detects build systems (Turborepo, Nx, Gradle, Make), orchestrates Docker Compose stacks for service interdependency testing, and supports legacy runtimes including PHP 5.6, Python 2.7, and Node.js v12—ensuring coverage across modern and maintenance-mode codebases.
Is there a free trial available for Jazzberry?
Yes—start a risk-free 7-day trial of Jazzberry Pro, including unlimited PR reviews, custom sandbox configuration, and priority support. No credit card required.