r/Everything_QA

I built my software 100% vibe-coded, and now I need to tighten up QA.

I’ve already set up around 200 automated Playwright tests for the software. I created the test cases using screenshots from both the mobile app and desktop version. I’m also using Check now to test workflows like invoicing, since that’s one of the features inside the app.
I’m curious what other vibe coders, or people working with mostly AI-generated codebases, are doing to reduce bugs and errors. Right now I have a staging environment with a new version of the software that I’m also unit testing each feature on using Codex as that is my primary AI coding tool. I’ve used Claude code, but I really prefer Codex and I have some technical background. I completed a degree in computer science southern private school so I’m not clueless when it comes to the software development life cycle but for vibecoding specifically I’m curious what protocols people have used to cut down on production bugs. To me it seems like with AI you can build much faster, but the testing process needs to be much more thorough than it needed to be before. I catch them by looking at post hog, and sometimes the users tell me directly, but the ones who onboard itself self serve without me talking to them thought the software was broken. Partly because to do the invoicing feature you needed to connect your Stripe account or Square account and I was doing that part of the onboarding on the phone and I’ve now moved up doing this step in the onboarding process but steal, I think that just goes to show that I really need to cut down on bugs. I get regression with sign in as well so I’ll fix a bug with sign in and then two days later. People can’t login with Google again. It’s extremely aggravating.

Right now, I dogfood the product, do manual testing, and run automated Playwright tests every morning around 4 AM. Sometimes the tests give me useful insight, and sometimes I question their reliability, but overall I know I need much stronger QA to reduce production bugs.
The hard part is that the software is already pretty extensive. I have around 70–100 features, so there are a lot of edge cases. Even with dogfooding and manual testing, users still report bugs I didn’t catch.

Marketing is working pretty well through Meta ads, and people are ready to use the software. The problem is that a lot of trials don’t convert because users hit bugs. The UI is also confusing, but I’m not focused on fixing that yet. The bigger issue right now is literal software bugs breaking the experience.

I built my software 100% vibe-coded, and now I need to tighten up QA.

I’ve already set up around 200 automated Playwright tests for the software. I created the test cases using screenshots from both the mobile app and desktop version. I’m also using Checkly now to test workflows like invoicing, since that’s one of the features inside the app.
I’m curious what other vibe coders, or people working with mostly AI-generated codebases, are doing to reduce bugs and errors. Right now I have a staging environment with a new version of the software that I’m also unit testing each feature on using Codex as that is my primary AI coding tool. I’ve used Claude code, but I really prefer Codex and I have some technical background. I completed a degree in computer science southern private school so I’m not clueless when it comes to the software development life cycle but for vibecoding specifically I’m curious what protocols people have used to cut down on production bugs. To me it seems like with AI you can build much faster, but the testing process needs to be much more thorough than it needed to be before. I catch them by looking at post hog, and sometimes the users tell me directly, but the ones who onboard itself self serve without me talking to them thought the software was broken. Partly because to do the invoicing feature you needed to connect your Stripe account or Square account and I was doing that part of the onboarding on the phone and I’ve now moved up doing this step in the onboarding process but steal, I think that just goes to show that I really need to cut down on bugs. I get regression with sign in as well so I’ll fix a bug with sign in and then two days later. People can’t login with Google again. It’s extremely aggravating.

Right now, I dogfood the product, do manual testing, and run automated Playwright tests every morning around 4 AM. Sometimes the tests give me useful insight, and sometimes I question their reliability, but overall I know I need much stronger QA to reduce production bugs.
The hard part is that the software is already pretty extensive. I have around 70–100 features, so there are a lot of edge cases. Even with dogfooding and manual testing, users still report bugs I didn’t catch.

Marketing is working pretty well through Meta ads, and people are ready to use the software. The problem is that a lot of trials don’t convert because users hit bugs. The UI is also confusing, but I’m not focused on fixing that yet. The bigger issue right now is literal software bugs breaking the experience.

I work in a team of 25 developers and 2 managers. Both managers are also developers and are husband and wife. I am the only Software Tester on the team.

When I joined the company, the previous Software Tester told me he was resigning because of the politics within the development team. He also mentioned that the tester before him had left for similar reasons.

For the first three months, everything was fine. However, after that, the managers' attitude toward me changed. They often dismiss my suggestions for improving the testing process and ignore ideas that could make QA more efficient. They frequently make comments such as "testing is easy," "anyone can do a tester's job," and that "developers are the stars."

I am an introverted person who prefers to talk less and focus more on my work. I usually avoid arguments, don't talk back, and try to stay productive with minimal breaks. Although I have made every effort to build good relationships with the development team and fit in, I feel that my quiet and non-confrontational nature has made me an easy target for bullying. Instead of being appreciated for my work ethic, I often feel ignored, undervalued, and treated with less respect than others on the team.

There have also been occasions where I call one of the managers, but he ignores me even though I am standing behind him. When I ask technical questions, I am often told, "I'm busy, come back later," without getting the support I need. Whenever I try to introduce new tools or improve the QA process, my efforts are blocked or discouraged through office politics.

I have been working in this environment for the past 10 months. Despite consistently performing my responsibilities and trying to contribute positively to the team, I continue to feel that QA is undervalued and that my contributions are not respected. The overall experience has become mentally exhausting and has negatively affected my motivation and confidence at work.

I want to know how HCL select the candidate if the candidate having the referal and specifically for QA role like api testing or manual testing I want to know all about interview process anyone having experience just share here no matter how much just share it help me a lot.

Hi everyone,

I’ve been a Test Lead for over a decade, mostly focused on backend database and ETL validation in banking, insurance, and retail. On paper, it looks like a solid career. In reality, I feel like the ground is shifting under me, and I don't know how to keep up.

