"Po Linn Chia presented how they re-used a single development environment to deploy multiple service versions for testing their distributed system in her presentation No QA Environment? No Problem at Dev Summit Boston. A small enablement team, cultural buy-in, and gradual learning helped teams collaborate, reduce cognitive load, and scale testing practices. Without a dedicated QA environment, teams faced tech and coordination issues when testing a distributed system,"
"A slow, unmaintainable CLI led an organization to shift left with automated testing. They built a tool for versioned deployments using CI and proxy routing, enabling developers to run isolated tests on multiple versions to catch bugs earlier. Having implemented their internal deployment tool, they realized that their team structure was no longer viable for what they were trying to do."
Teams reused a single development environment to deploy multiple service versions for testing distributed systems. A small enablement team, cultural buy-in, and gradual learning improved collaboration, lowered cognitive load, and scaled testing practices. A slow, unmaintainable CLI prompted a shift-left toward automated testing and the construction of a versioned-deployment tool using CI and proxy routing. The tool allowed isolated tests across multiple versions to surface bugs earlier. Growth exposed that the existing team structure blocked other teams and could not scale. Production testing failed because production systems would not accept test data and monitoring could not replace testing. A tiny tiger-style enablement team was created to remove obstacles and enable cross-functional work.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]