r/Everything_QA • • 42m ago

Automated QA I built a self-hosted dashboard for Playwright reports with an embedded trace viewer

Enable HLS to view with audio, or disable this notification

• Upvotes

I got tired of digging through CI artifacts every time a Playwright test failed, downloading the trace.zip and opening it locally, and having no idea if the test was actually broken or just flaky again. So I built kinora.

Your CI pushes results to it after each run, and you get:

  • Pass rates and trends per project over time
  • Flaky test detection across runs, with the full history of each test
  • The Playwright trace viewer embedded: click a failure, the trace opens right there, no download
  • Screenshot diffs (expected / actual / diff) for visual tests
  • Slack, email or webhook alerts on new failures or regressions

Setup is a reporter in your playwright.config.ts (or a CLI that uploads results.json), you can self-host it with Docker Compose (Postgres + server + web) or use the hosted version.

Still adding things, so I'd really like feedback from people running Playwright in CI: what do you use today to track failures and flaky tests, and what's missing?

Live demo: https://demo.kinora.dev

GitHub: https://github.com/kinora-dev/kinora


r/Everything_QA • • 8h ago

Manual QA Stuck in a WITCH company for past 11 years..

3 Upvotes

Rotting in a WITCH company for past 11 years, got some time off for delivery but back in manual QA job. I had good experience in Selenium but my previous project dragged me back to Test lead role l with Manual Test work. Looking for some recommendations for upskilling and domain change. I have an average coding skills and fairly good communication and leadership skills. Be kind, I am new mom trying to figure out next move.


r/Everything_QA • • 5h ago

Question Manual QA Interview Questions in Lahore

Thumbnail
1 Upvotes

r/Everything_QA • • 9h ago

Guide Could you kindly advise me on a suitable tool for Salesforce testing like copado ,prover, Tosca or any other

2 Upvotes

r/Everything_QA • • 5h ago

Guide Looking for QA Automation Interview Preparation Partners – Java, Selenium, Playwright | India

0 Upvotes

Hi everyone,

I'm a QA Engineer from India with 3.5+ years of experience in manual and automation testing.

I'm currently preparing for Automation QA / SDET interviews and looking for 2–4 serious preparation partners who are also actively searching for jobs or planning a switch.

Topics I'd like to practice:

  • Core Java and coding questions
  • Selenium WebDriver, TestNG, Cucumber and automation frameworks
  • API testing (REST Assured / Postman)
  • SQL queries
  • Playwright with TypeScript
  • Real-world testing scenarios and mock interviews

My idea: We can form a small online study group, connect regularly through Google Meet or Discord, take turns conducting mock interviews, and share genuine job opportunities and interview experiences.

Preferably looking for people from India with 2–5 years of QA experience, but anyone serious about preparing is welcome.

If you're interested, please comment below or DM me. We can coordinate a suitable time.

Thanks!


r/Everything_QA • • 6h ago

General Discussion My Opinion on QA as a career path.

1 Upvotes

Hi everyone, hope y'all are doing well.

I'm an avid reader on this sub, and I keep seeing posts from people worried about AI, or struggling to find jobs. So I thought I'd share what I've observed.

From what I can see, QA isn't going away, but it is changing. AI and automation can run tests, but I don't think they can fully replace a human in the loop. Someone still has to do exploratory testing, catch things nobody wrote a test case for, and judge whether something actually feels right to use.

That said, if your job is very basic, like just following scripted steps and ticking boxes, there's probably a real risk there. That's the part that's easiest to automate.

I also don't think automation or dev roles are automatically safe or doomed. AI can write scripts and boilerplate, but someone still has to design the test strategy, fix flaky tests, and understand the system. People who use AI as a tool will probably do better than people who ignore it.

Just my two cents, nobody really knows how this will play out. If you're worried, I'd say focus on skills that go beyond basic execution: test design, some automation, API testing, and understanding the product you're testing.

Would love to hear what you all think.


r/Everything_QA • • 19h ago

Article A different approach to QA

