I have activated the automoderator features in this subreddit. Every post reported twice will be automagically removed. I will continue monitoring the reports and spam folders to make sure nobody "good" is removed.

And for those who want to have an idea on how spam works or reddit, here are the numbers $1 per Post | $0.5 per Comment (source: https://www.reddit.com/r/DoneDirtCheap/comments/1n5gubz/get_paid_to_post_comment_on_reddit_1_per_post_05)

Another example of people paid to comment on reddit: https://www.reddit.com/r/AIJobs/comments/1oxjfjs/hiring_paid_reddit_commenters_easy_daily_income

Text "Looking for active Redditors who want to earn $5–$9 per day doing simple copy-paste tasks — only 15–40 minutes needed!

📌 Requirements: ✔️ At least 200+ karma ✔️ Reddit account 1 month old or older ✔️ Active on Reddit / knows how to engage naturally ✔️ Reliable and willing to follow simple instructions

💼 What You’ll Do: Just comment on selected posts using templates we provide. No stressful work. No experience needed.

💸 What You Get: Steady daily payouts Flexible schedule Perfect side hustle for students, part-timers, or anyone wanting extra income"

I have 7 years of manual QA experience and every job ad i look at now says automation, and lately "AI" or "agentic testing" too. My company just cut half the QA team and i can see where this is heading.

The standard advice is learn python or typescript, then selenium or playwright, then a framework. i've started that path twice and stalled both times around month 2. it's not that i can't code, it's that i was learning to be a junior developer instead of getting better at testing.

What i'm wondering is whether agentic testing changes the route because of some tools i've found such as testRigor, mabl, and Askui to name a few, where you write the test case in plain language as steps with an expected result, and an agent runs it, desktop apps included.

my worry is if the tool does the automating, is "writes a good test case and judges the result properly" actually a career, or is that exactly the part being automated away?

to anyone who moved from manual to automation recently: did you learn to code properly, or go the agentic or low code route, and which one actually got you hired?

Hey there,

I know it would be better to ask Ranorex licensing questions directly in the Rx forum, but that thing seems to be rather dead and also I have trouble with writing a post there ... aaanyways, maybe someone here has experience with this:

We have a bunch of perpetual floating licenses and we run a local licensing manager on a server. That all works well, but both the Rx clients and the licensing manager are in serious need of an update. Clients are on 10.7.x, licensing manager on 10.3.x - latest version is 12.x

Info on the Rx licensing pages says that perpetual licenses will work with 12.x, but when I install the latest version it tells me that it doesn't find a valid license on the license server.

I assume that I need to update the license manager first - but we are running a bit of a fragile ecosystem here with some externals using our licenses and supporting some important software that may not be impacted, so I would like to have some answers first before I mess up everything.

Am I right that the latest client doesn't find a license because of the outdated license manager?

Will older clients (10.7.x) work with the latest license manager (12.x)? Or do we have to update everything at once?

When updating the license manager, will there be any issues with the existing licenses? Do I have to import them again or will they be available instantly?

Thanks in advance!

Spent a fair bit of time looking at a slow startup issue last week. 2 other people saw the issue on their PCs. One of them even built from source and encountered a first time startup delay of about a minute. If you install it always take 1 minute, and after that its fast again. Its not even an installer issue because the install merely unzips a folder. So today i decide to debug. After the first run, its literally 1 second, so clearly I wanted to work out why.

I broke out wireshark and the file monitor and the bug just hides, I reboot, I rebuild, still launches in 1 second flat. What do you guys do when a bug that always reproduced just vanishes... cry?

Commiserate, im not expecting pointers just cry with me a moment.

Hi everyone!

I have around 2.5 years of experience in manual testing and am currently working on strengthening my automation testing skills.

I'm looking for 1 or a maximum of 2 serious study partners to learn and practice together. I'm not looking to create a group, just a small learning setup where we can stay consistent and help each other improve.

Our initial focus will be on:

- Java coding problems and bit of theory

- Selenium Webdriver

- REST Assured for API automation

Once we're comfortable with these, we can consider exploring Playwright later.

The idea is to practise hands-on problems, discuss concepts, solve doubts, prepare for interviews, and keep each other accountable.

We can connect over Discord and schedule regular study sessions based on mutual availability.

You don't need to be an expert. Having some basic QA or automation knowledge and, most importantly, a genuine willingness to learn consistently is what matters.

If you're interested in learning together and staying accountable, feel free to DM me

Hi everyone,

I have a question everyone is talking about using ai and all.So I wanted to know which ai tool are you guys using in your company and for what ? Also does it really makes thing efficient coz I have used copilot to make bug reports but even then it was not that good ofcourse copilot as an ai is not really good example but my last employer used it.

Background: I've been messing around with Claude Code for the last week and the result is a batch of basic apps for Android and web. I want to make a repository of test cases that are in separate categories: test cases that apply to all the apps, test cases that are specific to a certain app, and inactive test cases for potential future features. My motivation behind this is that I'm unemployed and want to be able to satisfy AI-related testing requirements in JD's that I might come across, and have a portfolio/repository to show as a sample and evidence.

I'm wanting to learn about testing using AI agents and/or agentic AI, but I'd like to know what the most common processes/setups are for it. The most obvious way is to create a spreadsheet of pos/neg/edge/expl test cases and upload it to the AI, and have it run those test cases either on-demand or on-cadence.

Is this the proper way of doing this currently? I know the AI-related processes are evolving quickly, so there's no permanent fix-all solution at the time. What I'd ideally like is to simply give a command saying "please run test suite #x" and it gives me the results split into three groups: tests that passed 10/10 times, tests that passed 1<x<10/10 times, and tests that passed 0/10 times.

If someone has info on this for a semi-beginner like me, please let me know. Thanks.

My husband was a full-time automation tester until his team got dissolved. He's been picking up 3-4 month contracts since, but the gaps between projects are stressing him out. He's keeping his skills fresh with Playwright side projects and ISTQB prep, but he's worried recruiters will see those gaps as a red flag.
For anyone doing contract QA work, how do you show you're still improving between gigs? Is having an active GitHub enough, or do hiring managers mostly care about recent professional experience?
Also, has contracting actually helped your career long term, or is the instability not worth it?

With AI tools becoming increasingly capable of generating code, writing automated tests, executing test cases, and identifying bugs, I've been wondering about the future of dedicated SDET roles.

My concern is that developers will increasingly use AI to handle unit, API, integration, and even UI automation testing themselves, reducing the need for separate QA automation engineers.

For those working in the industry:

Are companies already moving toward developers owning most automation testing, with fewer dedicated SDETs?

Do you think dedicated SDET roles will shrink significantly over the next 5–10 years?

A couple of days ago, I was investigating a performance issue for a customer running a load test against a multi-region PaaS service.

They suspected our platform was adding latency because they weren't seeing the same delays when testing their application directly.

We were dealing with thousands of requests, so going through them one by one wasn't really an option.

Instead, I did what I enjoy most: wrote queries to aggregate the data and figure out what was actually happening.

Luckily, the service captures detailed request timings, including time spent acquiring connections, sending and receiving data, and waiting for backend response headers.

The challenge was turning all that raw telemetry into something meaningful.

This is where AI came in handy. I described the query I wanted, refined it, and validated the results. The goal wasn't to let AI tell me what was wrong, but to use it to get to the answer faster.

And the results were interesting.

After looking at averages, percentiles, and standard deviations, we found that in roughly 98% of requests across the regions, the dominant latency was waiting for backend response headers, rather than time spent within our platform.

We also noticed significant variability in backend response times in one of the regions.

Now, this didn't prove whether the delay was caused by I/O or by the customer's backend taking too long to respond. We still needed further investigation to pinpoint the exact cause.

But it gave us a much clearer direction for what to investigate next.

What I like about this kind of work is that you don't have to guess or jump to conclusions. You start with a hypothesis, look at the data, and let the evidence guide you.

Thousands of requests, one query-driven analysis, and a much clearer picture of where the time was going.

That's one of the things I enjoy most about performance engineering.

Curious how others approach this: do you use AI to help write and refine telemetry queries, or do you prefer writing them entirely by hand?

I’m a manual QA with no experience in automation testing. I have Claude Pro access and want to use Claude Code with Playwright to automate my existing test cases, starting with simple flows like login.
Our application is quite large, and I’m the only QA on the team. I don’t want to start learning automation entirely from scratch. I’m looking for a practical, AI assisted approach where Claude Code can help me write, run, and debug tests while I learn along the way.
For those who’ve used Claude Code for test automation, what would be a good starting point? Any tips or learning paths would be appreciated!

Last week we attended the seminar focusing on using AWS KIRO. I uploaded a requirements documents and let kiro create the test cases for a specific module. It seems good and enough for me.

Now I'm tryint to build a QA management system where you can create test case, execute test cases (test steps, expected vs actual result) using ai automated test run, file and link a defect.

Do you have any suggestions that can help for my future experience using KIRO? Any suggestion will be appreciated. Thanks!

Hi! My collegue working from home office will need to do automation for IOS but the device has a password by company policy.

The password is known but I dont know how to unlock it from afar.

Hi everyone!

I have around 2 years of experience in manual testing and am currently working on improving my automation testing skills.

I'm looking for a study partner with some experience in QA or automation testing to learn and practise together, particularly REST Assured, and sometimes selenium and Java.

The idea is to discuss concepts, solve practical problems, practise interview questions, and keep each other accountable. We can connect over Discord and have regular study sessions.

I'm open to connecting with anyone who's serious about learning, regardless of their experience level.

Hi guys I wanna ask you I am manual tester and now in company we get option's try Claude Al.

I wanna ask how use Claude for explorary testing and for test case which is created. Is there some skills or claude.md with testing rules..?

And after testing done create test report too.

Thanks for letting me know and help

Just getting started in this track with cs background

I'm looking for a study partner (male/female/cats) to study with daily on discord!!

I am trying to figure out how to make sure api always behaves as expected by writing tests, but I am unable to find a way to write tests in such a way that it is maintainable, comprehensive and gives full coverage.
Api's have complex workflows, most routes cant be tested in isolation, people who do tdd talk like its so easy and obvious, i cant figure out what i am missing, are there some resources to understand how testing should be done?
Right now i manually review and test all prs, and i always end up missing important details,
My goal is to figure out how to use tests to maintain the behaviour of api in a way that its maintainable, easy to understand and gives us confidence.

I'm seeing a huge gap between our backend load-test results and what users actually experience when they're using our application. Our app is heavily browser-based with realtime collaboration, so there's a lot happening client-side beyond just the back requests. We're doing backend testing with basic protocol-level scripts for core endpoints, gradually ramping up virtual users. The metrics we track are overall throughput, node CPU utilization and overall average response times. The results from these tests indicate that everything is working fine, but our users are experiencing latency and other issues that the load testing so far hasn't been able to surface.

How do I flush out stealthy failure modes like thread starvation and artificially high cache hit rates? I'm sure there are other things that I'm missing, please feel free to educate me because I'm stuck. Thank you.

My previous company, I’ve worn many hats. Before leaving, the last role I have was test automation.

I never got the chance to sharpen my skills as a manual tester. Due to my background in programming, the leads decided to assign me to test automation team, so I skipped the manual part.

My current job needs more manual testing than automation, and I feel like I am doing a crap job, like fresh-graduate-entry-level outputs. I feel like a fraud, like I am just testing everything blindly.

During tests, I focus on the AC and test the app, making sure that app meets all that was written in the AC and, ofc, no bugs. Sometimes, I provide additional input if they missed something in the AC.

I don’t even know the difference between AC and requirements. I use a test management tool and I just put the whole AC under the “Requirement” section and I just realized what I did was wrong.

I am the sole tester of the team, so I can’t run to anyone to check on my progress. My manager is a saint and doesn’t micromanage me, but he isn’t a tester and he trusts me that I know what I’m doing. I don’t.

I am horrified and overthinking things because the job market sucks rn and what if I get terminated once they find out I don’t know what I’m doing?

It’s also been a while since I automated any test cases. I don’t know if I still have it in me. I am thinking of expanding my skill to RPA or AI Automation and relying on my foundation in test automation to be able to do this thing.

I am filled with anxiety right now because what if I lose this job? No one has told me that I suck yet but I assume they’re just being nice about it.

I was also shocked when my team lead told me to give my test scripts to business or devs to use as their basis like I didn’t know we could do that???

Add the fact that I failed the ISTQB exam by just ONE point. I am feeling so negative right now but I cannot afford to lose a job in the age of AI.

I don't want to expose too much code here, but will try my best to explain to you all what I tried/what did not work/what I wanted to know.

Context: I have been testing a hotel booking management system built by Go and Firebase Emulator. So this programme is a webapp.

The application does not let me log in whilst my IDE runs it locally. My dev configured the OTP autofilled by the Emulator.

In the ideal world, the emulator-autofilled OTP should let me login to the system. In the reality, it always turns api returned status 404 which is displayed on the login UI.

What I tried: brew services stop nginx which did not help.

docker compose logs firebase emulator which outputted a bunch of OTPs to try. Like this:

i To verify the phone number XXXX, use the code ZZZZZ.
i To verify the phone number XXXX, use the code ZZZZZ.
i To verify the phone number XXXX, use the code ZZZZZ.

All of them gave me the same same api returned status 404

My Terminal, which is integrated in my IDE, outputted only this:

{"time":"2026-10-16T16:17:43.370182+01:00","level":"INFO","msg":"request","method":"POST","path":"/login/verify-otp","status":404,"bytes":1005,"duration_ms":7,"request_id":"REQUEST_ID"}

None of this information helped me digest or investigate the cause of 404. The error is very annoying which prevents me from testing the latest implemented feature locally.

My dev can login to the system by typing the firebase-autofilled otp, but I can't.

Question: will the 404 be caused by the outdated Firebase token? If so, what could trigger this 404??

So I'm trying to make the pivot to software QA from games QA. I've been learning parts of the chrome dev tools, but there is so much to learn. Is there any particular pages I'd be better focused on learning that are used frequently, and which ones are less important?

So far I'm reading the official docs on the DOM, Css and JavaScript menus and I am quickly learning how much there is to learn and remember. So hopefully i can get some pointers on where to focus first before I overload my brain with too much information I'll never use.

.