Why Coverage Metrics Fail and System Tests Win
About this episode
The episode discusses the differences between various testing methodologies and the misuses of code coverage metrics.
An airhacks.fm conversation with Stanislav Bashkyrtsev about: discussion about testing terminology and the difference between unit tests, component tests, System Tests , and integration tests, defining component tests as in-process invocations without HTTP, using RestAssured with MockMvc-style direct endpoint calls, avoiding mocks in favor of real system tests, why code coverage is a misused management metric, the anti-pattern of using reflection to inflate coverage, distinguishing line and branch coverage from actual verification, using coverage from system tests to detect dead code for pruning, mutation testing with PIT to measure assertion quality, testing Quarkus applications, the default Guice and Guava dependencies in Quarkus RESTEasy , starting a new microservice with a separate system-test module, calling endpoints over HTTP with the MicroProfile REST Client or the Java HTTP client , deploying Quarkus on AWS Lambda as a production-like environment, backward compatibility testing with multiple production versions, turning system tests into stress and load tests, testing connection pools and metrics under load, introducing a test-only private API to verify state changes in…
People in this episode
Host: Adam Bien
Guest: Stanislav Bashkyrtsev
Mentioned in this episode
Organizations: Quarkus, AWS Lambda, PostgreSQL, GraalVM, Oracle Database, Guice, Guava, MicroProfile
More episodes of airhacks.fm podcast with adam bien
- Zero-Dependency Java 25, Event Sourcing, and Stabilizing Legacy Systems
- From CloudFormation to CDK with Java
- Architectural Trade-offs: Pendulum Swings, Outsourcing Cycles and System Design
- From WebSphere to Quarkus: The Evolution of Java Classloading
Explore listener stats, chart rankings, contacts and more on the airhacks.fm podcast with adam bien podcast page.