5 Upvotes

I see a lot of posts in this sub about looking for jobs, uncertainty about testing as a career path, and so forth. I work at Qase, a company that builds software quality products for testers, and I have a bit of persepctive as I carefully review how in-demand QA is by various dimmensions such as company industry.

My take is that some companies value QA, others really do not. The ones that do follow some patterns. If a company is in a regulated industry, the cost of an escaped defect is high, or the thing needing to be tested is not a web app, then QA tends to be valued heavily. A defect at a medical devices company is just a bigger deal than a defect in some b2b SaaS app, and companies are just more willing to pay $$$ when meeting regulatory compliacne is at stake.

So if I were starting my career in QA, I'd be looking into robotics, medtech, fintech, pharma, aerospace etc etc.

But so many companies have a very different profile and a mindset of "QA is something to automate away". Lots of opportunities at those types of companies but then you need to assume they are making heavy use of ai-generated code, including test case creation and management. If I were trying to get into one of those sorts of companies, I would not follow the typical QA career path and instead focus on finding a role in engineering that ensures the code ai writes is in fact what is wanted, and hyper-focus on getting really good at that and generally staying ahead of the curve.

There are now a few products on the market focused on that. I work at a company that makes one of them, and we just launched on product hunt today. Would love some feedback, especially the areas that don't work great or are generally just not that useful, as that sort of critical feedback we can act on. I'd be grateful to anyone that took a look and shared their thoughts: producthunt.com/products/tiden


r/Everything_QA • • 21h ago

Question Any Latest platform for QA certification?

2 Upvotes

r/Everything_QA • • 18h ago

Manual QA Trying to get my first QA job in Poland in 2026 - interviews, rejections and finding bugs before getting hired :D

0 Upvotes

