<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: QAlogy</title>
    <description>The latest articles on DEV Community by QAlogy (@qalogy).</description>
    <link>https://dev.to/qalogy</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2083562%2F9e107818-a20a-4136-9a74-821453a8593e.png</url>
      <title>DEV Community: QAlogy</title>
      <link>https://dev.to/qalogy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/qalogy"/>
    <language>en</language>
    <item>
      <title>10 Years in QA: The Journey I Never Expected to Have</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Sat, 04 Apr 2026 09:40:14 +0000</pubDate>
      <link>https://dev.to/qalogy/10-years-in-qa-the-journey-i-never-expected-to-have-53gn</link>
      <guid>https://dev.to/qalogy/10-years-in-qa-the-journey-i-never-expected-to-have-53gn</guid>
      <description>&lt;p&gt;This year I am celebrating 10 years since I started working as a QA.&lt;/p&gt;

&lt;p&gt;Ten years… It sounds like a lot when I say it out loud. But in my head, I can still clearly remember my first days on the job. Sitting in front of the screen, learning the functionalities of my first project, trying to think about some scenarios that I can try, opening a ticket…&lt;/p&gt;

&lt;p&gt;Back then, everything was new for me, and it was kind of confusing, scary, interesting, and exciting at the same time. Now, when I think of it, I have only positive and interesting memories.&lt;/p&gt;

&lt;p&gt;Where It All Started&lt;br&gt;
Back then, when I started in 2016, my job was simple.&lt;/p&gt;

&lt;p&gt;I would open a ticket from the board, read the description, and try to follow it as closely as possible. If something didn’t work, I would report a bug. When the developer fixed it, I would test it again.&lt;/p&gt;

&lt;p&gt;That cycle repeated every day. I had a couple of tickets ready for testing every day. I would go through that list, test them manually till the working day ends, and that was mostly it.&lt;/p&gt;

&lt;p&gt;At that time, I thought: “This is QA. This is what testing looks like.”&lt;/p&gt;

&lt;p&gt;Read the full post on my blog: &lt;a href="https://qalogy.com/10-years-in-qa-the-journey-i-never-expected-to-have/" rel="noopener noreferrer"&gt;https://qalogy.com/10-years-in-qa-the-journey-i-never-expected-to-have/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>testing</category>
      <category>discuss</category>
      <category>watercooler</category>
    </item>
    <item>
      <title>How I Passed ISTQB Foundation Level: What Worked, What Didn’t</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Fri, 20 Mar 2026 21:20:48 +0000</pubDate>
      <link>https://dev.to/qalogy/how-i-passed-istqb-foundation-level-what-worked-what-didnt-1b60</link>
      <guid>https://dev.to/qalogy/how-i-passed-istqb-foundation-level-what-worked-what-didnt-1b60</guid>
      <description>&lt;p&gt;After nearly 10 years of QA experience across different industries, I finally decided to take the ISTQB Foundation Level exam.&lt;/p&gt;

&lt;p&gt;This wasn’t something completely new to me. I had been thinking about getting the certification for a while, but never really found the right moment. I wanted to take the exam, but sometimes there were other priorities, and sometimes I didn’t have enough time to prepare. As time has flown, 10 years have passed, and I still haven’t applied to take the exam.&lt;/p&gt;

&lt;p&gt;So when an opportunity came up through my company, I saw it as the perfect time to finally do it.&lt;/p&gt;

&lt;p&gt;Read the full post on my blog: &lt;a href="https://qalogy.com/how-i-passed-istqb-foundation-level-what-worked-what-didnt/" rel="noopener noreferrer"&gt;https://qalogy.com/how-i-passed-istqb-foundation-level-what-worked-what-didnt/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>discuss</category>
      <category>learning</category>
      <category>istqb</category>
    </item>
    <item>
      <title>Test Data Management: The Problem No One Talks About</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Tue, 17 Mar 2026 22:07:37 +0000</pubDate>
      <link>https://dev.to/qalogy/test-data-management-the-problem-no-one-talks-about-33hb</link>
      <guid>https://dev.to/qalogy/test-data-management-the-problem-no-one-talks-about-33hb</guid>
      <description>&lt;p&gt;When a test fails, as QA engineers, we instinctively start debugging the test itself by checking the locators, adjusting the waits, looking for timing issues, or maybe adding waits or retries just to stabilize things.&lt;/p&gt;

&lt;p&gt;At first, it feels logical. After all, the test failed — so the test must be the problem.&lt;/p&gt;

&lt;p&gt;But in many cases, that assumption is wrong.&lt;/p&gt;

