2 posts tagged with "Smoke Testing"

Test Automation: A Practical Guide to Getting Started

Co-Founder and CEO, DevAssure

TL;DR

Automate the repetitive, well-defined checks so people can focus on judgment work. Keep a healthy testing pyramid, start with smoke tests in CI, and treat flaky/false failures as urgent. AI-driven tools like DevAssure O2 mainly cut E2E brittleness and authoring cost — they do not replace deciding what is worth testing.

Manual QA doesn't scale with a growing codebase. Every new feature adds another set of paths someone has to click through by hand, and every release means re-checking that nothing old broke. Test automation exists to break that tradeoff — but only if it's built the right way. Here's a practical, in-depth look at what test automation actually involves, where teams typically go wrong, how to think about tooling choices, and what's changed recently with AI-driven approaches.

Smoke Test: What It Is, Why It Matters, and How to Automate It

Divya Manohar

Co-Founder and CEO, DevAssure

TL;DR

A smoke test is a short, shallow check that a new build is usable — load, login, core paths — so you fail in minutes, not after a full regression. Keep it tagged, run it first in CI, and automate it with plain-English cases in DevAssure O2 instead of brittle selectors.

If a build breaks in an obvious way — the login page won't load, the checkout flow throws a 500, the dashboard is a blank white screen — you want to know in minutes, not after a full regression suite finishes hours later. That's the job of a smoke test.