TestContainers, Unit, Integration, System, Load and Stress Testing

An airhacks.fm conversation with Kevin Wittek (@kiview) about: The Java Blockchain Benchmarking Framework, ironkobra, practicing heavy metal in a hospital, boring but fast Mugen Seiki, Uli Jon Roth and G3, playing together with Uli Jon Roth, the Dodge Charger experience, the Jakarta EE, MicroProfile and Quarkus test approaches, the 3 kubernetes environments, using Jenkins on OpenShift, unit tests, integration tests and system testing, the wad.sh tool for local deployment, using TestContainers to launch PostgreSQL, port forwarding with OpenShift, seamless onboarding with TestContainers, black box integration tests are system tests, convenient system testing with Jakarta EE, kubernetes readiness probes are waiting strategy from test containers, using TestContainers to execute openshift deployments locally, TestContainers is a convenient, object oriented API for docker, in the next, major, TestContainers release the testing and docker remote control are going to be separated, using TestContainers for JPA integration testing, Quarkus and TestContainers, in-process System Testing is for lazy developers, enforcing frequent integrations, kubernetes is a larger problem than an application server, from local scripts, to central Jenkins pipeline, TestContainers always removes all the containers after JVM exit, the reusable container feature, interactive testing environment, unit tests are for classes in project's control, integration tests are for classes outside the project's control, pentagonal architectures, system tests is a blackbox tests, stress tests and performance tests, why REST-assured is not used, performance tests with JMH, using JMH for Blockchain Benchmarking Kevin Wittek on twitter: @kiview on github https://github.com/kiview and Kevin's blog.