4 posts tagged with "Software Testing"

"We're now cooperating with AIs and usually they are doing the generation and we as humans are doing the verification. It is in our interest to make this loop go as fast as possible. So, we're getting a lot of work done."

— Andrej Karpathy: Software Is Changing (Again)

This quote describes a shift that is already visible in many teams. Code generation has accelerated. Verification and validation increasingly become the bottleneck.

With AI tools, writing code is often not the limiting factor anymore. The hard part is proving that what was generated is correct, safe, and maintainable.

Writing unit tests is expensive. Not just in time, but in technical debt.

Every test you write is code you must maintain. When you refactor, you refactor twice: once for production code, once for test code. When dependencies change, you update mocks. When APIs evolve, you rewrite assertions.

What if there was a different way? What if your tests could be generated from reality itself?

For decades, a "golden mantra" of product-to-test code ratio existed among engineers: 1:1. It was believed that if the volume of code a developer writes equals the volume of tests, the project is in good shape.

However, new scientific research and the rapid development of test automation tools (especially LLMs) in 2024–2025 show that this metric is outdated. Today, to ensure high quality in mature systems, test code must constitute 50% or more of the entire codebase.

Testing for JVM applications-Java, Kotlin, Spring Boot-often struggles to keep up with distributed systems, asynchronous flows, and frequent code changes. Traditional methods rely on mocks and black‑box checks that don't reflect how the system really behaves. The result: flaky tests, missed bugs, and uncertainty before release.

BitDive provides a single platform for the entire testing lifecycle. It captures real execution data, curates meaningful scenarios, replays them across builds, and validates results where it matters most-at the level of API responses, database queries, and messaging flows.

JVM-first • Testcontainers-ready • Kafka/gRPC/JDBC support • CI/CD friendly • Flake-resistant