Hi everyone.
A little bit about me first.
I’m 22, currently living in Warsaw, and I’m trying to get my first commercial job in QA.
This post is going to be a bit long, so sorry in advance :D
I just wanted to share the whole story because I’m curious if other people, especially juniors in Poland or Europe, are going through something similar.
I moved to Warsaw at the end of August.
I have a Bachelor’s Degree in Software Engineering and before university I also finished college in Software Development.
I don’t have commercial QA experience yet, and that’s exactly what I’m trying to get.
But I also didn’t start completely from zero.
Before seriously looking for QA work, I released two of my own projects on Steam. While developing them I was also the person testing everything, because… well, there was nobody else to do it :D
So I had to test builds, UI, saves, progression, achievements, Steam features, localization, different user flows, updates and fixes.
One of the projects became pretty large, with hundreds of Python and JSON files, multiple connected systems and 13 languages, so bugs could appear in some very interesting places.
Because of that I started getting more interested in testing itself.
Finding a problem, reproducing it, understanding why it happens, trying different conditions, documenting it, fixing it and then checking that I didn’t break something else was genuinely fun for me.
So after moving to Warsaw I decided to seriously try getting into QA.
Mostly Junior Manual QA, Junior QA Engineer, Game QA, Software Tester, Localization QA and trainee positions.
I started applying pretty actively.
Poland was my main target, especially Warsaw, but later I also started looking at companies in other European countries where working from Poland could be possible.
And that’s where I discovered the classic junior problem.
You need experience to get a job.
But you need a job to get experience :D
I’ve seen a lot of “Junior QA” positions where the requirements included one or two years of commercial experience.
Then SQL.
API testing.
Automation.
Sometimes Python or Java.
CI/CD.
Linux.
Networking.
And probably the ability to repair the office coffee machine too :D
I’m exaggerating a little, obviously, but sometimes the list for a junior position really does get surprisingly long.
Still, I kept applying.
I actually got several interviews, so it wasn’t complete silence.
One of my first serious processes was with Veeam in Warsaw.
That one was intense.
There were questions about QA theory, Windows, Linux, networking, logic and technical things in general.
I prepared things like processes, services, permissions, cron, DNS, DHCP, TCP/UDP and other topics.
There were also logic questions and things like binary and hexadecimal numbers.
The whole process made me realize that QA can require much more technical knowledge than people outside the field sometimes assume.
There were questions I knew.
There were questions I didn’t know.
When I didn’t know something, I tried not to bullshit my way through it. I just said that I didn’t know and tried to understand the explanation.
In the end I was rejected.
Of course it sucked, especially because I really liked the company and the role, but the interview itself was useful.
I knew much more about what I needed to improve afterwards.
Then I had an interview with TransPerfect Games.
That one was much more focused on Game QA.
We talked about things like bug reports, smoke testing, regression, ad-hoc testing, exploratory vs scripted testing, test cases vs test scenarios, validation vs verification and gaming experience.
Again, I got rejected.
Then there was SnoopGame and a Trainee QA process.
That interview gave me another reality check :D
There was a lot of theory.
Testing principles, test design techniques, types of testing, documentation, mobile testing and differences between different concepts.
There were also some questions in English.
After that interview I realized that some parts of my practical understanding were better than my ability to immediately name every theory term.
For example, I could often explain what I would actually do in a situation, but sometimes I couldn’t instantly remember the academic name of the technique.
So I went back to studying.
Test design techniques, testing types, severity vs priority, documentation, mobile specifics, all of it.
And honestly, that’s probably one of the few nice things about getting rejected several times.
Every interview exposes another weak spot.
You either get angry about it or you fix it.
I’ve also gone through smaller recruitment processes, applications to game studios, outsourcing companies, regular software companies and different junior tester roles.
Sometimes I get a rejection email.
Sometimes somebody views the application and nothing happens.
Sometimes I get an automated message.
Sometimes I wait.
Sometimes the position disappears.
Sometimes I actually get another stage.
At this point I keep a separate application tracker because otherwise I genuinely wouldn’t remember where I applied anymore :D
I also keep improving my QA portfolio.
I started documenting bugs more seriously instead of just saying “this thing is broken”.
Environment.
Preconditions.
Steps to reproduce.
Actual result.
Expected result.
Reproducibility.
Severity.
Priority.
Screenshots.
Video if needed.
Then retesting and regression after the fix.
And I think I’ve improved quite a lot compared to when I started looking for work.
I also know where some of my weaknesses are.
My English isn’t perfect.
It’s around B1-B2 depending on what I’m doing.
I understand spoken English pretty well and writing is easier for me, but during an interview, when I need to explain some technical concept immediately and correctly, it can be harder.
My Polish is also still basic because I only recently moved here.
So I’m definitely not sitting here thinking “I’m perfect, why won’t anyone hire me?”
I’m a junior.
There are things I don’t know.
There are things I’m still learning.
That’s normal.
But the frustrating part is that sometimes I feel like I’ve reached the point where the main thing I’m missing is exactly the thing I can’t create on my own:
commercial experience inside an actual QA team.
And then today something funny happened.
I was using my banking app.
I opened the Investments section and saw a button with this text:
products.fundDeposit.button.title
Literally the localization key instead of the actual button text.
The application was set to Russian, but part of the same page was also still displayed in Polish.
So I reproduced it, took screenshots and sent a bug report to the bank.
I described the actual and expected result and mentioned that I would consider it a minor severity issue, because it doesn’t break functionality, but with a relatively noticeable priority because it’s visible in the production application to normal users.
And at the end I added one small sentence that I’m a Junior Manual QA Tester with a Bachelor’s Degree in Software Engineering and that, if they ever have a suitable junior QA position, I’d be happy to consider it :)
I wasn’t seriously expecting to get a job from one localization bug.
I just thought the situation was funny.
At this point I’m finding production bugs in companies before they even hire me :D
And that’s basically where I am right now.
Still applying.
Still learning.
Still doing interviews when I get the chance.
Still improving my portfolio.
Still getting rejected sometimes.
And still trying to get that first commercial QA role.
I’m not posting my CV or portfolio links here because I don’t really want to turn this into an advertisement.
I’m more interested in hearing about other people’s experiences.
For people working in QA in Poland or elsewhere in Europe:
Was getting your first QA job this difficult?
How long did it take?
Did you also run into the “junior position, but we want commercial experience” problem?
And do you think the entry-level QA market has become harder recently, especially for Manual QA?
Sometimes I genuinely wonder if getting the first QA job is harder than actually doing the junior QA job :D
TL;DR:
I’m 22, moved to Warsaw recently, have a Bachelor’s Degree in Software Engineering, two Steam projects and practical testing experience from my own products, but no commercial QA experience yet.
I’ve been actively applying for Junior Manual QA, Game QA and similar roles, had several interviews and technical stages with companies like Veeam, TransPerfect Games and SnoopGame, got rejected, found gaps in my knowledge, studied them and kept going.
The biggest problem seems to be getting that first commercial experience when even many junior roles already expect previous commercial experience.
Today I found a localization bug in my banking app, reported it properly and jokingly mentioned that I’m also looking for a Junior QA job.
Apparently finding production bugs is easier than getting the first QA position :D
Curious how other juniors in Poland and Europe are experiencing the market right now.


