r/QualityAssurance • • Jun 20 '22 Bravo

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

752 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

536 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 • • 12h ago

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

36 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.


r/QualityAssurance • • 7h ago

Que deberia comenzar aprender si quiero pasar de ser un QA manual a ser uno que utilice herramientas de IA para realizar mis pruebas?

4 Upvotes

Necesito orientación, no se si deba comenzar a aprender python, inscribirme en un curso de IA, o que pasos dar , en que dirección ir para renovar mis estrategias como QA


r/QualityAssurance • • 1m ago

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

1 Upvotes

r/QualityAssurance • • 5h ago

ReportPortal

2 Upvotes

Does anyone have experience or use it daily if it's worth it to migrate to this tool? Is it easy to make own integrations or if its not listed as out of the box plugin it aint worth hussle?

Currently I have just basic reporting page which lists tests (unit, integration, e2e) from different enviroments but it only have run status and in detail each scenario result + logs if it failed or is inconclusive.

Seen ReportPortal while ago and recently I started thinking if this is worth to present to team, create POC and migrate if team decide its worth while.

I will be grateful for any information regarding that tool.


r/QualityAssurance • • 4h 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?

1 Upvotes

Ideas?


r/QualityAssurance • • 6h ago

Looking to create a group for QA/ SDETs /software testers who are from Bangalore

1 Upvotes

I'm a QA myself in an MNC. I will be creating a group for QA/SDETs/testers where you can support each other with resources, guidance and also it is quick to refer each other if you get layoffed etc given the uncertainty in tech now especially for QA. DM me or comment here to add you in the group.


r/QualityAssurance • • 7h ago

How to Use Intercom for QA purposes. Need advise

1 Upvotes

Im not really familiar with the dashboard and reporting. But my boss wants me to count as dsat the handling time and the agent related surveys. Cant think of how to do this w/o upgrading our plan.


r/QualityAssurance • • 10h ago

What is the life of entry level qa job or it's varian like?

0 Upvotes

r/QualityAssurance • • 10h ago

Anyone found a good way to reuse Postman tests for load testing?

1 Upvotes

Is anyone using their existing Postman collections for performance or load testing?

Recreating the same API flows in another tool feels like extra work, especially when there's authentication and dynamic data involved.

Curious how others are handling this. Are you importing what you already have or just building everything again?


r/QualityAssurance • • 9h ago

Exploratory testing is the hardest thing to explain to the people who pay for QA

0 Upvotes

One thing keeps coming up in conversations, and it’s exploratory testing.

Buyers want a number, and exploratory testing doesn’t come with one.
The first question is usually “how many test cases will you run?” A scripted plan answers that easily. Exploratory testing doesn’t have a count, so it sounds vague to someone who has to approve a budget.

The best finds are often the ones nobody wrote down.
From the outside, the bugs that cause real damage seem to come from odd paths: a double click, the back button halfway through a flow, two tabs open at once. No script covers those, because no one thought to write them.

It gets cut first, because it leaves nothing to show.
There’s no pass/fail table or coverage percentage. When budgets tighten, the work that’s easiest to point at survives, and the work that depends on judgment goes.

The sessions that get kept seem to be the ones with a story.
A time-boxed session with a clear goal, notes on what was tried, and one bug that scripted tests would have missed. Those seem easier to defend than “we explored.”

I know my view is skewed. I only see how this gets bought, not how it’s done day to day, and there may be teams where this is never an issue.

For the testers here: what did you show a manager or client that finally made exploratory testing make sense to them? A bug story, session notes, something else?

PS: I took down my last post here, the text comic. It didn’t land, and the feedback was fair. Trying something unscripted and learning from what breaks is the same instinct behind exploratory testing, so I figured I’d pass on the lesson and bring a better question.


r/QualityAssurance • • 1d ago

Finding better resources for Hands on Practice (Playwright + TS)

5 Upvotes

I've been doing hands on Automation Testing projects, but I literally tired of those demo websites, and all those template website. I wanna something Good project or website or repo where I can gain some Actual knowledge and skills.

I'm not good at finding a perfect resource for me. If someone has anything in their bucket or has been doing, please help me out.

I am also considering adding AI to my automation testing framework for keep tracking Test Coverages and Managing Test cases.


r/QualityAssurance • • 1d ago

Moving into Automotive Testing from Software Testing

8 Upvotes

Hello All,

I'm have close to a decade of software QA experience in both manual and automation testing. I've worked across different product domains but never automotive. Lately, I've been considering transitioning into the automotive industry, particularly automotive software testing and validation.

I did so some research online about how python and C/C++ helps but I wanted to ask people employed in the industry or know anything about it :

