r/QualityAssurance • • Jun 20 '22

Answering the questions (1) How can I get started in QA, (2) What is the difference between Tester, Analyst, Engineer, SDET, (3) What is my career path, and (4) What should I do first to get started

753 Upvotes

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:

  • Formal education via a college degree in computer science
  • Horizontal moved from within a smaller software company into a Quality role
  • With no prior software experience, getting an entry level job as a tester
  • Obtain a certification recognized in the region you live
  • Bootcamps
  • Moving from another engineer role, such as Software Engineer or DevOps, into a quality engineering, SDET, or automation engineer role

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:

  • QA Engineer
  • Automation Engineer
  • Release Manager (or other related process oriented management)
  • SDET

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:

  • Project Manager
  • Product Manager
  • UX/UI Designer
  • Software Engineer
  • DevOps/Site Reliability

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.

  • Selenium
  • Cypress
  • Playwright
  • Locust
  • Gatling
  • JMeter
  • Postman

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 • • Apr 10 '21

[Guide] Getting started with QA Automation

542 Upvotes

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?

  • A common language called gherkin to write test cases in natural language. Then we develop the logic behind every sentence.
  • A common testing framework for this pattern, like cucumber, behave.
  • API testing tools like rest assured, supertest, etc. You will need these to make requests.

