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.
Explore the category through a featured entry point, a short recommended reading flow, and the tags that appear most often here.
This category currently contains 20 posts.
Featured In This Category
You cannot run everything before deployment. A strong release gate depends on a short, reliable smoke test set with clear purpose.
Popular Picks
How to use Playwright as a reliable E2E testing platform rather than just a browser automation tool. Covers strategy, configuration, selector rules, mocking, auth-state reuse, and practical ways to reduce flaky tests.
A practical guide to using k6 as a tool for validating performance hypotheses. Covers scenario design, thresholds, think time, workload modeling, CI integration, and common mistakes.
A practical guide to Spring Boot test slices from the perspective of test-pyramid design and execution cost. Covers when to use @WebMvcTest, @DataJpaTest, @JsonTest, @RestClientTest, and when @SpringBootTest is the better choice.
Reading Flow
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.
Key Tags
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.
How to decide what a contract test should cover so teams catch integration risk without duplicating full end-to-end suites.
A practical way to classify, contain, and fix flaky tests before they erode trust in the entire pipeline.
How to separate release-time end-to-end tests from production synthetic checks without duplicating effort or confusing confidence signals.
A practical guide to Spring Boot test slices from the perspective of test-pyramid design and execution cost. Covers when to use @WebMvcTest, @DataJpaTest, @JsonTest, @RestClientTest, and when @SpringBootTest is the better choice.
A practical guide to choosing the right test double. Covers the difference between state verification and interaction verification, the risk of excessive mocking, and how to decide between mocks, stubs, spies, and fakes.
A practical guide to testing Java-based APIs with REST Assured. Focuses on contract validation, authentication flows, test data, and integration-test boundaries rather than just request examples.
A practical guide to using k6 as a tool for validating performance hypotheses. Covers scenario design, thresholds, think time, workload modeling, CI integration, and common mistakes.
A practical guide to designing test data for unit, integration, and end-to-end testing through fixtures, factories, masking, and environment reset strategies.
How to test Vue components with Vue Testing Library and Vitest from the user's point of view. Covers rendered output, interactions, async UI, Pinia/Router integration, and how to avoid implementation-heavy tests.
How to use React Testing Library as a user-centered testing tool. Covers query priority, interaction tests, async UI, provider wrappers, and how to avoid excessive mocking.
A practical guide to TDD as a design feedback loop rather than a memorized procedure. Covers the meaning of Red-Green-Refactor, where it works best, where it can be too much, and how to apply it sustainably in real teams.
A practical guide to designing confidence instead of maximizing test count, covering the balance between unit, integration, contract, and E2E tests, flaky test control, CI gates, ownership, and operational policy.
How to use Playwright as a reliable E2E testing platform rather than just a browser automation tool. Covers strategy, configuration, selector rules, mocking, auth-state reuse, and practical ways to reduce flaky tests.
How to use Cypress as a reliable user-flow validation tool, not just a browser automation script. Covers selector strategy, network control, test data, and ways to reduce flaky tests.
A practical guide to Jest that goes beyond syntax. Covers what to unit test, how far mocking should go, and how to keep tests maintainable.