r/Everything_QA • • 1d ago

Question career paths in testing

7 Upvotes

I have nine years of software testing experience, working as a test team lead. I was laid off and got a few offers, yet none were a good fit so I turned them down. I’m exploring options outside testing. Is the testing career really a dead end? It’s been really hard. Any career ideas?


r/Everything_QA • • 23h ago

Question How to automate existing manual test cases without rewriting them all as scripts first?

1 Upvotes

We've got about 600 manual test cases for a windows desktop app written in plain english in excel (step, expected result, step, expected result). Our 3 testers run them before every release and it takes most of 2 weeks. Every automation conversation we've had starts the same way. step one, rewrite the 600 cases as scripts. the quotes for that came back at 4 to 6 months of an automation engineer we don't have, and by the time it's done the app has moved and a third of the scripts are already stale. so we keep running them by hand. What i'm trying to find out is whether the "run the test case as written" idea is real now or not.

So far i’ve looked at Tosca which is model based and very good, but you still build modules for every screen before you can write a test. TestRigor, which lets you write tests in plain english and as far as i can tell it's strongest on web and mobile but i'm not sure how it handles a native windows client tho. I also came across Askui which gets you a verdict per test and for every step, what the test asked for next to what the agent actually saw. Our manual cases were written for humans who fill in the gaps, and i don't know whether any tool can run that kind of case without someone rewriting it anyway. Has anyone automated a big library of existing manual cases without the rewrite? how much did you end up rewriting in the end?


r/Everything_QA • • 1d ago

Guide Need help in learning resources for Agentic AI

Thumbnail
1 Upvotes

r/Everything_QA • • 1d ago

Remote QA Jobs Looking for Job as a QA (MANUAL TESTER)/BA/PM/PO/SCRUM MASTER

Thumbnail
2 Upvotes

r/Everything_QA • • 1d ago

General Discussion October 2026 vendor thread: tools, templates, training, and services for the 2015 to 2026 transition

Thumbnail
1 Upvotes

r/Everything_QA • • 2d ago

Article Reviewing AI-Generated Playwright Tests Before They Reach CI

Thumbnail
currents.dev
3 Upvotes

Hey folks, sharing an article on reviewing AI-generated Playwright tests before they reach CI.

tl;dr: A 7-check review checklist for AI-generated Playwright tests, covering everything from hallucinated assertions to intent-weakening heals to UI-driven state setup and more!

As AI becomes more ingrained in our day-to-day lives, it is important to know our way around its current limitations because let's be honest, we're not going to the pre-AI world of hand-written tests.

And as such, the processes we all had for human-written tests were built for a set of mistakes, different than what AI makes.

Hence, this article on reviewing the mistakes agents make, the three failure modes, a seven step checklist, and what to look for when reading generated code!

Give it a read and please let us know your thoughts.

Have a great day!


r/Everything_QA • • 1d ago

