r/QualityAssurance • u/bonisaur • Jun 20 '22
So I’ve been working in in software for the past decade, in QA in the latter half, and most recently as a Director of QA at a startup (so many hats, more individual contributions than a typical FANG or other mature company). And I have been trying to answer questions recently about how to get started in Quality Assurance as well as what the next steps are. I’m at that stage were I really want to help people grow and contribute back to the QA field, as my mentor helped me to get where I am today and the QA field has helped me live a happy life thanks to a successful career.
Just keep in mind that like with everything a random person on the internet is posting, the following might not apply to you. If you disagree, definitely drop a comment as I think fostering discussion is important to self-improvement and growth.
How can I get started in QA?
I think there are a few different pathways:
A formal college degree is probably the most expensive but straightforward path. For those who want to network before actually entering the software industry, I think it is really important to join IEEE, a fraternity/sorority, or similar while attending University. Some of the most successful people I know leverage their college network into jobs, almost a decade out. If you have the privilege, the money, and the certainty about quality assurance, this is probably a way to go as you’ll have a support system at your disposal. Internships used to be one of the most important things you had access to (as in California, you can only obtain an internship if you are a student or have recently graduated). This is changing though which I’ll go into later. However, if you won’t build a network, leverage the support system at your university, and don’t like school, the other options I’ll follow are just as valid.
This was how I moved into Quality Assurance - I moved from a Customer facing role where I ETL (extract, transform, load) data. If you can get your foot in the door at a relatively small, growth-oriented company, any job where you learn about (1) the company’s software and (2) best practices in the software industry as a whole will set you up to move horizontally into a QA role. This can include roles such as Customer Support, Data Analyst, or Implementation/Training. While working in a different department, I believe some degree of transparency is important. It can be a double-edge sword though, as you current manager may see you as “disloyal” to put it bluntly, and it’ll deny you future promotions in your current role. However, if you and your manager are on good terms, get in touch with the Quality Manager or lead and see if they are interested in transitioning you into their department. One of the cons that many will face going this route will be lower pay though. Many of the other roles may pay less than a QA role, especially if you are in a SDET or Automation Engineering role. This will set you back at your company as you might be behind in salary.
Another valid approach is to obtain an entry level job as a manual tester somewhere. While these jobs have tended to shift more and more over-seas from tech hubs to cut costs, there are still many testing jobs available in-office due to the confidential or private nature of the data or their development cycle demands an engaged testing work-force. There is a lot of negative coverage publicly in these roles thought and it seems like they are now unionizing to help relieve some of the common and reoccurring issues though. You’ll want to do your research on the company when applying and make sure the culture and team processes will fit with your work ethics. It would suck to take a QA job in testing and burn out without a plan in place to move up or take another job elsewhere after gaining a few years of experience.
Obtaining certification will help you set yourself apart from others without work experience. Where I’m from in the United States, the International Software Testing Qualifications Board (ISTQB) is often noted as a requirement or nice-to-have on job applications. One of the plusses from obtaining certifications is you can leverage it to show you are a motivated self-learner. You need to set your own time aside to study and pay for these fees to take these tests, and it’s important at some of the better companies you’ll apply for to demonstrate that you can learn on the job. As you obtain more experience, I do believe that certifications are less important. If you have already tested in an agile environment or have done automated tests for a year, I think it is better to demonstrate that on your resume and in the interview than to say you have certifications.
The Software Industry is kinda like a gold rush right now (but not nearly as volatile as a gold rush, that’s NFTs and crypto). Bootcamps are like the shovel sellers - they’re making a killing by selling the tools to be successful in software. With that in mind, you need to vet a bootcamp seriously before investing either (1) your tuition to attend or (2) your future profits when you land a job. Compared to DevOps, Data Science, Project Management, UX, and Software Engineering though, I see Bootcamps listed far less often on QA resumes but they are definitely out there. If you need a structured environment to learn, don’t want to attend university, and need a support system, a bootcamp can provide those things.
I often hear about either Product Managers, UX Designers, Software Engineers, or DevOps Engineers starting off in QA. Rarely do run into someone who started in another role and stayed put in QA. If I do, it’s usually SWE who are now dedicated SDETs or Automation Engineers. I do believe that for the average company, this will require a payout though. I think the gap might be closing but we’ll see. Quality in more mature companies is growing more and more to be an engineering wide responsibility, and often engineers and product will be required to own the quality process and activities - and a QA Lead will coordinate those efforts.
What is the difference between a tester, QA Analyst, QA Engineer, Automation Engineer, and SDET?
A tester will often be a manual testing role, often entry-level. There are some testing roles where this isn’t the case but these are more lucrative and often get filled internally. Testers usually execute tests, and sometimes report results and defects to their test lead who will then provide the comprehensive test report to the rest of engineering and/or product. Testers might not spend nearly as much time with other quality related activities, such as Test Planning and Test Design. A QA Analyst or test lead will provide the tests they expect (unless you are assigned exploratory testing) as they often have a background in quality and are expected to design tests to verify and validate software and catch bugs.
I see fewer QA Analyst roles, but this title is often used to describe a role with many hats especially in smaller companies. QA Analysts will often design and report tests, but they might also execute the tests too. The many hats come in as often QA Analysts might also be client facing, as they communicate with clients who report bugs at times (though I still see Product and Project handling this usually).
QA Engineers is the most broad role that can mean many things. It’s really important to read the job description as you can lean heavily into roles or tasks you might not be interested in, or you may end up doing the work of an SDET at a significant pay disadvantage. QA Engineers can own a quality process, almost like a release manager if that role isn’t formal at the company already. They can also be ones who design, execute, and report on tests. They’ll also be expected to script automated tests to some degree.
Automation engineers share many responsibilities now with DevOps. You’ll start running into tasks that more such as integrating tests into a pipeline, creating testing environments that can be spun up and down as needed, and automating the testing and the test results to report on a merge request.
A role that has split off entirely are SDETs. As others have pointed out, in mature companies such as F(M)AANG, SDETs are essentially SWE who often build out internal frameworks utilized throughout different teams and projects. Their work is often assigned similarly to other software engineers and receive requirements and tasks from a role such as project managers.
What is the career path for QA?
I believe the most common route is to go from
Entering as a Tester or an Analyst is usually the first step.
From there you can go into three different routes:
However, if you do not enjoy programming and prefer to uphold quality processes in an organization, QA Engineers can make just as much as an SDET or Automation Engineer depending on the company. More often though, QA Engineers, SDETs, and Automation Engineers may consider a horizontal move into Software Engineering or DevOps as the pay tends to be better on average. This may be happening less and less though, as FANG companies seem to be closing the gap a little bit, but I’m not entirely sure.
For management or leadership, this is usually the route:
Individual contributor -> QA Lead / Test Lead -> QA Manager -> Director of Quality Assurance -> VP of Quality
For those who are interested in other roles, I know some colleagues who started in QA working in these roles today:
QA is set up in a position to move into so many different roles because communication with the roles above is so key to the quality objectives. Often times, people in QA will realize they enjoy the tasks from some of these roles and eventually move into a different role.
What should I do or learn first?
Tester roles are plentiful but this is assuming you want to start in an Analyst or Engineering role ideally. Testers can also have many of the responsibilities of an Analyst though.
If you have no prior experience and have no interest in going to school or bootcamp, (1) get a certification or (2) pick a scripting tool and start writing. I’ve already covered certification earlier but I’ll go into more detail scripting.
Scripting tools can either be used to automate end-to-end tests (think browser clicking through the site) or backend testing (sending requests without the browser directly to an endpoint). Backend tests are especially useful as you can then leverage it to begin performance testing a system - so it won’t just be used for functional or integration testing.
If you don’t already have a GitHub account or portfolio online to demonstrate your work, make one. Script something on a browser that you might actually use, such as a price tracker that will manually go through the websites to assert if a price is lower that a price and report it at the end. There are obviously better ways to do this but I think this is an engaging practice and it’s fun.
Here is a list of tools that you might want to consider. Do some research as to what is most interesting to you but what is most important is that if you show that you can learn a browser automation tool like Selenium, you have to demonstrate to hiring managers that if you can do Selenium, you feel like you can learn Playwright if that’s on their job description. Note that you will want to also look up their accompanying language(s) too.
These are the more mature tools with GUIs that will require scripting only for more advance and automated work. I recommend this over straight learning a language because it’ll ease you into it a little better.
Wrap-up
Hope someone out there found this useful. I like QA because it lets me think like a scientist, using Test Cases to hypothesize cause and effect and when it doesn’t line up with my hypothesis, I love the challenge of understanding the failure when reporting the defect. I love how communication plays a huge role in QA especially internally with teammates but not so much compared to a Product Manager who speaks to an audience of clients alongside teammates in the company. I get to work in Software,
r/QualityAssurance • u/Fissherin • Apr 10 '21
Hello, I am writting (or trying to) this guide while drinking my Saturday's early coffee, so you may find some flaws in ortography or concepts. You have been warned.
I have seen so many post of people trying to go from manual qa to automated, or even starting from 0 qa in general. So, I decided to post you a minor learning guide (with some actual market 10/04/2021 dd/mm/aaaa format tips). Let's start.
------------Some minor information about me for you to know what are you reading-----------------
I am a systems engineer student and Sr QA Automation, who lived in Argentina (now Netherlands). I always loved informatics in general.
I went from trainee to Sr in 4 years because I am crazy as hell and I never have enough about technology. I changed job 4 times and now I work with QA managers that gave me liberty to go further researching, proposing, training and testing, not only on my team.
Why did I drop uni? because I had to slow off university to get a job and "git gud" to win some money. We were in a bad situation. I got a job as a QA without knowing what was it.
Why QA automation? because manual QA made me sleep in the office (true). It is really boring for me and my first job did't sell automation testing, so I went on my own.
----------------------------------------------------Starting with programming-------------------------------------------------
The most common question: where do I start? the simple answer is programming. Go, sit down, pick your fav video, book, whatever and start learning algorithms. Pls avoid going full just looking for selenium tutorials, you won't do any good starting there, you won't be able to write good and useful code, just steps without correlation, logic, mainainability.
Tips for starting with programming: pick javascript or python, you will start simple, you can use automating the boring stuff with python, it's a good practical book.
Alternative? go with freecodecamp, there are some javascript algorithms tutorials.
My recommendation: don't desperate, starting with this may sound overwhelming. It is, but you have to take it easy and learn at your time. For example, I am a very slow learner, but I haven't ever, in my life, paid for any course. There is no need and you will start going into "tutorial hell" because everyone may teach you something different (but in reality it is the same) and you won't even know where to start coding then.
Links so far:
Javascript (no, it's not java): https://www.freecodecamp.org/ -> Aim for algorithms
Python: https://automatetheboringstuff.com/ you can find this book or course almost everywhere.
Java: https://www.guru99.com/java-tutorial.html
C#: https://dotnet.microsoft.com/learn/csharp
What about rust, go, ruby, etc? Pick the one of the above, they are the most common in the market, general purpose programming languages, Java was the top 1 language used for qa automation, you will find most tutorials around this one but the tendency now is Javascript/Typescript
---------------I know how to develop apps, but I don't know where to start in qa automation---------------
Perfect, from here we will start talking about what to test, how and why.
You have to know the testing pyramid:
/ui\
/API\
/Component\
/ Unit \
This means that Unit tests come first from the devs, then you have to test APIs/integration and finally you go to UI tests. Don't ever, let anyone tell you "UI tests are better". They are not, never. Backend is backend, it can change but it will be easy and faster to execute and refactor. UI tests are not, thing can break REALLY easy, ids, names, xpaths, etc.
If your team is going to UI test first ask WHY? and then, if there is a really good reason, ok go for it. In my case we have a solid API test framework, we can now focus on doing some (few) end to end UI test.
Note: E2E end to end tests means from the login to "ok transaction" doing the full process.
What do I need here? You need a pattern and common tools. The most common one today is BDD( Behaviour driven development) which means we don't focus on functionality, we have to program around the behaviour of the program. I don't personally recommend it at first since it slows your code understanding but lots of companies use it because the technical knowledge of the QAs is not optimal worldwide right now.
TIP: I never spoke about SQL so far, but it's a must to understand databases.
What do we use?
Tool list:
Pick only one of these to start, then you can test others and you will find them really alike. Links on your own.
TIP: learn how to use JSONs, you will need them. Take a peek at jsons schema
------------------It's too hard, I need something easier/I already have an API testing framework------------
Now you can go with Selenium/Playwright. With them you can see what your program is doing. Avoid Cypress now when learning, it is a canned framework and it can get complicated to integrate other tools.
Here you will have to learn the most common pattern called POM (Page object model). Start by doing google searches, some asserts, learn about waits that make your code fluent.
You can combine these framework with cucumber and make a BDD style UI test framework, awesome!
Take your time and learn how to make trustworthy xpaths, you will see tutorials that say "don't use them". Well, they are afraid of maintainable code. Xpaths (well made) will search for your specific element in the whole page instead of going back and fixing something that you just called "idButton_check" that was inside a container and now it's in another place.
AWESOME TIP: read the selenium code. It's open source, it's really well structured, you will find good coding patterns there and, let's suppouse you want to know how X method works, you can find it there, it's parameters, tips, etc.
What do I need here?
OR
--------------------------------I am a pro or I need something new to take a break from QA-----------------
Great! Now you are ready to go further, not only in QA role. Good, I won't go into more details here because it's getting too long.
Here you have to go into DevOps, learn how to set up pipelines to deploy your testing solutions in virtual machines. Challenge: make an agnostic pipeline without suffering. (tip: learn bash, yml, python for this one).
Learn about databases, test database structures and references. They need some love too, you have to think things like "this datatype here... will affect performance?" "How about that reference key?" SQL for starters.
What about performance? Jmeter my friend, just go for it. You can also go for K6 or Locust if that is more appealing for you.
What about mobile? API tests covers mobile BUT you need some E2E, go for appium. It is like selenium with steroids for mobile. Playwright only offers the viewport, not native.
And pentesting? I won't even get in here, it's too abstract and long to explain in 3 lines. You can test security measures in qa automation, but I won't cover them here.
--------------------------------------------Final tips and closure (must read please)-----------------------------------------
If you got here, thanks! it was a hard time and I had to use the dicctionary like 49 times (I speak spanish and english, but I always forget how to write certain words).
I need you to read this simple tips for you and some little requests:
Update 28/03/2023
I see great improvements using Playwright nowadays, it is an E2E library which has a great documentation (75% well written so far IMO), it is more confortable for me to use it than Selenium or Cypress.
I use it with Typescript and it is not a canned framework like Cypress. I made a hybrid framework with this. I can test APIs and UIs with the library. You can go for it too, it is less frustrating than selenium.
The market tendency goes to Java for old codebases but it is aiming to javascript/typescript for new frameworks.
Thanks for reading and if you need something... post!
Regards
Edit1: added component testing. I just got into them and find it interesting to keep on the lookout.
Edit2 28/03/2023: added playwright and some text changes to fit current year's experience
Edit3 10/02/2024: added 2 more tools for performance testing
Edit4: 22/01/2025: specflow has been discontinued. I haven't met an alternative.
r/QualityAssurance • u/lessem • 5h ago
A couple of our UAT events flopped. One big reason is that the users are stumbling through the app(s)/system. User training should happen before a UAT. in our case, it did not happen.
what is your take on it and how are you handling in your projects and what success have you seen?
r/QualityAssurance • u/sisamisigs • 30m ago
Hey everyone,
I'm looking for some perspective from senior QA folks, SDETs, or engineering managers who have navigated a similar career plateau.
I've been with my current company since 2019. When I joined as a Software Tester, there were virtually no standardized QA processes. Over the years, I built testing protocols from scratch, introduced multi-level environments and built UI/API test frameworks(POM design pattern)
Recently, I hit a point where manual release testing wasn't keeping me challenged, so I took the initiative to solve an internal bottleneck: our test automation setup required 2 to 5 hours of tedious, manual data entry into our web app just to get a clean environment ready for automation.
To fix this, I engineered an end-to-end automated data preparation & onboarding pipeline using Playwright & Node.js
Automated the signup flow and integrated the Gmail API to dynamically poll/parse confirmation tokens and authenticate sessions automatically.
On the same framework, I created scripts to automatically seed complex test data into the web app based on external configuration files (Excel/JSON)
Integrated google workspace webhooks to notify teams and broadcast freshly seeded app credentials to private workspace to be consumed by another automation framework.
The Problem:
When I demoed this solution to leadership, I found out something unexpected. The company's actual customer onboarding process took 1 month because staff manually entered data through legacy windows apps and DB scripts.
Leadership immediately realized my internal QA pipeline could solve their production bottleneck. They are planning to use this exact implementation as billable feature to charge clients to expedite onboarding.
Yet, when I previously asked about career progression, leadership explicitly told me I had "reached the ceiling" here and that titles don't matter. Now the company is downsizing sprints and asking QA to take on general customer support duties instead of expanding automation.
Questions:
Am I overvaluing my contributions, or is it common for companies to monetize internal engineering wins while capping QA growth?
With a mix of QA strategy, framework architecture, 3rd-party API integration, and process building, should i be targeting Lead QA Engineer, SDET, or pivoting toward QA/Engineering management?
I've built my career entirely on hands-on framework development and practical systems. Do recruiters/managers actually care about ISQTB certs, or does proven architecture and business impact carry more weight in current hiring markets?
For those who transitioned out of company where you were "stuck", how did you hightlight business impact on your resume without sounding like you stepped outside your QA scope?
Would love to hear your thoughts or experiences!
r/QualityAssurance • u/goldmember2021 • 4h ago
Hey guys 👋🏽
I have recently been made redundant. Big shock as there was no indication that the QA function was to be axed!
Anyway onwards and upwards, I'm now looking for a role.
18 years experience, worked on a number of projects including finance, government and safety industry.
Playwright, cypress, selenium and degree in java.
Any remote UK roles or hybrid in Cardiff/Bristol 🙏🏽
r/QualityAssurance • u/Great-Talk1310 • 1h ago
Hi everyone,
Is there anything specific that annoys you about Test Plans (pricing, specific features, bugs, or usability)? Is there anything you feel is missing?
If you've considered switching to another tool that still works entirely inside Azure DevOps, what stopped you?
Also, what does Test Plans do really well that you wouldn't want to lose?
I've built an Azure DevOps extension that is an alternative to Test Plans, and I'm trying to understand different perspectives and use cases. If you have any specific expectations for a tool like this, I'd really appreciate your feedback.
r/QualityAssurance • u/Royal-Job-9905 • 2h ago
Can anyone suggest a good tutorial on Performance testing with k6? Also some environments where I can play around k6.
Thanks.
r/QualityAssurance • u/Vivid_Criticism_1762 • 5h ago
Hello,
I would like some insight from experienced professionals.
I am have non IT (7 years) and 2 years of manual testing experience, I recently completed MBA (it's more of an IT mba rather than general MBA), I am looking to transition into automation testing.
I found playwright interesting, so I have started learning playwright with js/ts, currently I am on the core programming fundamentals and
I would like to know, how is the market for this ?
Is it possible to secure a job with 3 months of hardcore practice (building framework from scratch) ?
Can I show my own made project (github) to get a call for interviews ?
Is playwright easier than selenium (+java) ?
How is the growth in automation testing in coming years (because of A.I.) ?
Is it viable to enter into this, as I am not young and have lots of experience in another field ?
I am an Indian but currently located in Europe
Thanks.
r/QualityAssurance • u/Alternative-Try7044 • 11h ago
I’ve been trying out managing test cases as plain YAML files right inside our Git repos.
The whole point is treating manual tests just like code. Everything is local-first so there’s no web vendor lock-in, and team collaboration happens smoothly by pushing updates to dedicated test branches instead of messing with heavy third-party syncs. Also, since it's all plain text, using Cursor or other AI tools to write, search, and clean up test cases turns out to be super handy.
Anyone else tried keeping QA cases in Git like this?
Just to clarify based on the comments—I totally agree that reading raw YAML isn't the goal. What makes this setup actually usable is a lightweight local UI to render, edit, and execute cases cleanly (so it feels like a real test management tool), while keeping everything Git-native under the hood.
r/QualityAssurance • u/Weary_Ad_1728 • 8h ago
Buenas gente, como les va? Primera vez que posteo en todo reddit en general, pero viendo que siempre responden y son buena onda acá con las consultas de los demás, me propongo postear esto a ver si me dan una mano.
Para tratar de hacerla corta: me recibí de ing en sistemas pero la programación no es lo mío, nunca le terminé de agarrar la mano del todo. Se que es algo que si o sí voy a tener que aprender en algún momento, al menos lo básico pero bue, por ahora es lo que hay... medio a los golpes fui consiguiendo laburos de soporte hasta donde estoy ahora. Casi 8 años de recibido y 6 años y medio de soporte IT entre dos empresas internacionales con bastantes clientes y demás.
La cosa es que quiero salir de soporte de una vez por cuestiones y opiniones que no quiero comentar para no armar bardo al dope.
Tomando en cuenta que la programación me cuesta bastante, quiero emepezar el camino de QA. Antes que se diga: si, sé que para la automatización necesito saber de programación, pero quiero verlo más adelante. Quiero empezar a hacer QA manual, hice un cursito y estoy haciendo otros y tratando de formarme. Para no hacerla más larga, la consulta en sí es: alguno me tiraría qué tecnologías, herramientas y demás necesito saber para empezar? Me refiero a cosas prácticas (tema de teoría, metodologías de trabajo y demás yerbas creo que por ahí las podría aprender rápido).
En el curso que hice recomendaron muchísimo aprender postman (que ya uso algo básico en el laburo) también Jmeter, recomendaron meterle algo de mano a la consola de chrome y unos amigos me nombraron BURP. Qué otras herramientas podría sumar o mejor dicho, en qué herramientas debería centrarme? y más que nada alguien sabe de alguna página o algo donde pueda practicar cosas así? Por mi cuenta estoy tratando de completar plantillas de test cases pero si tuviera un marco en donde laburarlo, mejor. Por otro lado, me dijeron que siempre conviene conocer SQL y si bien conozco, por ahí no soy un gran experto. Me gustaría saber qué tan en profundidad me sirve conocerlo como para empezar... a ver, se hacer consultas y cosas así, pero ya si tengo que hacer una consulta compleja usando varios joins se me complica (de nuevo, no es tanto lo mío la lógica de programación, pueden juzgarme si quieren, no me jode).
Para tener una referencia: en mi laburo puedo hablar y pedir que me cambien de proyecto (es una idea bastante fuerte porque la persona que tengo de encargada es bastante soreta y no la aguanto) y se que hay mínimo 3 grupos de QA manual, trabajamos con una app tanto para android como iOS, se usa AWS para ciertos servicios y SalesForce de CRM aunque el lenguaje en qué se programa la app no tengo idea. También hay una parte web pero es secundario.
Bueno, creo que por ahora sería eso. Les agradezco de antemano a los que respondan. Si me surgen más dudas o cosas así iré agregando.
Un saludo gente de Reddit.
r/QualityAssurance • u/nothinginto_much • 13h ago
Need some genuine advice from people who have worked in CSV or regulated pharma projects.
I've been working as a Computer System Validation (CSV) Analyst for the last 4 years. For the last 6 months, I've also been handling manual testing in my project.
A senior (14 years experience) joined our team. Initially he was brought in mainly for automation, so I gave him KT on the manual testing activities, project flow and documents. That was completely fine.
Now the automation work is no longer happening, so he's been moved to manual testing full-time. The problem is, now he's asking me to teach him CSV and validation concepts as well, and my managers are also asking me to give that KT.
I'm a bit confused about this.
The validation knowledge I have didn't come from formal KT. Nobody sat with me and explained all this. I spent 4 years reading validation documents, understanding regulations, handling deviations and escalations, and learning things the hard way while working on projects.
I don't mind explaining our project, documents, process or how we do things. But teaching years of validation knowledge feels different from normal KT.
Maybe I'm thinking about this the wrong way, so I wanted to ask people who have more experience.
If you've worked in CSV or pharma:
Is this a normal expectation?
Would you share everything, or is there a boundary between project KT and domain expertise?
How would you handle this professionally?
Just looking for honest opinions from experienced people.
r/QualityAssurance • u/Visible_Attitude_819 • 10h ago
Hello everyone,
I am currently seeking opportunities as a Manual QA Engineer with 5+ years of experience in Manual Testing, API Testing (Postman), SQL, Jira, and Agile methodologies.
I am an immediate joiner and open to remote, hybrid, or onsite roles. If your organization is hiring or you know of any relevant openings, I would greatly appreciate your referral or any leads.
Thank you for your support.
r/QualityAssurance • u/userNULLname • 7h ago
Been maintaining Playwright suites for a while, and the 2026 AI-testing pitch bugs me: let an agent write and run your tests, with a model in the CI hot path deciding on every build whether an assertion is reasonable.
That's a closed loop. The same kind of system that wrote the assertion certifies it. A model is great at inventing a plausible test and much worse at catching its own wrong assumptions, so it ends up confidently wrong twice in the same direction.
I built a pipeline around one boring rule from normal engineering: the thing that makes something shouldn't be the thing that certifies it. Producer is not validator.
Concretely:
It's open source with a demo shop, runs end to end in a few minutes. Honest about what it doesn't solve too: curating the frontend slice is the real cost on a big app, and the deepest check only works where values cross the wire as text.
Curious how others here handle trusting AI-generated tests. Do you let a model into your CI, or keep generation dev-time only?
r/QualityAssurance • u/Major_Host_1250 • 5h ago
**I’m currently working as a Senior QA Test Engineer and am considering a career change due to the declining number of QA opportunities in the job market. I’m looking for advice on the best courses and in-demand skills to learn in 2026 that can help me successfully transition into a stable, high-growth career.**
r/QualityAssurance • u/Direct-Cockroach-980 • 16h ago
Suggest me any tutorial website or youtube video
Right now I am preparing for the QA job
r/QualityAssurance • u/theITGuy_27 • 14h ago
Hi everyone,
I'm looking for QA Engineer/SDET opportunities and am available to join immediately in India
Experience: \~2 years
Skills: Python, SQL, Playwright, JavaScript, Manual Testing, API Testing, Test Automation, Functional & Regression Testing.
I'm also actively learning AI concepts like LLMs, RAG, Agentic AI, MCP, and AI tools
If your company is hiring or you know of any relevant openings, I'd really appreciate a referral,I will share my resume over DM.
Current Location: Noida,Uttar Pradesh Open to Relocation: Gurugram,Pune,Chennai, Hyderabad, Bengaluru, Chandigarh Reason for change: Lack of learning opportunities in current organisation.
Thanks in advance!
r/QualityAssurance • u/Whole_Coffee9084 • 1d ago
Release week is when a screenshot queue starts collecting everything at once: a real layout shift, a clipped label, and the usual font rendering noise. The diff job catches all of it, then a reviewer opens a stack of nearly identical images to decide what can actually block the release.
One idea is to send only those noisy regions to SAM 2 and use LingBot-Vision for the boundary features. It would still need a small classifier trained on the team's own screenshots, with the original image next to every result. Sorting obvious rendering noise away from likely layout bugs is enough; the release decision can stay with the reviewer.
r/QualityAssurance • u/thiagocoliveir • 1d ago
For those using AI coding agents for web test automation, which one are you currently preferring: Claude Code or Codex?
I mainly work with Playwright/Cypress and would like to hear from people who have actually used both.
What made you choose one over the other?
r/QualityAssurance • u/MidnightRain_17 • 1d ago
I am planning to change career and shift to QA.
r/QualityAssurance • u/geek_in_room • 2d ago
We've started shipping a couple of llm-backed features and I'm realising our existing regression suite doesn't really give us much confidence once the model behaviour starts changing....
Automated regression seems to work well for our regular application. But with LLMs, even a small prompt tweak or model update can change responses even when all tests are still passing. I'm not sure how to validate it properly.
I've been spending some time looking at some tools. Promptfoo, langsmith, deepeval, testsigma etc. but the more I read it feels like each one handles a different part of the problem. I'm trying figure out what we actually use in production.
Anything working well for your team? One platform or are you guys combining different tools?
Also, what does your validation workflow look like from building evaluation datasets and integrating checks into CI/CD to deciding whether a model change is actually safe enough to ship.
Just want to avoid spending weeks building something that we'll end up replacing a few months later .
r/QualityAssurance • u/Fantastic-Walrus-429 • 2d ago
I do blockchain QA, and finding a working testnet faucet was a waste of time.
I kept a written document but it kept getting outdated and I never knew the actual status of the faucet.
I built a small tool to help myself:
It covers 36 faucets across 30+ networks (Sepolia, Solana, BTC, Polygon Amoy, Fuji, Sui, Aptos, Sei…). It does a simple faily HTTP check and reports back.
It's open source, so if you spot one wrongly marked down (or know a faucet I'm missing), corrections are welcome.
Not selling anything — it's free and there's no login. Just hoping it saves someone else the 20-minute faucet hunt.
r/QualityAssurance • u/CtrlAltDelLife_06 • 2d ago
Hi everyone,
I’m currently working full-time as a QA Engineer and, due to some financial commitments, I’m looking for a part-time remote job or freelance QA/testing work to earn some additional income.
I have a few questions:
Which platforms are genuinely good for finding remote QA/freelance testing work (Upwork, Toptal, Test IO, uTest, etc.)?
If I’m already employed full-time, would taking freelance work be considered moonlighting?
Do these platforms or clients usually ask for PAN, Aadhaar, or other tax details?
Has anyone here managed freelance QA work alongside a full-time job? Any tips or things to watch out for?
Looking for advice from people with real experience. Thanks!
r/QualityAssurance • u/WoodenFudge9908 • 2d ago
I have 5 year QA experience. Manual and automation. I’ve gotten let go 2.5 months ago. Started applying a month ago.
Seeing this part-time job in Los Angeles for an ai platform, they want me on-site 3 days. 90 min round trip commute, sole QA person at early stage startup, I’m gonna have to come in and build QA processes from scratch basically. Will make almost same as EDD is paying.
Only pro is on my resume it’ll say I’m currently employed instead of a gap.
I can get paid more with non-QA part time.
Would it be worth it? Should I take it?
r/QualityAssurance • u/pha_uk_u • 2d ago
Hi All,
I am QE by profession. made a doc control app for myself.
I made this android app for myself. As my file explorer gets dumped with everything and anything. I wanted to have folders, revise docs(Taxes, insurances, license, etc). with OCR you can search for a word and every document with that word would pop up. you can set expiration date to docs.
please dm and drop a comment if you would like to test my app. you will get lifetime free without ads for this.
thank you.
r/QualityAssurance • u/Assureur • 2d ago
I have an ISTQB Foundation Level certificate and have built several Java-based projects using Selenium, TestNG, Rest Assured, Postman, Jenkins, and GitHub Actions.
GitHub: https://github.com/alkanf
I don’t have professional QA experience yet. What should I focus on next ?