{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"How We Run 250,000 Automated Tests a Day on Kubernetes","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/21749d9e\"></iframe>","width":"100%","height":180,"duration":1417,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/how-we-run-250000-automated-tests-a-day-on-kubernetes.\nHow a financial-services firm runs 250,000 automated tests a day on 4 Amazon EKS clusters with Kueue quotas, sharding, flake policy, and certification.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #kubernetes, #test-automation, #devops, #software-testing, #platform-engineering, #cicd, #flaky-tests, #testing,  and more.\nThis story was written by: @lokeshsuri. Learn more about this writer by checking @lokeshsuri's about page,\n            and for more stories, please visit hackernoon.com.\nA centralized test platform on Kubernetes runs about 250,000 automated tests a day across four EKS clusters. Kueue quotas and priority classes keep any one team from starving the others. Indexed Jobs split large suites into shards. Flaky tests are handled as platform policy, with a single retry and a quarantine that has an owner. The reporting layer turns raw results into release certification, and it matters as much as the scheduler.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}