Cloud Testing Without the Wait: K8 development experience
summary
Claims a practical way to push cloud testing earlier so developers catch cloud-specific bugs in seconds not hours, using shift left on cloud testing via the tool mer. mer injects an agent into a target pod, connects local IDE/CLI to a remote cluster, reroutes traffic and file access, and auto-terminates the agent when done. Demo changes render in the live URL without affecting production, startup completes in 15–30 seconds and scales across hundreds of microservices.
AI-written summary · about
chapters (7)
- 0:00Introduction and Overview
- 0:19About the Speaker
- 1:23Traditional Development Workflow Challenges
- 7:56The Need for Shift Left Testing
- 12:20Introducing MirrorD
- 16:31MirrorD Demo
- 24:11Conclusion and Further Resources
related talks
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
30mMaybe It's Time to Rethink How You've Been Developing?
55mFrom my Machine to the Cloud with Cloud-Native Tools
01h 00mJava on Kubernetes What I Wish I Knew First
35mElevate your testing: testing smarter, not harder, in the cloud!
50mSimplifying cloud-native app testing across environments
48mTesting The Cloud
13mInterview of Jerome Petazzoni