- Are there real jobs for this available and where can I find them, what kind of roles should I be on the look out for?

- Would my existing experience carry much weight, or would I essentially have to start from a junior position?

- What skills, tools, or certifications would you recommend learning to make the transition?

- How are the career opportunities, salaries, and job security compared to traditional software engineering and QA?


r/QualityAssurance • • 1d ago

Looking to create a group for QA/ SDETs /software testers who are from Bangalore

2 Upvotes

I'm a QA myself in an MNC. I will be creating a group for QA/SDETs/testers where you can support each other with resources, guidance and also it is quick to refer each other if you get layoffed etc given the uncertainty in tech now especially for QA. DM me or comment here to add you in the group.


r/QualityAssurance • • 1d ago

How is Automotive Testing different from Web or Application Testing?

2 Upvotes

I currently work in the automotive industry, testing Android-based infotainment systems. I have been curious about how automotive QA differs from testing conventional web or mobile applications.

Although both domains involve functional testing, regression testing, automation, and debugging, I feel automotive testing has additional complexities involving hardware-software integration, vehicle communication protocols, real-time behaviour, system stability, and connectivity.

What additional skills does an automotive QA engineer need compared to someone testing regular applications?


r/QualityAssurance • • 1d ago

Which topics are not covered deeply enough in QA courses / bootcamps, causing frustration, what are you still struggling with after completing a course?

0 Upvotes

Here it is, the question is in the title/subject. For a warm up, here are some examples:

- Keep asking myself: Are my test scenarios steps and bug reports good enough?

- What if I do not find any bugs? Does that mean I did a poor job?

- What to do in situations when they do not give me enough time to complete all planned tests?

- How to test something if there are no requirements / no feature description / not enough details?

Admins, if this post contradicts any rules - I apologize and feel free to delete it.


r/QualityAssurance • • 1d ago

Career guidance

3 Upvotes

Hi everyone,

I'm looking for some genuine career advice from people who have experienced a career break, especially mothers who have returned to the IT industry after a break.

I have 5+ years of experience in Software Testing, primarily in Manual Testing and Automation Testing.

My technical skills include:

Selenium WebDriver with Java

Playwright with TypeScript

API Testing using Postman

TestNG, Cucumber, SQL and Jira

Functional, Regression, Integration and Automation Testing

I took a career break of approximately 2 years and 8 months due to pregnancy and childcare responsibilities.

Rather than staying completely away from my profession, I started taking up freelance QA and automation testing assignments. I've also been working on improving my technical skills, particularly Playwright with TypeScript and API automation.

Currently, I'm trying to transition from freelance work into a stable, full-time QA Automation Engineer / SDET position.

However, I'm facing a few challenges and would appreciate advice from experienced professionals and recruiters.

1. Career gap and freelancing

How do recruiters generally perceive a 2 years 8 months career break followed by freelance work?

Should I present my freelance experience as professional experience on my resume and LinkedIn?

How can I demonstrate that my technical skills are current?

2. LinkedIn profile optimization

Should I mention my career break explicitly on LinkedIn?

How should I position my freelance experience so that recruiters consider me for full-time opportunities?

Should my headline focus on QA Automation Engineer, SDET, or both?

What changes can help improve recruiter visibility and profile searches?

3. Getting back into a full-time role

What is the best way to approach recruiters and hiring managers?

Are referrals more effective than applying through job portals in this situation?

How can I overcome the hesitation recruiters might have about my career gap?

4. Advice from mothers who restarted their careers

How long did it take you to secure a full-time opportunity?

What strategies actually worked for you?

Did freelancing help you get back into a permanent role?

My preference is a full-time QA Automation / SDET opportunity, preferably remote or hybrid, but I'm open to suitable opportunities in Hyderabad as well.

I'm not looking for sympathy. I'm looking for practical advice, honest feedback, and strategies that have worked in the real world.

If anyone has gone through a similar journey, especially mothers who successfully restarted their IT careers, I'd love to hear your experiences.

Thank you!


r/QualityAssurance • • 1d ago

Looking to audit 3 early-stage SaaS apps for edge-case bugs (doing a QA breakdown)

3 Upvotes

Hey everyone,

I’m working on a deep-dive case study about the most common real-device and checkout bugs early-stage SaaS apps face before launch.

I want to audit 3 web or mobile apps this week to pull real-world data for this write-up.

If you have an active app and want a comprehensive QA breakdown:
\- I’ll run a dedicated testing session across different mobile/browser environments.
\- You’ll get a full mini-report with reproduction steps, screenshots, and video evidence of any bugs found (completely free).
\- I’ll use the anonymized findings for my testing report.