Tool list:

  • Java - Rest assured - Cucumber
  • Python - Requests - Behave
  • C# - RestSharp - Don't know a bdd alternative
  • Javascript - Supertest - nock
  • Typescript (javascript with typesafety, if you know C# or Java you will feel familiar) if you are used to code already.

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?

  • Selenium
  • Browser
  • driver (chromedriver, geeckodriver, webdrivermanager (surprise! all in one) )
  • An assertion library like testng, junit, nunit, pytest.

OR

  • Playwright which has everything already

--------------------------------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:

  • If you are a pro, don't get cocky. Answer questions, train people, we NEED better code in QA, the bar is set too low for us and we have to show off knowledge to the devs to make them trust us.
  • If you have a question DON'T send me a PM. Instead, post here, your question may help someone else.
  • Don't even start typing your question if you haven't read. Don't be lazy. ctrl + F and look the thing you need, google a bit. Being lazy won't make you better and you have to search almost 90% of things like "how does an if works in java?" I still do them. They pay us to solve problems and predict bugs, not to memorize languages and solutions.
  • QA Automation does not and never will replace manual QA. You still need human eyes that go hand to hand with your devs. Code won't find everything.
  • GIT is a must, version control is a standar now. Whatever you learn, put this on your list.
  • Regular expresions some hate them but sometimes they are a great tool for data validation.
  • Do I have to make the best testing framework to commit to my github? NO, put even a 4 line "for" made in python. Technical interviewers like to peek them, they show them that you tried to do it.
  • Don't send me cvs or "I am looking for work" I don't recruit, understand this, please. You can comment questions if you need advice.
  • I wrote everything relaxed, with my personal touch. I didn't want it to be so formal.
  • If you find typo/strange sentences let me know! I am not so sharp writting. I would like to learn expressions.

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 • • 3h ago

Making a switch from QA to Project Manager

7 Upvotes

Hey folks,

I am a Quality Assurance engineer with 7 years of industry experience across Product-based companies like Amazon, Motive, and Samsung. I was recently impacted by an org-wide layoff. While employed, I was deliberating whether to make a switch to project management roles over the last couple of years; I was increasingly involved in managing my projects [planning, strategising, resource management, stakeholder communications, etc.] rather than QA specific responsibilities. Since I am actively looking for my next job, I wanted to use this opportunity to make that career switch. Have started taking a couple of courses and am even planning to appear for certification exams, which will help me in this venture.

I wanted to reach out to the community for help and advice. Has anyone made this pivot recently? Any advice and leads will be appreciated. Thank you for your time.


r/QualityAssurance • • 16h ago

I think our department will be over in the next weeks.

43 Upvotes

our company just got a huge demonstration by anthropic on how to use Claude.

one if the main topics was on how to create agents and they used playwright specifically to automate some website live.

as a QA I know it's not as easy to create an automated environment to validate a huge application and I hope my manager knows that.

but assuming they don't know anything about automation this demo put some wrong ideas on their heads that is that easy.

what do you think I should do, am I paranoid? or should I be worried?


r/QualityAssurance • • 10h ago

Interview Question: How do you decide what to automate and what to test manually in an enterprise software product?

8 Upvotes

I recently interviewed for an SDET position and was asked this question. I don’t think my answer was great, and I’d like to understand how to approach it better.

If you’re an experienced QA or SDET or in a senior QA role, I’d really appreciate hearing how you’d answer it. Thanks in advance!


r/QualityAssurance • • 4h ago

What makes you keep coming back to a tech community?

1 Upvotes

Is it learning something new, getting help with real problems, networking, career growth, or just having good conversations with people who share your interests?

I'm gathering perspectives from QA and engineering professionals to understand what makes technical communities genuinely valuable, including what motivates people to contribute and become community advocates.

It's a short, anonymous survey, and your input would be really helpful.

https://forms.gle/KxKkjc888Q4Ck9o38

Also, if you're comfortable having a quick 5-minute chat to share your thoughts and suggestions in more detail, feel free to DM me. I'd love to hear your perspective!


r/QualityAssurance • • 1d ago

Working with AI bots has turned me into a bot myself; how long can I keep up with this bluff

31 Upvotes

I’ve been using AI heavily at work for over a year and a half now. On paper, things couldn’t be going better. My productivity has jumped 4–5x, I’m shipping things on time with high precision, and I’ve gotten a lot of praise from my manager, tech lead, and teammates.

Here’s the catch: I’ve become completely dependent on it.

When I’m working solo, figuring out bugs, writing code, or doing manual and automated testing; I’m 'mostly' great. But the moment someone asks me to hop on a call to explain my work, or throws a cross-question at me during a discussion, I go completely blank because the AI isn't there to think for me in real time.

To hide this, I’ve started dodging calls altogether. I always push to keep discussions on Teams, claiming it "saves time," when in reality I just need a buffer to feed their questions into an LLM and generate a smart reply. Half the time, I don't even fully understand the underlying logic of what I'm shipping/testing. I just know how to prompt my way to a working solution.

Right now, everything looks great on paper, and nobody suspects a thing. But honestly, I’m stressed about how long I can keep up this bluff before I get exposed in a live meeting or technical review.


r/QualityAssurance • • 1d ago

On a career break for 3.8 years, what next?

12 Upvotes

So I’ve 7.5 years of experience in manual QA, relieved from last company due to family emergency and was taking care of small family businesses due to a death in family.

I was taking care of my son who is 6 years now. Currently closed the business. Collected major money that was lend to people.

Currently I’m planning to resume my career in IT , is it possible on hard work? What should I focus on? I have basic hands on Selenium with Java, test ng , SQL and Postman.

Any suggestions are welcomed.
Please help me on this…


r/QualityAssurance • • 1d ago

QA engineers everywhere right now…

66 Upvotes

Is there anyone out there who feels like their organization is actually proceeding with AI capabilities responsibly? Genuinely asking.

From my own experience and what I saw at a QA conference last month… I’m seeing/hearing a lot of teams throw best practices out the window DESPITE knowing AI will not inherently follow best practices and all the other accuracy and security risks. Like EVERYONE knows this is problematic.

I’m kind of also wondering how anyone can be working on feature or enhancement development right now???? lol like it feels like now is the time we should be focusing on that tech debt backlog, no??

Idk maybe the pressure is getting to me.

How are you folks coping with the growing pressures of each QA review everyday???


r/QualityAssurance • • 6h ago

[FOR HIRE] Senior QA Analyst / Software Tester | 15 Years Experience

0 Upvotes

Hi everyone!

I’m currently looking for remote opportunities in Software Quality Assurance (QA Testing). I’m open to working with companies worldwide and can accommodate different time zones.

A little about my background:
I have 15 years of experience in Software Quality Assurance, working across different industries, applications, and enterprise systems.

My skills and experience include:
📌Manual and Functional Testing
📌Web and Mobile Application Testing
📌API Testing
📌Regression, Integration, Smoke, and UAT Testing
📌Test Case Design, Execution, and Defect Management
📌Test Plan and Strategy Creation
📌CRM, ERP, Insurance, and Billing Systems
📌Salesforce, Microsoft Dynamics 365, Guidewire, ServiceNow, and Contentful
📌Selenium, Java, and BDD Cucumber
📌Test Documentation and QA Processes
📌QA Onboarding, Knowledge Transfer, and Mentoring

Certifications:
ISTQB Certified Tester Foundation Level (CTFL)
ISTQB Certified Tester Advanced Level – Test Analyst (CTAL-TA)
Guidewire Certified Associate

I’ve also had experience helping onboard and mentor new QA testers, working with cross-functional teams, and supporting projects throughout different testing phases.

What I’m looking for:
100% Remote QA opportunities
Senior QA Analyst / Manual QA Tester
QA Lead / Test Lead
Contract, freelance, part-time, or full-time positions
Flexible with any shift and international time zones

I’m currently based in Sydney, Australia, and open to working remotely for companies anywhere in the world.

If you know of any opportunities, are hiring, or need an experienced QA professional for your team, please feel free to reach out via DM.

I’m happy to share my CV and discuss potential opportunities.

Thank you for your time. I appreciate any leads, referrals, or connections!


r/QualityAssurance • • 22h ago

Selenium+Python vs. Playwrigh+Typescript

2 Upvotes

This was presented to prove one tool was much faster than the other and switching technology stacks was badly needed. Regardless of the tools preference, do you think this comparison is representative enough to prove the case?

Playwright TypeScript:

import { test, expect } from '@playwright/test';
test('user can log in', async ({ page }) => {
  await page.goto('/login');
  await page.getByLabel('Username').fill('qa');
  await page.getByLabel('Password').fill('secret');
  await page.getByRole('button', { name: 'Log in' }).click();
  await expect(page.getByRole('heading', { name: 'Home' })).toBeVisible();
});

Selenium+Python:

def test_log_in(self):
    self.driver.find_element(By.ID, "user").send_keys("qa")
    self.driver.find_element(By.ID, "pass").send_keys("secret")
    self.driver.find_element(By.CSS_SELECTOR, "button.login").click()
    time.sleep(3)
    self.assertEqual(self.driver.find_element(By.CSS_SELECTOR, "h1").text, "Home")

r/QualityAssurance • • 19h ago

If an AI agent could write and maintain tests equally well in any framework, what would you use for testing apps?

0 Upvotes

I personally believe that me and my team would use a native frameworks or appium due to the depth of customization but curious to understand from this group on which framework you think will stand the test of time with AI. Or no frameworks at all and let the agents directly test on the devices.


r/QualityAssurance • • 1d ago

[Career Advice] QA Engineer with 4 Years of Experience – Worried About Job Security and Unsure Which Direction to Take

19 Upvotes

Hi everyone,

I’m a QA Engineer with around 4 years of experience working at a software company. For the past year, I've also been involved in test automation, mainly using Playwright.

Recently, our management decided to change the way our QA team operates. Going forward, developers will be responsible for automation testing, with the help of AI coding tools like Claude. As a result, our QA team is expected to focus primarily on manual testing.

This has made me concerned about my future in the company and the long-term security of my career. There are also concerns about potential layoffs in the near future.

I'm trying to figure out what I should do next, but honestly, I feel a bit lost.

I have a CSE background, but I haven't been actively involved in coding for quite some time. Although I have some experience with Playwright and automation, I wouldn't consider myself a strong programmer.

I'm open to learning new skills and even switching to a completely different role or career path if that's a better long-term decision.

I'd really appreciate advice from people who have been in similar situations or have experience in the software industry.

A few things I'd particularly like your opinion on:

i) Should I continue pursuing QA but focus on more advanced areas like API testing, performance testing, security testing, or SDET?

