# 🔍 Weekly Testing Topic: What's trending in QA this week?

**URL:** <https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026>\
**Category:** Miscellaneous\
**Created:** [June 23, 2026, 2:00am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026 "2026-06-23T02:00:07Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![nghi.phan](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/nghi.phan/32/30970_2.png) [@nghi.phan](https://forum.katalon.com/u/nghi.phan)\
**Post date:** [June 23, 2026, 2:00am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/1 "2026-06-23T02:00:07Z")

</div>

Every week we spotlight a trending topic in software testing and QA. This week’s topic is one the community has been buzzing about **Flaky tests aren’t actually flaky** share your experience, ask questions, and let’s learn from each other!

**This week’s discussion:**

What’s your team’s approach to this testing challenge? Have you experimented with new tools or methodologies? What’s worked, what hasn’t?

Drop your thoughts below — there are no wrong answers, only shared experiences that help us all grow as quality engineers.

---

<div class="post-metadata">

**Author:** ![Monty\_Bagati](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/monty_bagati/32/33047_2.png) [@Monty\_Bagati](https://forum.katalon.com/u/Monty_Bagati)\
**Post date:** [June 23, 2026, 5:31am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/2 "2026-06-23T05:31:58Z")

</div>

I am currently working on a tool named Open Text CSDP (aka Value Edge) : fantastic central test management tool

---

<div class="post-metadata">

**Author:** ![nghi.phan](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/nghi.phan/32/30970_2.png) [@nghi.phan](https://forum.katalon.com/u/nghi.phan)\
**Post date:** [June 23, 2026, 5:54am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/3 "2026-06-23T05:54:59Z")

</div>

Please share your progress with us ^^

---

<div class="post-metadata">

**Author:** ![sneha.sajeev](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/sneha.sajeev/32/29015_2.png) [@sneha.sajeev](https://forum.katalon.com/u/sneha.sajeev)\
**Post date:** [June 23, 2026, 9:10am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/4 "2026-06-23T09:10:44Z")

</div>

In my experience, many “flaky tests” are not actually flaky. They often expose underlying issues in the application, test environment, or test design.

Some common causes I’ve encountered include:

- Timing and synchronization issues where elements are not fully loaded before interaction.

- Test data dependencies between test runs.

- Environment instability, especially when multiple teams are using the same environment.

- Dynamic UI elements and asynchronous API responses.

- Locator strategies that are too dependent on changing UI attributes.

What has worked for our team:

- Using explicit waits instead of fixed delays.

- Improving test data management and test isolation.

- Reviewing failures before simply rerunning tests.

- Collaborating with developers to determine whether failures indicate actual application issues.

One lesson I’ve learned is that repeatedly rerunning failed tests can hide real defects. When a test fails intermittently, we try to investigate the root cause rather than immediately labeling it as a flaky test.

I’m curious to hear how other teams distinguish between a genuinely flaky test and a product defect that only appears under certain conditions.

---

<div class="post-metadata">

**Author:** ![Monty\_Bagati](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/monty_bagati/32/33047_2.png) [@Monty\_Bagati](https://forum.katalon.com/u/Monty_Bagati)\
**Post date:** [June 23, 2026, 11:20am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/5 "2026-06-23T11:20:29Z")

</div>

I mean it’s a well thought central test management tool, been working a lot on this

---

<div class="post-metadata">

**Author:** ![nghi.phan](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/nghi.phan/32/30970_2.png) [@nghi.phan](https://forum.katalon.com/u/nghi.phan)\
**Post date:** [June 25, 2026, 3:59am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/6 "2026-06-25T03:59:22Z")

</div>

> [@Monty\_Bagati](#):
>
> currently working on a tool named Open Text CSDP (aka Value Edge) : fantastic central test management tool

please do share more with us 🤩

---

<div class="post-metadata">

**Author:** ![arvind.choudhary](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/arvind.choudhary/32/33165_2.png) [@arvind.choudhary](https://forum.katalon.com/u/arvind.choudhary)\
**Post date:** [June 25, 2026, 11:24am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/7 "2026-06-25T11:24:53Z")

</div>

As per me the flaky tests often tell us something important about our system design or test strategy—we just need to listen carefully and investigate deeper.

---

<div class="post-metadata">

**Author:** ![arvind.choudhary](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/arvind.choudhary/32/33165_2.png) [@arvind.choudhary](https://forum.katalon.com/u/arvind.choudhary)\
**Post date:** [June 25, 2026, 11:26am UTC](https://forum.katalon.com/t/weekly-testing-topic-whats-trending-in-qa-this-week/192026/8 "2026-06-25T11:26:04Z")

</div>

Flaky” exposes issues like timing gaps, shared test data, or environment instability.