&lt;p&gt;The real issue is often something less visible, something we don’t immediately question. And that issue is often bad or inconsistent test data.&lt;/p&gt;

&lt;p&gt;Read the full post on my blog: &lt;a href="https://qalogy.com/test-data-management-the-problem-no-one-talks-about/" rel="noopener noreferrer"&gt;https://qalogy.com/test-data-management-the-problem-no-one-talks-about/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>automation</category>
      <category>software</category>
      <category>qa</category>
    </item>
    <item>
      <title>The Hidden Cost of Flaky Tests Nobody Puts in the Sprint Report</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Sun, 25 Jan 2026 21:12:03 +0000</pubDate>
      <link>https://dev.to/qalogy/the-hidden-cost-of-flaky-tests-nobody-puts-in-the-sprint-report-io9</link>
      <guid>https://dev.to/qalogy/the-hidden-cost-of-flaky-tests-nobody-puts-in-the-sprint-report-io9</guid>
      <description>&lt;p&gt;Every QA team has that moment.&lt;/p&gt;

&lt;p&gt;Someone runs the automated tests, and suddenly some of them fail. They fail once, then pass on the next run. Or the third. Or after a small tweak. Someone reruns the pipeline, the build turns green, and the team moves on. No ticket is created. No task is added to the sprint. Nothing appears in the report.&lt;/p&gt;

&lt;p&gt;And that is exactly why flaky tests are so dangerous.&lt;/p&gt;

&lt;p&gt;They don’t stop delivery immediately. But the cost doesn’t disappear. It just moves underground. They slowly drain trust, focus, and energy — until one day the entire test suite is questioned.&lt;/p&gt;

&lt;p&gt;Read the full post on my blog: &lt;a href="https://qalogy.com/the-hidden-cost-of-flaky-tests-nobody-puts-in-the-sprint-report/" rel="noopener noreferrer"&gt;https://qalogy.com/the-hidden-cost-of-flaky-tests-nobody-puts-in-the-sprint-report/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>automation</category>
      <category>software</category>
      <category>agile</category>
    </item>
    <item>
      <title>When a Test Passes but the Feature Is Broken: A QA Reality Check</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Mon, 19 Jan 2026 18:33:30 +0000</pubDate>
      <link>https://dev.to/qalogy/when-a-test-passes-but-the-feature-is-broken-a-qa-reality-check-1f93</link>
      <guid>https://dev.to/qalogy/when-a-test-passes-but-the-feature-is-broken-a-qa-reality-check-1f93</guid>
      <description>&lt;p&gt;The build is green, all automated tests have passed, and the pipeline finished without any warnings. At this point, the feature is marked as ready to move forward. From the outside, everything appeared exactly as modern software delivery is supposed to look.&lt;/p&gt;

&lt;p&gt;Then the app was opened.&lt;/p&gt;

&lt;p&gt;A tester logged in, navigated to the feature, and performed the exact action covered by the automated test. The confirmation message appeared, just like the test expected. Everything looked correct at first.&lt;/p&gt;

&lt;p&gt;But when the tester left the screen and came back, the change was gone.&lt;/p&gt;

&lt;p&gt;The action had never been saved. No error was shown. No warning appeared. From the user’s perspective, the app simply ignored what they had done. The automated test had passed because the UI responded correctly at the moment, but the system state never changed.&lt;/p&gt;

&lt;p&gt;The feature worked just long enough to fool the test.&lt;/p&gt;

&lt;p&gt;This is one of those moments that every QA engineer recognizes immediately. The uncomfortable realization that follows is always the same:&lt;/p&gt;

&lt;p&gt;The tests passed, but the feature is broken.&lt;/p&gt;

&lt;p&gt;Read the full post on my blog: &lt;a href="https://qalogy.com/when-a-test-passes-but-the-feature-is-broken/" rel="noopener noreferrer"&gt;https://qalogy.com/when-a-test-passes-but-the-feature-is-broken/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>automation</category>
      <category>softwaredevelopment</category>
      <category>testing</category>
    </item>
    <item>
      <title>QA Spotlight: Taia Dimitrova — How a QA Engineer Built a Telegram Bot with AI and Engineering Thinking</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Mon, 19 Jan 2026 18:32:04 +0000</pubDate>
      <link>https://dev.to/qalogy/qa-spotlight-taia-dimitrova-how-a-qa-engineer-built-a-telegram-bot-with-ai-and-engineering-5end</link>
      <guid>https://dev.to/qalogy/qa-spotlight-taia-dimitrova-how-a-qa-engineer-built-a-telegram-bot-with-ai-and-engineering-5end</guid>
      <description>&lt;p&gt;In this QA Spotlight edition, I feature a refreshing and very modern perspective on what it means to be a QA engineer today.&lt;/p&gt;