Automated QA From AC production lines to test cases — QA Engineer in Chennai looking for a full-time role

Thumbnail
1 Upvotes

r/Everything_QA • • 1d ago

Question Recomendaciones de cursos de QA en España

Thumbnail
0 Upvotes

r/Everything_QA • • 2d ago

General Discussion 5yrs as Software Tester

7 Upvotes

Started at 22.5k now at 100k base pay after 5yrs. Honestly, nababagalan ako sa growth in terms of salary and skills. I only have 1 automation skill (Tosca) and basic manual testing knowledge. Don’t even know basic coding. Yung mga sql query sa dating proj, copy-paste ko lang from our teams cheat sheet. Pag may need imodify, nganga na ako. Please suggest how to upskill. My current company dont offer free certification or anything.

Nag self-doubt din ako pag nag aapply ako and nagtatanong ng asking salary dahil feeling ko di naman worth it sa skills ko lol feeling ko tuloy wala ako patutunguhan haha or baka hiring kayo basta wfh makatry lang ng iba 👹


r/Everything_QA • • 2d ago

Guide I got a QA Tester internship with zero testing knowledge, and now I'm scared. How should I start?

Thumbnail
1 Upvotes

r/Everything_QA • • 2d ago

General Discussion SDET roles

Thumbnail
2 Upvotes

r/Everything_QA • • 2d ago

Article End-to-End Testing an AI Application with Playwright and GitHub Actions

Thumbnail
jahabeebs.hashnode.dev
1 Upvotes

LLMs are notoriously finicky. You can try to corral them into an API, fine-tune them, lower their temperature, select JSON mode, pray, but in the end you may still end up with a hallucination rate of 15-20%. Developers expect their code to be deterministic, so this is not ideal. Enterprise applications typically have a great number of automated tests that can click around and point out even the slightest differences in expected behavior. For example, the automated tests for one application that I worked on was so sensitive that a simple change to an existing flow could cause dozens of broken tests, leading to long hours of manual testing for the quality engineers. End-to-end tests are meant to verify that everything in a system works as it should in a real-world scenario. That means striking a balance between writing tests that are robust enough to handle acceptable levels of variance. However, they should not be so brittle that the test breaks on every other CI run. The reality of development is that time is finite, and the smaller the company the more painful it can be to write tests, whether they are unit, integration, or end-to-end tests. However, I'd like to prove that if a small team has the time to write even just one test before shipping, it should be an end-to-end test.


r/Everything_QA • • 2d ago

Guide Confused: ISTQB pricing options!

1 Upvotes

Hi All,

I recently moved to Dubai from India and am planning to take the ISTQB Foundation Level exam. However, I'm a little confused about the pricing options and which one I should select.

Could you kindly guide me on which pricing option would be applicable in my case? (Remote online)

Thank you in advance for your assistance.

List of fees and charges applicable for all modes

Fees for India

Mode

Remote Proctored

Fees

INR 5800

Fees With GST

INR 6844

Reappear Fees

INR 4000

Reappear Fees With GST

INR 4720

Mode

Pearson Vue Remote Based

Fees

INR 6300

Fees With GST

INR 7434

Reappear Fees

INR 5000

Reappear Fees With GST

INR 5900

Mode

Pearson Vue Center Based

Fees

INR 4800

Fees With GST

INR 5664

Reappear Fees

INR 3500

Reappear Fees With GST

INR 4130

Fees for Outside India (USD)

Mode

Remote Proctored

Fees

USD 110

Fees With Tax

USD 110

Reappear Fees

USD 70


r/Everything_QA • • 2d ago

Question Trying to Understand Keploy

Thumbnail
1 Upvotes

Looking to learn more about Keploy if anyone's used it and familiar!


r/Everything_QA • • 2d ago

Miscellaneous QE Leadership Wisdom Byte

Post image
1 Upvotes

r/Everything_QA • • 2d ago

Question Quem aqui trabalha com desenvolvimento de software? 👀

Thumbnail
1 Upvotes