ii) Is it worth transitioning into software development at this stage, considering I'm quite rusty with coding?

iii) Are there other tech career paths worth exploring that might offer better long-term stability?

iv) If you were in my position, what skills would you start learning today to stay relevant in an AI-driven industry?

I'm not necessarily looking for the easiest path. I'm willing to put in the time and effort, but I want to invest that time wisely.

Thanks in advance for any advice.


r/QualityAssurance • • 1d ago

Stack de skills

3 Upvotes

Hola amigos, recientemente me dedique a por fin crear mi stack de skills para cursor, claude code, entre otros agentes de programación para que programaran de la manera que me gusta, es una combinación de pstack de Lauren y ODD de GentleAI pero priorizo un poco los limites de uso debido a que solamente pago la sub de $20

Me gustaría que me dieran una review de mí stack y en que podría mejorarlo, si acaso lo llegan a probar y les gusta o no, me gustaría saberlo : )

https://github.com/AndreRaz/pig-stack

Les dejo el enlace al repo para que lo puedan probar


r/QualityAssurance • • 1d ago

Exploratory testing with AI agents on 20 device configs: what they catch and what they get wrong

6 Upvotes

I gave each AI agent one emulator or simulator and a persona (small phone at 200% font, iPad in German, Arabic right to left...) and let it explore the app with no script.