&lt;p&gt;This post tells the story of how a QA engineer turned a personal frustration — constantly missing good theatre tickets — into a fully functional Telegram bot that monitors theatre websites and sends notifications automatically. The twist? The bot wasn’t built in the traditional “write everything by hand” way.&lt;/p&gt;

&lt;p&gt;Instead, ChatGPT was used for brainstorming and architecture, while Copilot was utilized for implementation. The QA engineer orchestrated everything, defining the flow, validating logic, handling edge cases, resolving deployment issues, and shaping the overall quality of the solution.&lt;/p&gt;

&lt;p&gt;Read more about it in my blog post: &lt;a href="https://qalogy.com/qa-spotlight-taia-dimitrova/" rel="noopener noreferrer"&gt;https://qalogy.com/qa-spotlight-taia-dimitrova/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>testing</category>
      <category>programming</category>
    </item>
    <item>
      <title>Top Automation Anti-Patterns to Avoid (With Real Examples)</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Mon, 01 Dec 2025 20:35:59 +0000</pubDate>
      <link>https://dev.to/qalogy/top-automation-anti-patterns-to-avoid-with-real-examples-cjm</link>
      <guid>https://dev.to/qalogy/top-automation-anti-patterns-to-avoid-with-real-examples-cjm</guid>
      <description>&lt;p&gt;Automation frameworks are becoming more powerful, scalable, and AI-assisted. But, even today, the same types of failures continue to appear across teams: flaky tests, slow pipelines, unstable locators, and brittle architecture.&lt;/p&gt;

&lt;p&gt;These issues rarely come from the tools themselves. Usually, they come from using specific anti-patterns that repeat again and again across projects.&lt;/p&gt;

&lt;p&gt;Because automation is not just about writing tests — it’s about writing good tests, designing test architecture, thinking about maintainability, and making long-term decisions. Unfortunately, some QAs still fall into dangerous habits that slowly destroy the reliability of their framework.&lt;/p&gt;

&lt;p&gt;Let’s go through the most damaging automation anti-patterns, understand why they happen, what they cause, and how to fix them.&lt;/p&gt;

&lt;p&gt;Read more about that on my blog: &lt;a href="https://qalogy.com/top-automation-anti-patterns-to-avoid/" rel="noopener noreferrer"&gt;https://qalogy.com/top-automation-anti-patterns-to-avoid/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>software</category>
      <category>automation</category>
      <category>coding</category>
    </item>
    <item>
      <title>The First 5 Minutes of Bug Investigation: How to Do It Right</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Mon, 01 Dec 2025 20:34:17 +0000</pubDate>
      <link>https://dev.to/qalogy/the-first-5-minutes-of-bug-investigation-how-to-do-it-right-1i6k</link>
      <guid>https://dev.to/qalogy/the-first-5-minutes-of-bug-investigation-how-to-do-it-right-1i6k</guid>
      <description>&lt;p&gt;There is one moment that every QA knows well… you are testing, and something behaves differently than expected. Suddenly, you’re staring at a bug that wasn’t supposed to exist. That first moment — those first five minutes of investigation — can determine whether you uncover the root cause quickly or get lost and waste time.&lt;/p&gt;

&lt;p&gt;Bug investigation isn’t about panicking, guessing, or immediately running to create a ticket. The first few minutes are about gathering clarity, removing the unnecessary details, determining the cause, and understanding the behavior before it slips away. If you use these moments well, the rest of the investigation becomes faster, much more accurate, and you will save a lot of time.&lt;/p&gt;

&lt;p&gt;Read the full blog post on my blog: &lt;a href="https://qalogy.com/the-first-5-minutes-of-bug-investigation-how-to-do-it-right/" rel="noopener noreferrer"&gt;https://qalogy.com/the-first-5-minutes-of-bug-investigation-how-to-do-it-right/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>software</category>
      <category>discuss</category>
      <category>learning</category>
    </item>
    <item>
      <title>The New QA Mindset: Testing AI and LLMs</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Wed, 19 Nov 2025 21:22:10 +0000</pubDate>
      <link>https://dev.to/qalogy/the-new-qa-mindset-testing-ai-and-llms-edo</link>
      <guid>https://dev.to/qalogy/the-new-qa-mindset-testing-ai-and-llms-edo</guid>
      <description>&lt;p&gt;For years, QA engineers have tested deterministic systems — applications that behave predictably when given specific inputs. But with the rise of AI-driven apps and large language models (LLMs), the rules have changed. The systems we’re testing today are not predictable. They’re probabilistic, data-driven, and can behave differently even when nothing in the code has changed.&lt;/p&gt;

