# Which Web & Mobile automation tool, framework people are using at the moment?

**URL:** <https://club.ministryoftesting.com/t/which-web-mobile-automation-tool-framework-people-are-using-at-the-moment/85701>\
**Category:** Discussions\
**Tags:** tools, learning, automation, process\
**Created:** [4 July 2025 21:48 UTC](https://club.ministryoftesting.com/t/which-web-mobile-automation-tool-framework-people-are-using-at-the-moment/85701 "2025-07-04T21:48:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![aimantirmizi](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/aimantirmizi/32/15210_2.png) [@aimantirmizi](https://club.ministryoftesting.com/u/aimantirmizi)\
**Post date:** [4 July 2025 21:48 UTC](https://club.ministryoftesting.com/t/which-web-mobile-automation-tool-framework-people-are-using-at-the-moment/85701/1 "2025-07-04T21:48:01Z")

</div>

I am interested to know what tools and automation framework people are currently using to automate web and mobile most importantly how people decide that we should use this?

Looking forward to know your thoughts:

- What are the new tools in the market that we are after?
- Easy to integrate / setup?
- Which tools you think is a gem and MUST learn these days?

We had a topic the past: [AI + no Code automation tools](https://club.ministryoftesting.com/t/what-ai-based-no-code-automation-tool-are-you-currently-using/85504)

Thanks! 😊

---

<div class="post-metadata">

**Author:** ![fayeezahmed](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/fayeezahmed/32/11307_2.png) [@fayeezahmed](https://club.ministryoftesting.com/u/fayeezahmed)\
**Post date:** [5 July 2025 13:49 UTC](https://club.ministryoftesting.com/t/which-web-mobile-automation-tool-framework-people-are-using-at-the-moment/85701/2 "2025-07-05T13:49:41Z")

</div>

Playwright for web with Typescript.

Considerations I made when deciding :

- needs to be stable
- Needs to be fast
- Big community
- Good documentation
- Good support from the framework team
- 

I got tired of Selenium based frameworks, although I know Selenium v4 does also use dev tools protocol like Playwright, we were already investing into playwright so I haven’t checked that out properly.

---

<div class="post-metadata">

**Author:** ![Pritigaikwad](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/pritigaikwad/32/14918_2.png) [@Pritigaikwad](https://club.ministryoftesting.com/u/Pritigaikwad)\
**Post date:** [11 July 2025 13:45 UTC](https://club.ministryoftesting.com/t/which-web-mobile-automation-tool-framework-people-are-using-at-the-moment/85701/3 "2025-07-11T13:45:22Z")

</div>

From what I’m seeing across teams lately, tools like **Playwright** and **Cypress** are becoming really popular for web automation—mainly because they’re fast, reliable, and easy to integrate into modern dev workflows. That said, **Selenium** still holds its ground, especially for legacy systems or when cross-browser support is a must.

For mobile automation, **Appium** is still the top choice, especially when there’s a need to test both Android and iOS with a single codebase. Some teams also experiment with tools like **Detox** or **Espresso** , depending on whether the focus is on native performance or CI-friendly setups.

When it comes to frameworks, I often see a mix— **TestNG** , **JUnit** , **Cucumber** , and even custom-built setups that combine reporting, CI/CD hooks, and cloud device labs. At the end of the day, the “best” tool often comes down to the project’s needs, team familiarity, and how well the tool fits into the overall QA process.

---

<div class="post-metadata">

**Author:** ![aimantirmizi](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/aimantirmizi/32/15210_2.png) [@aimantirmizi](https://club.ministryoftesting.com/u/aimantirmizi)\
**Post date:** [11 July 2025 21:42 UTC](https://club.ministryoftesting.com/t/which-web-mobile-automation-tool-framework-people-are-using-at-the-moment/85701/4 "2025-07-11T21:42:30Z")

</div>

Yes, thats what we are using as well Cypress. In my previous role for mobile we had used Cucumber + Appium with JUnit.

We have also started using gitHub copilot - its like a code buddy these days 😃

Its amazing to hear different perspective. Thanks for sharing 💜

---

<div class="post-metadata">

**Author:** ![ramanan49](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/ramanan49/32/15686_2.png) [@ramanan49](https://club.ministryoftesting.com/u/ramanan49)\
**Post date:** [12 July 2025 01:49 UTC](https://club.ministryoftesting.com/t/which-web-mobile-automation-tool-framework-people-are-using-at-the-moment/85701/5 "2025-07-12T01:49:56Z")

</div>

@aimantirmizi  
Great questions—very relevant in today’s automation landscape!

What I discern from the communities and the current projects is that **Web automation** is still largely dominated by **Selenium** under various frameworks like TestNG, JUnit, and Cucumber; however, **Playwright** and **Cypress** have lately seen a resurgence given their speed and reliability and built-in capabilities. **Appium** is still very much in vogue for **mobile automation** , but things are opening up, with tools such as **Detox** for React Native and **Maestro** being more and more commonly eyed.

Choices come down usually to the following parameters:

- Skillset of the team

- Type of app (native/hybrid/web)

- Compatibility with their CI/CD pipeline

- Community support and documentation

Concerning the relatively new tools, **Playwright** has been somewhat of a gem that is being embraced by many testers—is capable of multi-browser testing, is fast, and works excellently with modern frameworks. On the mobile side, **Maestro** rates high in ease of setup and fits well into fast release cycles.

AI + no-code automation tools are indeed the hype these days. Test platforms like **Testim** , **Katalon** , and even **mabl** make their marks in places where groups want to sort of enable non-coders to contribute to testing.

Cheers,  
Ramanan
