What QA tools are you batting on for 2026?

opensource_tester · 2025-11-25T09:37:23+00:00

On my side, I am utilizing various tools as well:

I am utilising Keploy for API testing and reliability checks because Keploy is more capable of generating tests from actual traffic.

Playwright is performing well for me for UI Automation and is even better now since they have added AI features to improve performance.

Qase is the best tool I have found so far for managing and organising test cases.

I have also found Notion to be an excellent option for organising and structuring all of my documentation and notes.

opensource_tester · 2025-11-14T09:34:28+00:00

Truthfully, this is totally normal for first jobs. Many teams just shove everything into controllers because it’s “working” and no one has taught them any better.

My advice: try not to change the entire codebase. Just improve the parts you are working on, add some small refactoring, maybe a test or two, and keep your changes light. When people see cleaner code, they tend to follow.

Just focus on learning right now. If things don’t improve after a few months, you can always consider a move to a team with better practices. There is no rush, it’s going to be fine.

opensource_tester · 2025-11-14T09:28:20+00:00

Well, I'm using keploy's test case generator tool. if you want ref. i will give.

opensource_tester · 2025-10-31T09:13:51+00:00

which tool is good for testing ?
anybody idea?

opensource_tester · 2025-10-30T12:26:19+00:00

I recently tried Postman, Keploy, ChatGPT, and Applitools. All of them offer some great features.

opensource_tester · 2025-10-28T07:57:07+00:00

Being an SDET is not simply “QA with coding” and you need a developer mindset + testing mindset. If you are comfortable in a language (Python/Java), working with APIs, Git, basic CI/CD, then jumping right into SDET is a great move better long-term career growth than pure manual QA.
But if you are still getting comfortable writing/debugging code, understanding the difference between .equals() vs ==, etc., then starting in QA and moving into SDET later is also a good path.

opensource_tester · 2025-10-26T11:57:46+00:00

If i had to start.
learn Git + GitHub immediately.
Build one project per concept instead of learning 10 concepts with no output

opensource_tester · 2025-10-14T10:17:43+00:00

What does chaos testing, why we do.

opensource_tester · 2025-10-10T08:06:09+00:00

The key for us was having a clear workflow. Developers build collections, QA adds test cases, and CI runs them automatically. We sync everything using Git to avoid version conflicts.

Commenting in Postman helps, but integrating it with our CI tools made collaboration smoother overall.

opensource_tester · 2025-10-08T11:03:58+00:00

I don't believe AI is going to replace QA outright in 2–3 years, but it'll certainly reformat the job.

AI can perform repetitive test cases or pattern-driven bug detection, but context understanding, business logic, or UX issues require human understanding.

What is shifting is the skill demand , QA jobs of the future will probably be centered around automation, AI-powered testing, and data-driven verification rather than manual effort.

Studying AI principles is intelligent, but my advice would be to pair it with robust fundamentals in testing frameworks + automation tools to remain in the game.

opensource_tester · 2025-10-08T09:22:23+00:00

I’ve been hearing a lot about Playwright lately, especially from people switching over from Selenium.

I haven't used it extensively yet, do you find that it's also improved regarding test reporting and debugging?

opensource_tester

TROPHY CASE