&lt;p&gt;That’s why we, as QA professionals, need a new mindset.&lt;/p&gt;

&lt;p&gt;Read the full article on my blog, QAlogy.com: &lt;a href="https://qalogy.com/the-new-qa-mindset-testing-ai-and-llms/" rel="noopener noreferrer"&gt;https://qalogy.com/the-new-qa-mindset-testing-ai-and-llms/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>ai</category>
      <category>llm</category>
      <category>discuss</category>
    </item>
    <item>
      <title>I Was a Guest on the Tech Savvy Talks Podcast!</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Wed, 19 Nov 2025 21:20:58 +0000</pubDate>
      <link>https://dev.to/qalogy/i-was-a-guest-on-the-tech-savvy-talks-podcast-4i6</link>
      <guid>https://dev.to/qalogy/i-was-a-guest-on-the-tech-savvy-talks-podcast-4i6</guid>
      <description>&lt;p&gt;I recently had the pleasure of being a guest on the Tech Savvy Talks podcast, hosted by my Technology Team Lead, Kiro Kosturanov, where we had an amazing conversation about how Quality Assurance (QA) goes far beyond “just testing.”&lt;/p&gt;

&lt;p&gt;We discussed how QA plays a crucial role in building successful products — from early involvement in development to enhancing usability and ensuring a seamless user experience.&lt;/p&gt;

&lt;p&gt;Some of the topics we covered:&lt;br&gt;
🔹 The four pillars of QA: role, skills, boosters, and personal growth&lt;br&gt;
🔹 Why QA should be part of the process from day one&lt;br&gt;
🔹 The right balance between manual testing, automation, and exploratory testing&lt;br&gt;
🔹 How QA contributes to usability and product quality, not just bug detection&lt;br&gt;
🔹 Why QA is a career path in its own right&lt;/p&gt;

&lt;p&gt;This episode is perfect for anyone interested in how great products are built — whether you’re a developer, QA, product manager, or just curious about the process.&lt;/p&gt;

&lt;p&gt;🎧 You can watch the full episode on YouTube:&lt;br&gt;
&lt;iframe width="710" height="399" src="https://www.youtube.com/embed/45DW0nBz3jU"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;A huge thank you to my company, Scalefocus, for organizing this podcast and giving me the opportunity to share my experience and perspective on the QA role. 🙌&lt;/p&gt;

&lt;p&gt;Visit my blog QAlogy.com for more interesting topics related to Quality Assurance: &lt;a href="https://qalogy.com/" rel="noopener noreferrer"&gt;https://qalogy.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>discuss</category>
      <category>community</category>
      <category>podcast</category>
    </item>
    <item>
      <title>What QA Can Learn from Doctors, Athletes, and Pilots</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Wed, 19 Nov 2025 21:18:34 +0000</pubDate>
      <link>https://dev.to/qalogy/what-qa-can-learn-from-doctors-athletes-and-pilots-17lg</link>
      <guid>https://dev.to/qalogy/what-qa-can-learn-from-doctors-athletes-and-pilots-17lg</guid>
      <description>&lt;p&gt;The work of Quality Assurance is not about clicking through the app, running scripts, or ticking checkboxes. As QA, you are the first real user of the product, who is giving feedback not just on defects but on product value, usability, intuitiveness, and user flows. The best testers think differently — they borrow skills and mindsets, and take inspiration from fields outside tech. In fact, QA has a lot in common with doctors, athletes, and pilots. Even though their work is completely different, there are a lot of similarities in their mindset and way of thinking.&lt;/p&gt;

&lt;p&gt;Read more about it on my blog QALOGY.COM: &lt;a href="https://qalogy.com/what-qa-can-learn-from-doctors-athletes-and-pilots/" rel="noopener noreferrer"&gt;https://qalogy.com/what-qa-can-learn-from-doctors-athletes-and-pilots/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>software</category>
      <category>discuss</category>
      <category>learning</category>
    </item>
    <item>
      <title>Celebrating 1 Year of QAlogy: From Idea to Reality</title>
      <dc:creator>QAlogy</dc:creator>
      <pubDate>Sat, 09 Aug 2025 08:47:29 +0000</pubDate>
      <link>https://dev.to/qalogy/celebrating-1-year-of-qalogy-from-idea-to-reality-2kp3</link>
      <guid>https://dev.to/qalogy/celebrating-1-year-of-qalogy-from-idea-to-reality-2kp3</guid>
      <description>&lt;p&gt;Exactly one year ago, something that had lived in my head for years became reality. QAlogy.com was created.&lt;/p&gt;

