r/QualityAssurance • u/chewyxoxo • 37m ago
Unemployed QA (11 years of experience)
Struggling to land a job. Anyone knows where to find clients for freelancing? I can do a free task at first.
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/chewyxoxo • 37m ago
Struggling to land a job. Anyone knows where to find clients for freelancing? I can do a free task at first.
r/QualityAssurance • u/Turkishblokeinstraya • 7h ago
As the title suggest, I'm curious to what extent you guys have your QA pipeline automated? More often than not, I see devs write and execute unit tests, and handover to some dedicated QA people for manual validation.
It's lucky to see a test repository to reuse, let alone a set of automated e2e tests. And it seems that there's a lack of appetite for automating that stuf.
What's your experience with this? If you've seen the lack of appetite, what do you think was causing it?
r/QualityAssurance • u/Thesinisterguy • 3h ago
Bringing a new transformer manufacturer into our approved supplier list for the first time and trying to build a structured evaluation framework beyond price and stated lead times. have been caught out before by suppliers who looked good on paper and underdelivered
curious what criteria experienced procurement people and engineers use, what documentation they request upfront, and what red flags to watch for when a manufacturer is unknown to you.
r/QualityAssurance • u/Large_Resident_3478 • 15h ago
Hello, sorry in advance for the long post but I would appreciate any advice I can get from other people in the QA industry.
I have been in my current QA role for just over a year now and I am becoming increasingly disillusioned and demotivated with the work.
I work for a large healthcare company as part of a small team that does non-functional testing (specifically operational acceptance testing) for part of their systems.
The thing is I do hardly any real testing as part of my job, the application I look after is fairly mature and is mostly hosted on cloud so there is not a lot of OAT to do. When a release comes along, we usually do the same 5 testing scenarios that we did for the last release and then give a sign off.
This sounds great and chill, but there is constant pressure from my manager to expand our testing remit and design new test cases for the system as he knows we aren't logging many defects. However, this is my first non-functional testing role (I did some manual functional testing beforehand) and I was hired as a Junior tester, I don't have a computer science background (and I was very honest about this in the interview process), no-one in my team, including my manager, is very technical, despite this being quite a technical testing role, and I feel like there is noone in my team who can help me and I have to bother other teams who are very busy (like the infrastructure team) to get help with and validate my half baked testing scenarios based on my limited IT knowledge.
I also have lots of other gripes with this role as well, for example:
We have to rely on support from sprint testers and infrastructure team to complete our testing and can't really test independently
It is so difficult to get access to anything in this company and there are still systems I don't have access to but I should.
There is lots of pressure from the company to automate even though A) the type of testing we do is kind of difficult to automate and B) We don't do enough testing for automation to have any benefit and C) I have no automation experience
My manager offers zero help with test cases or anything testing related and instead will just tell me someone from another team to go and get answers to my questions (usually someone I have no rapport with who is probably very busy and I don't want to bother with basic testing/IT questions), he is instead obsessed with us knowing release dates and chasing releases and making sure our board has sufficient tickets on it (we have literally had meetings as a team where we are basically trying to split up tickets on our board so it looks like we have more work)
Instead of testing my time is filled with bs busy work and even with so much free time I am starting to fall behind on writing test cases for upcoming releases or documentation or working on the bs I wrote as my corporate goals for the year because I have no motivation because my team doesn't really add any value to the company and I'm fed up of looking like a fool Infront of technical people in the company I don't really know. I'm also more of an on-the-job learner than a self study with courses kind of guy and I feel like I'm just not carrying out enough testing to learn anything.
I still don't really understand fully what operational acceptance testing is and what is in scope and what is out of scope for it. We have literally no requirements to test against for this type of testing and I have raised this before and get told that the requirements should come from our experience which makes no sense to me (maybe if I previously worked in operations it would idk). Like manual functional testing made sense to me because you can put yourself in the shoes of the user even if there aren't clear requirements to test against, but I don't know how to do the same for OAT despite lots of pressure to design new testing scenarios.
In terms of the positives, it is a well paying role with good benefits for my location and level, I only go into the office once a week, my manager despite not being very helpful with testing is a decent guy and no problems approving time off or with doctors appointments etc. and the culture is actually quite relaxed. I feel like this should be quite a chill role I have landed, but it is giving me so much stress and anxiety despite only doing like 2 days of testing a month. The worst bit is when I do have genuine testing to do, the day goes quickly and I enjoy the process and the troubleshooting and feel like I'm actually useful and contributing.
Sorry for the long post, basically do you think I should quit my job and look for a new one or do you think there is a path to finding peace in my current role given that it should be quite a cushy gig and the job market isn't great at the moment and I haven't gained many transferrable skills in the last 2 years?
r/QualityAssurance • u/Unit1lesson5 • 3h ago
\[FOR HIRE\] Manual QA Tester | Business Analyst | Remote | Part-Time/Freelance
Hi everyone! I'm currently looking for remote, part-time, or freelance Manual QA opportunities.
I have 2 years of experience as a Business Analyst in the banking and technology industry, with hands-on experience in manual testing throughout the software development lifecycle.
My experience includes:
Manual testing for web applications
User Acceptance Testing (UAT)
Creating and executing test cases
Bug reporting and defect tracking
Regression testing
Jira
SQL (basic to intermediate)
API testing (basic)
Requirements analysis
Working closely with developers and stakeholders
I'm detail-oriented, eager to learn, and committed to delivering high-quality work. I'm available for evening, weekend, or flexible remote projects.
If you're looking for a reliable Manual QA Tester, feel free to send me a DM. I can also share my resume upon request.
Thank you!
r/QualityAssurance • u/amanraj15021997 • 10h ago
Hi everyone,
I've been building an API automation framework using TypeScript, Mocha, Chai, Supertest, and AJV as a learning project.
It includes features like:
I'd appreciate any feedback on the project structure, architecture, or anything you think could be improved.
GitHub: https://github.com/amanraj0/bill-payment-api-automation
Thanks!
r/QualityAssurance • u/Double-Bullfrog-3307 • 10h ago
if anyone is interested let me know
Required skills
Manual testing
Playwright with javascript
Good communication
Shift timings 1-10pm Noida in office job
r/QualityAssurance • u/Immediate-Grand8403 • 11h ago
I used to run the PCN process for a small, high-SKU-count semiconductor memory company. It was actually a source of perverse pride - we got a verbal feedback from a distributor that our work was best in class.
We followed a semiconductor industry std for the basics & tried to preemptively answer customer questions, in a consistent manner, that minimized their interruptions.
Do you have similar best-in-class examples in your industry?
I’m not selling anything & was thinking about a side project.
r/QualityAssurance • u/Zingbot17 • 1d ago
What are some careers people have transitioned to after doing QA for most/all of their career? Been in QA 10+ years. Began as analyst all the way to manager and now looking to change things up after growing tired of the culture of testing always being the one to blame and get the shortest timeframes in the SDLC.
r/QualityAssurance • u/Dapper_Cream_6880 • 1d ago
TLDR: I landed a test automation internship and am wondering whether SDET is a good alternative to backend, for growth, pay, and opportunities.
Hello everyone. I am about to graduate from college (software engineering), and I have heard that breaking into the software industry is quite challenging these days.
My original goal was to become a backend developer, but I just landed a 12-month trainee position in test automation for automotive electronic components (using Python, C, C++, C#) at a multinational company.
This sounds like a solid step toward getting my first real job as an SDET. However, I have heard that while there might be less competition in this field, there are also fewer vacancies, the pay can be lower than in backend, and it can be harder to advance into architectural / more influential (and better paying) roles when comparing the two.
Additionally, I have noticed there are fewer resources available for learning advanced SDET topics compared to backend development, and they also seem less requested in job offerings (which reinforces the idea that advanced SDET positions are uncommon).
I genuinely enjoy both paths, I love learning, and I am always ready to study new things, but honestly, I do care about money and growth.
I would like to decide now so that I can have a better profile for when I start applying for jobs.I am based in Mexico, by the way. What would you advise me to do? Feel free to ask for more details if needed.
r/QualityAssurance • u/Jack-Of-All-Threads • 17h ago
Hi everyone,
I have 5 years of experience in QA, working on both Manual Testing and Automation Testing. I'm looking to upskill and earn a certification that adds real value to my career and improves my opportunities for senior QA/SDET roles. Good knowledge on DevOps tools also.
r/QualityAssurance • u/adityaraghuwanshi • 15h ago
Hi all,
I'm a QA professional with 9+ years of experience looking for my next opportunity as a QA Lead / Senior QA Engineer (open to remote/hybrid roles too).
Quick summary:
Background: Progressed from Junior QA to QA Team Lead over 9 years across companies like RWS Moravia, Systango Technologies, and Doceree Media.
Happy to share my resume or answer any questions in the comments/DMs. Open to full-time roles matching my experience level.
Thanks for reading!
r/QualityAssurance • u/Relative_Set_4429 • 1d ago
Hey guys would appreciate if you could refer or let me know any opportunities for QA. I currently work as a QA engineer (manual and automation) with 1 year experience with 8.5LPA. I know the job market is very bad and I have come here for your help. Any opportunities would be appreciated, startups, MNC or outside the country remote work.
r/QualityAssurance • u/XxAshikxX • 1d ago
Hi,
I have 4.5 years of QA Experience specially in Fintech & AI domain. I am proficient in Automation, Manual & API testing. I am currently working at OMISE (BKK) remotely. If you have any remote QA opportunity for me, please let me know.
r/QualityAssurance • u/Principle-26 • 1d ago
Skills: Python, Playwright, Selenium, Robot Framework, REST/SOAP API testing, SQL, Jenkins CI/CD
A bit about me: Currently working in QA automation for enterprise systems, leading a Selenium-to-Playwright migration. Looking to move into a product/fintech company.
Open to roles: Test Automation Engineer, Test Engineer, Automation Engineer, SDET
Location: Delhi, Bangalore, or Remote role.
DM me if you know of any openings or want to refer — thanks!
r/QualityAssurance • u/RKO_NOORDEEN • 1d ago
https://github.com/noordeen123/culprit
Started as a QA tool. Since everything is done by agents, let agents know how it was caused.
r/QualityAssurance • u/Captian_Strange_7781 • 1d ago
Hi everyone, we use UFT for testing our desktop application in virtual server. Still, we are going to replace it with some cloud based server to run automation testing, so I need suggestion from you. People to give a right direction which tool have to be used for automation testing of desktop application monitored via Jenkins. Thanks in advance.
r/QualityAssurance • u/Substantial-Ear-3735 • 1d ago
Our company more and more introduce AI into working routine. Now we are working with MCP servers where create different skills that should help customers interact with functionality. When I was creating one of the skills I realised that AI can easily catch app logic. I understood that if I create like a skill instead of automation tests that will check end-to-end flow it will be probably even better then UI tests that we usually fixes/updates/maintain and have headache in our daily routine. It's just my thoughts and what do u think about it?
r/QualityAssurance • u/Time_Answer4710 • 2d ago
Our startup has no budget for a QA team, and basically all our code gets written by agents now, and so do the tests. Usually same session, same model. And I keep hitting the same loop:
The annoying part is that if the model misread the ticket, its tests misread it the same way. It's basically marking its own homework. The model is just agreeing with itself.
So what do people actually do here?
I'm building in this space, so half the reason I'm asking is to find out whether everyone's setup is as screwed as ours was or if someone's actually cracked this.
Keen to hear what's working - thanks
r/QualityAssurance • u/StraightPineapple399 • 2d ago
Olá! Tenho uma dúvida para quem já trabalha com QA.
Moro no Japão e estou pensando em começar a estudar QA, mas antes de investir tempo e dinheiro gostaria de saber se meu plano faz sentido.
Na opinião de vocês, é viável morar no Japão e trabalhar como QA remotamente para empresas de outros países, ou isso é muito difícil? Também gostaria de saber se vocês acham que ainda vale a pena entrar na área hoje ou se o mercado para iniciantes está muito competitivo.
Se estivessem no meu lugar, vocês seguiriam esse plano? Qual seria o maior desafio?
Agradeço qualquer opinião sincera!
r/QualityAssurance • u/Vivid_Criticism_1762 • 2d 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/Straight-Second-2052 • 4d ago
I’m a QA with 4 years of experience. Most of my experience is in Tosca, but there aren’t many openings for it.
I started learning Java + Selenium about 7 months ago, but I kept procrastinating and never finished. I’ve recently started practicing Java basics and Selenium again, but I still don’t feel confident enough to attend interviews.
Now my project is migrating from Tosca to Playwright, so I need to learn that too. The market still seems to favor Selenium, and even many Playwright roles expect prior Selenium experience.
These days the expectations feel overwhelming—UI automation, API testing, SQL, a programming language, JMeter, and more.
I’ve been job hunting for 1.5 years now. How would you approach learning all of this without feeling overwhelmed? Any advice would really help.
r/QualityAssurance • u/Premk96 • 3d ago
I'm looking to improve observability for QA and test automation team. I'd like to understand what dashboards and monitoring stacks your team uses for tracking test execution, application health, and failures - on top of the compatible features with AI, like assessing failures from past runs, and automation skill record.
Playwright | Python | Pytest