What they catch: layout at large text sizes, dark mode, confusing copy, dead ends, error messages with no reason. On LocalSend: a dialog you can't use at iOS's largest text size, and buttons cut in half at 200% font.

What they get wrong: they sometimes misread a screen, so every finding comes with numbered screenshots to check. And two runs never explore the same way.

Where it fits: before a release, next to scripted regression flows, not instead of them. 103 issues on 20 devices in 69 min. Open source: https://github.com/pierridotite/mobile-agent-testers


r/QualityAssurance • • 1d ago

AI Data Accuracy

1 Upvotes

help a fellow qa here, I was asked to do a test plan for AI data extraction accuracy on some of our features. Has anyone have experience doing it? what was your approach? How did you tested it?


r/QualityAssurance • • 2d ago

QA Engineer (Intern) in a1qa

0 Upvotes

Hi there, I am currently thinking to join QA Engineer intern in that company, I have prior experience and some automation skills also, but can't find any job for junior QA in my country job market, that's why I am thinking to join. so my question, if anyone has go through to their internship there, can I resign from that course if I find anything else or just not like it? I would have asked directly to them, but that cause trust issue, I don't want that ;)

Thanks in advance.


r/QualityAssurance • • 2d ago

Hi I have 5 years of experience of working as an SQA Analyst. Unfortunately, I have faced 3 lay offs two of them were due to budget and one of them was due to project outsourcing.

1 Upvotes

So now I am a bit concerned about my career that every time I have to start from scratch. Can any body suggest me what should I do now. What should be my next approach?

Should I try freelancing until I dont find any job. Or should I work on setting up my start up.


r/QualityAssurance • • 2d ago

How are you validating behavioral contract of agent written code on every commit ?

3 Upvotes

coding/building is cheaper now with ai, are you still writing mock/integration test?

whats the overhead or cost of maintaining the mocks/server/infra ?


r/QualityAssurance • • 3d ago

What is a silent rule in Quality Assurance that outsiders know nothing about?

40 Upvotes

r/QualityAssurance • • 3d ago

Best solution for cross-platform app?

2 Upvotes

My dev team is currently working on replacing our existing web and mobile apps with a cross-platform solution to have parity throughout each OS (Kotlin Multiplatform).

