Designing Smoke Tests for Release Gates
You cannot run everything before deployment. A strong release gate depends on a short, reliable smoke test set with clear purpose.
AI DevOps Korea
Aidevops.kr covers LLMOps, RAG, agents, observability, evaluation, and cost-performance optimization for production AI services.
This group clusters posts that are best read together inside the Test category, so the learning path feels more intentional.
This group currently contains 6 posts.
Start Here
You cannot run everything before deployment. A strong release gate depends on a short, reliable smoke test set with clear purpose.
Group Archive
You cannot run everything before deployment. A strong release gate depends on a short, reliable smoke test set with clear purpose.
Many unstable tests fail because of data, not assertions. Teams need rules for creation, sharing, cleanup, and retention.
Testing should not end at pre-release CI. This post explains how to connect synthetic monitoring with canary rollout validation.
Running more tests is not the same as shipping safely. This guide explains how to define a release-candidate cutline around real risk.
A structured testing roadmap from unit test basics to contract boundaries, flaky-test control, and production-grade quality strategy.
A practical way to classify, contain, and fix flaky tests before they erode trust in the entire pipeline.