&lt;p&gt;It wasn’t just the launch of a website.&lt;br&gt;
It was the beginning of something I’ve always dreamed about — having my own space on the internet.&lt;/p&gt;

&lt;p&gt;Why I Started QAlogy?&lt;br&gt;
For a long time, I wanted to have my own corner online.&lt;br&gt;
A place where I could write.&lt;br&gt;
Where I could share what I know.&lt;br&gt;
Where I could help others, communicate with people in the QA world, and express myself creatively.&lt;/p&gt;

&lt;p&gt;So, one year ago, QAlogy wasn’t a brand. It wasn’t a community.&lt;br&gt;
It wasn’t even a real website. It was just… a blank screen.&lt;/p&gt;

&lt;p&gt;And from that blank screen, I created everything — piece by piece:&lt;/p&gt;

&lt;p&gt;I chose the colors&lt;br&gt;
Designed the logo&lt;br&gt;
Built the website&lt;br&gt;
Picked the fonts&lt;br&gt;
Wrote the content&lt;br&gt;
Hit “Publish” for the first time&lt;br&gt;
And just like that — QAlogy was live.&lt;/p&gt;

&lt;p&gt;What Happened in This First Year?&lt;br&gt;
A lot.&lt;/p&gt;

&lt;p&gt;From that first post to today, I’ve:&lt;/p&gt;

&lt;p&gt;Published a lot of blog posts (some planned, some spontaneous, all from the heart)&lt;br&gt;
Redesigned the blog once to keep things fresh and better organized.&lt;br&gt;
Got my posts shared by other QA professionals from Serbia, Germany, and beyond.&lt;br&gt;
Was featured by LambdaTest and SoftwareTestingWeekly — who included my content in their newsletter (huge thank you to them!)&lt;br&gt;
I was invited to be a guest on the Tech-Savvy podcast in Bulgaria by Scalefocus, where I shared my story and talked about QAlogy and other QA related topics (the episode will be published around the end of September). Huge thanks to Scalefocus and my Team Lead, Kiro Kosturanov, for the support.&lt;br&gt;
Met some truly amazing people from the QA community — people I wouldn’t have connected with if this blog didn’t exist.&lt;br&gt;
Grew my LinkedIn following by nearly 300% thanks to the blog and the support from the community.&lt;br&gt;
What I’ve Learned&lt;br&gt;
Starting something from scratch is hard — but incredibly rewarding.&lt;br&gt;
It’s okay not to have everything figured out. Just start.&lt;br&gt;
Writing consistently helps you grow — not just as a QA, but as a thinker and communicator.&lt;br&gt;
There’s a whole world of amazing QA people out there — willing to support, engage, and share.&lt;br&gt;
What’s Coming Next?&lt;br&gt;
As QAlogy enters its second year, I’m excited to keep building and improving.&lt;/p&gt;

&lt;p&gt;I have a few ideas I’d love to explore in the near future, such as:&lt;/p&gt;

&lt;p&gt;Creating a QA course.&lt;br&gt;
Writing more in-depth articles on some advanced testing topics.&lt;br&gt;
Featuring stories and interviews from other QA professionals.&lt;br&gt;
Possibly starting a newsletter for those who want to stay updated and inspired.&lt;br&gt;
These are just ideas for now, but I’m really looking forward to seeing where QAlogy goes next — and I’m always open to feedback, suggestions, and collaborations along the way.&lt;/p&gt;

&lt;p&gt;Thank You&lt;br&gt;
To every single person who:&lt;/p&gt;

&lt;p&gt;Visited QAlogy.com&lt;br&gt;
Read even one post&lt;br&gt;
Shared an article&lt;br&gt;
Reached out with a message&lt;br&gt;
Supported me online or offline&lt;br&gt;
Thank you !!!&lt;br&gt;
You helped turn a blank website into something real.&lt;/p&gt;

&lt;p&gt;Let’s keep going. Let’s keep testing, learning, and sharing.&lt;br&gt;
Here’s to Year 2 of QAlogy.com!&lt;/p&gt;

&lt;p&gt;Visit QAlogy here: &lt;a href="https://qalogy.com/" rel="noopener noreferrer"&gt;https://qalogy.com/&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;– Vladimir Josifoski&lt;br&gt;
Founder of QAlogy.com&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>community</category>
      <category>networking</category>
      <category>career</category>
    </item>
  </channel>
</rss>
