Smoke testing vs Sanity testing : 1 telling difference to free your mind

chocolate bar and a granola bar being placed side by side

🔍 Excerpt:
In the world of software testing, “Smoke” and “Sanity” testing are often confused—but understanding the distinction between the two is essential for any QA professional, especially freshers. While both are forms of quick, surface-level testing, they serve different purposes at different stages of the software lifecycle. This blog breaks down the key differences, provides real-world examples, and clarifies when and why each should be used. Whether you’re preparing for an interview or refining your testing strategy, this guide will help you speak the language of quality with confidence.

Generative AI with Ollama: 1 LLM that is’nt so scary

getting feet wet

The author discusses the rise of generative AI tools like ChatGPT and privacy concerns related to prompts. They recommend using Ollama as an open-source alternative that can run locally. The installation process can be challenging, especially for beginners with insufficient memory. Finally, they caution against blindly trusting generative AI for coding tasks.

False Dichotomy: 2 techniques to transform Zombie Testers to Creative Testers

Hands with yes and no labels

The blog discusses the issue of false dichotomy in software testing, emphasizing the limitations of traditional pass/fail metrics. It advocates for more dynamic methodologies like exploratory and rapid testing, which encourage creativity and risk assessment. The post encourages a holistic approach to software quality and promotes collaboration among testing teams.

Understanding Logs as Part of Your Expected Results

Tower

This post discusses a login test case in software testing, emphasizing the need for a comprehensive understanding beyond just expected outcomes. It highlights the importance of analyzing logs and background processes, as part of the test report for every expected result? Suggesting that while automation can assist with lower-priority cases, high-priority tests should begin with manual execution to ensure thoroughness.