QA service mesh approach
summary
Claim: deploying a tiny QA Web Services app alongside each SUT gives one-to-one REST control over server files and queues, removing flaky SSH hacks. Built artifacts include an FS util to create/read/delete files and an MQ util that caches messages to avoid race conditions and enable parallel runs. Implementation is a Spring Boot example on GitHub, runs in the same container, requires CI/deployment and unit tests only, and proves practical: it speeds setup and works well with manual checks and lightweight unit coverage.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 3:01File system testing
- 10:01Message queue integration
- 14:48Standardizing infrastructure
- 19:15Dynamic property management
- 22:24QA service mesh approach
- 25:40Microservices and logging
- 26:50Best practices for adoption
- 32:01Explaining the terminology
- 33:01Q&A session
related talks
56mWrite Tests That Spark Flow
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
30mQA in DevOps: Transformation thru Automation via Jenkins
02h 36mTesting Java Microservice
26mStreamlining Cloud-Native Development: Simplifying Dependencies and Testing with Microcks
36mFrom Sledgehammer to Fine Brush for QA
05mNew Rules Of Engagement For Product Quality: Testing-As-A-Service In ...
34mWrite tests that spark flow