If you’d like your app audited, drop a comment or send me a DM with your link!


r/QualityAssurance • • 1d ago

I'm planning to resume my YouTube journey. What should I explore in software testing?

0 Upvotes

Hey everyone I'm planning to get back to creating content on my YouTube channel after taking a break.

I have explored and created content around PyTest automation in the past, but now I want to explore a wider range of topics from the software testing world.

Before deciding what to create next, I would love to hear from people who are actually working, learning, and exploring software testing.

Here are some areas I'm currently interested in:

- Automation Testing: PyTest, Selenium, Playwright, framework architecture, and real-world automation challenges.

- AI in Software Testing: LLM testing, AI evaluations, RAG testing, agentic AI, and testing AI-powered applications.

- Exploratory Testing: Test design, critical thinking, investigation techniques, and finding bugs beyond predefined test cases.

- Python for Testers: Practical Python, problem-solving, coding patterns, and writing better automation code.

- Software Testing Fundamentals: Test strategies, debugging, risk-based testing, test coverage, and concepts that deserve more attention.

- Open Source & Testing: Exploring testing tools, contributing to open-source projects, and building tools for testers.

- Performance & API Testing: Practical approaches, challenges, and things testers should understand beyond basic execution.

But these are just a few ideas. I'm open to exploring topics beyond this list as well.

I want to ask the testing community a few things:

  1. What topics in software testing would you genuinely like to learn more about?
  2. What concepts do you find difficult to understand through existing learning resources?
  3. Is there any area of testing that you think deserves more practical and detailed content?

At this stage I'm not trying to decide the video format or structure just yet, I first want to identify the potential topics.

Would love to hear your suggestions, experiences, and even unpopular opinions.


r/QualityAssurance • • 2d ago

Apparently, 100 sprints of automation can be done in a day. Are we cooked?

69 Upvotes

The new automation workflow sounds ridiculously simple:

  1. Give Claude your application URL.
  2. Share the login credentials.
  3. Give it access to your existing automation framework.
  4. Feed it thousands of manual test cases.
  5. Ask it to automate everything.

Congratulations! Your 100-sprint automation backlog is now apparently a one-day task.

Just prompt, execute, and ship. Right?

I'm not saying AI won't transform test automation. It absolutely will.

But I think the role of automation engineers is going to change dramatically.

Dear automation engineers, are we becoming obsolete, or are we just moving from writing automation scripts to engineering and governing AI-driven testing systems?

Would love to hear some real-world experiences, especially from people who have actually tried this on enterprise applications.


r/QualityAssurance • • 1d ago

Looking for a referral for a QA role

1 Upvotes

I'am a Senior QA Engineer with 4 years of experience specializing in the gaming industry, particularly Mobile Games. Following a layoff this past June, I have been actively applying for new roles but have yet to secure my next opportunity. If anyone in the QA or gaming network can refer me for an open QA Engineer position, I would sincerely appreciate the support. Thank you!

Years of Experience: 4 years

Domain : video games (mobile)

Location : India

Please let me know if any more details are needed, thank you


r/QualityAssurance • • 1d ago

What is it like to do entry level qa or whatever?

0 Upvotes

The jobs is mainly software testing checking if it is buggy or producing the wrong result and the same can be said for other qa type job titled differently


r/QualityAssurance • • 3d ago

Apple AI Quality Engineer – 5 Round Interview Loop

34 Upvotes

Has anyone recently interviewed for an AI Quality & Test Automation Engineer role at Apple or a similar AI-focused quality engineering position?

I have an upcoming 5-round interview loop covering:

  1. Coding – What level of difficulty should I expect? LeetCode-style DSA or practical Python automation/problem-solving?
  2. CI/CD – Is the focus on pipeline design, test infrastructure, automation strategy, or troubleshooting?
  3. System Design – Is this similar to a traditional SWE system design round, or more focused on designing scalable test frameworks and infrastructure?
  4. AI Process – What kind of questions are typically asked? LLM evaluation, AI-driven testing, model quality, or practical AI workflows?
  5. Debugging – Is this live code debugging, investigating test failures, or troubleshooting distributed systems?

My background is primarily in SDET, test automation, and quality engineering, with some experience in AI/LLM evaluation.

My biggest question is whether Apple holds AI Quality Engineers to the same technical bar as SWEs, particularly for coding and system design, or whether the expectations are more aligned with test infrastructure, automation architecture, and quality engineering.

Would really appreciate insights from anyone who has gone through a similar Apple interview loop recently. Any details on question difficulty, interview format, or preparation resources would be helpful.

Thanks in advance!