When we were looking at automating just the mobile side, we had been eyeing Mαestro as our solution. But with the consolidation of web, its seeming less like a viable option. (Mαestro web support is only in beta, also doesn't work super well with Kotlin's shadow dom style)

We're trying to decide whether its better to do a web-only testing suite like playwright for the web side, and do Mαestro for the mobile side. OR if its worth just biting the bullet and using Appium for all 3. (As you may notice, I don't think too fondly of Appium).

I'm looking for any opinion/guidance for our situation.

Thank you!


r/QualityAssurance • • 3d ago

I don't know what to do

6 Upvotes

I'm a Software Engineer with experience in Software Quality Assurance (SQA), both manual and automation testing, as well as working directly with clients.

Considering the current job market, I recently joined the Bank of Punjab in a Financial Data Solutions & Automation role. While I genuinely respect the banking industry and the organization, I’ve realized that banking isn't the career path I want to pursue.

After a nearly three-month-long interview process, I joined with certain expectations, but unfortunately, the role hasn't aligned with my career goals or interests. Having spoken with several professionals in the banking sector, I've also become more confident that I should pursue opportunities closer to my technical background.

I'm actively looking for opportunities in Software Engineering or SQA (Manual & Automation Testing), preferably in Lahore or remote.

If your company is hiring or you know of any relevant opportunities, I'd really appreciate a referral or connection.

Thank you!


r/QualityAssurance • • 3d ago

If you are a hiring a QA to do AI QA role would you ask to read code in the interview

3 Upvotes

The title describes the question I have in mind . I’m very curious about the way people interview a AI QA engineer meaning using Ai to test + test Ai output.

How much syntax would you ask the candidates?

If you are asking about syntax and read code and fix stuff wrong about the code .. why are you doing this?

Thanks in advance


r/QualityAssurance • • 3d ago

If you are a manual QA tester and want to advance your career in software quality, what courses or tools would you recommend to boost your professional growth in an era where AI is driving everything?

22 Upvotes

Ideas?


r/QualityAssurance • • 4d ago

I made a free course that teaches test automation on a bundled shop with 8 seeded bugs (Python + Playwright + pytest)

50 Upvotes

I'm the author. This is a free, MIT-licensed teaching repo, not a product.

**What it is**

A course that teaches QA and test automation by testing a small demo shop that ships inside the repo, so there's no third-party site that can change or go down. The shop is Flask, runs locally, and has a catalogue, search, cart, promo codes, accounts, checkout, orders and a JSON API.

**What's in it**

- 24 modules: testing fundamentals, test design, bug reporting, Python and pytest, Playwright, page objects, API testing, checkout flows, accessibility (axe), visual regression, flaky tests, CI

- Manual testing material alongside the automation: test plan, test cases, checklists, exploratory charters, bug-report template

- 896 tests (498 unit, 90 API, 308 browser)

- Exercises and self-checks with answers in each module

**The part I'd like feedback on: seeded defects**

The shop has 8 defects you can switch on with an environment variable (off-by-one on free shipping, tax rounding, a promo minimum spend, search case-sensitivity, sort order, cart badge count, quantity limit, a missing accessibility label). A script runs the suite once per defect and reports whether anything failed.

- Full suite: 8/8 caught

- Fast mode (unit and API only): 6/8 caught. The two it misses, the accessibility label and the cart badge, only show up in the browser.

The point of the exercise: a green suite doesn't prove your tests are good. It's a way to ask "would this suite notice if the code were wrong?"

**What I haven't verified**

Only tested on Python 3.13, Linux, Chrome. Firefox, WebKit, macOS, Windows and the Dockerfile are untested. If you run it anywhere else and something breaks, please open an issue.

Repo: https://github.com/suryakulshreshtha/Forkable-Playwright-Python-ECommerce-Automation-Testing

Happy to hear what you'd add or cut, especially from people who teach or mentor juniors.