My strength is SQL and data logic, but even my confidence there has taken a hit lately. I’ve found myself leaning on AI tools to write scripts for me instead of doing it manually, which makes me doubt how sharp I actually still am. Meanwhile, job postings want Selenium, Playwright, APIs, BDD, CI/CD, and AI certifications... I have surface-level exposure to some of it, but no real depth.

Every time I sit down to try to plan how to fix this, I completely freeze. There are too many directions, too little time, and life doesn't pause for upskilling. I don't even know where to start or what a realistic plan looks like without burning out completely.

I'm posting because I need help getting out of this rut:

1. If you transitioned from ETL/Data testing into modern automation, how did you do it? What did you focus on first, and what tools actually matter vs. what is just keyword hype?
2. How do you structure learning when you're already exhausted from work? Any tips for breaking the paralysis?
3. Does anyone want to tackle this together? I don't have a concrete plan yet—I want to build one based on the feedback here. If you are also a mid-to-senior QA feeling lost and wants to connect, build a roadmap together, and keep each other accountable, please let me know.

I’d genuinely love any suggestions, course recommendations, or just to connect with anyone else who is trying to reinvent themselves right now. Would mean a lot to know I'm not doing this alone.

Hey everyone,

I recently joined a spirits company as their first QA hire. The product is quite large, but there’s very little documentation, and up until now, developers have been responsible for testing.

Right now, things feel unstructured. I often find out about new features or deployments after they’ve already happened, and testing requests come in randomly. Most of my work ends up being exploratory, without a defined process or clear expectations.

I’d like to introduce some structure and improve how testing is handled, but I don’t want to overwhelm the team or disrupt their current workflow too much.

Where would you recommend starting in a situation like this?
I’d really appreciate any advice or experiences you can share.

Hi everyone,
I recently completed and cleared the HackerRank assessment for an SDET role. I wanted to know, based on your experience, how many days it usually takes to receive the next email (interview invitation or next round)?
If you’ve been through this process, could you please share your timeline?
Thanks in advance!

[supprimé]

Hi there,

we are developing an open source application for robotics and it is used by many people around the world. We have a community with over 2000 people on discord and about 100 people are actively contributing in the further development. The most of the code is written by us, but as the project has become more popular, we want also give the contributors a better and easier way to be part of the project.

At the moment we habe github with github actions and there we execute the unit tests and the integration tests. We also have system tests, but these tests are written by a person working in our company and cannot be modified anyone outside the company. He uses a framework that he has written to grab testcases, written in actionword or keyword in Qase, the test management tool. Then these test cases are pulled by a script via the api and transformed to robotFramework testcases, that can be executed.

The main goal is, that our CEO wants to have the last word in quality. As we are developing the hardware and the software and we use the robot also for other purposes, we give the main roadmap for development, but also implement participants wishes, improvements and complaints. But the quality should me assessed by us.

Is there a good strategy to organize these things? Like, for development, we have a functional CICD-Pipeline. But how about reviews of the code? Who should be able to write testcases for the system tests? How can we ensure a good quality AND delegate at least some of the testing and QA to our community? Are there different strategies for doing so?

Du you work in an open source project and how is it solved there?

How does your team handle updating unit tests after large pull requests? What's the most frustrating part?

I’m trying to understand the best roadmap to follow. What should I learn first before jumping into tools like Selenium, Postman, SQL, Jira, etc.? Should I start with Manual Testing fundamentals or something else?

Also, can anyone recommend the best YouTube channels, websites, courses, or learning resources that are up-to-date and beginner-friendly? I’m looking for something structured rather than random tutorials.

If you were starting QA from absolute zero in 2026, what would your learning plan look like?

Thanks in advance!

I am 37F and have 13+ years of experience in QA manual + automation. Since 2024 I took break but now I want to resume into product management. I want to ask current working PO or PM how their day look like and if remote work is possible. I am opting for PSPO for start any guidance would be helpful

Hi everyone,

I've been learning Playwright with TypeScript over the past few months, and instead of just following tutorials, I built my own UI automation framework from scratch.

So far my framework includes:

Page Object Model

Fixtures

Data-driven testing

Environment configuration (.env)

Screenshots, videos and traces

Reporting

Parallel execution

The framework is working well, but I feel like I've reached the point where tutorials and courses aren't teaching me anything new.

What I really want now is practical, industry-level experience.

I'm not looking for another course. Instead, I want to build something that exposes me to real-world automation challenges such as:

Complex user workflows

Multi-page business processes

Dynamic UI handling

Network mocking

Authentication/session management

File uploads/downloads

API + UI integration

Advanced Playwright features used in production

Can anyone recommend:

A website or open-source application that's complex enough to automate?

A project idea that resembles what SDETs automate in real companies?

How you personally moved from "knowing Playwright" to writing automation that's production-ready?

I'm willing to spend the next 2–3 months building a serious portfolio project, so I'd really appreciate suggestions from people working as SDETs or QA Automation Engineers.

I'm new on qa and i'm working on a test suite that have many flaky tests that fail on assertion because of the page taking to much time to load. Is there any advices on good practices to prevent those issues?

Over the past few months I've been building VeriOps, an open-source QA management platform.

The original goal wasn't to compete with TestRail or any other tool. I mainly wanted to understand what QA teams actually need in their day-to-day work.

A few things surprised me:

- Many teams use only a small subset of defect statuses.
- Complex permission models become difficult to maintain very quickly.
- Test execution workflows matter more than most reporting features.
- Smaller teams often prefer simplicity over extensive traceability.

For QA engineers, test leads, and managers:

What features do you rely on every day?

What features do existing QA tools overcomplicate?

I'm trying to understand whether my experience matches what other teams are seeing in practice.