Performance Testing is not only API
summary
Shows a concrete proof of concept that unit/component tests can run as performance tests using Zero Code TDD with JUnit 5, WireMock and pipeline templates, replacing OpenJDK/JMH for licensing reasons. Implements per-test isolation, parallel execution fixes, and switches timing to nanoseconds to get real response times. Runs nightly delta comparisons as a baseline. Custom work takes about 80 hours for JUnit5 adjustments; the POC works technically but initial client teams decide their services don’t need it.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 6:33Shift left testing concept
- 8:21Performance testing basics
- 13:04Tool research and selection
- 19:30Initial implementation steps
- 25:09Team collaboration challenges
- 29:08Final results and lessons learned
- 31:17Q&A session
related talks
29mJava Performance Testing for Everyone
49mPerformance Testing
29mProgressive Testing to Meet the Performance Imperative
41mContinuous Performance Testing in DevOps
51mThe Swag of Performance Testing
50mPerformance Testing Java Applications
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
57mOpen Forum on Performance Testing