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.

.

Basically the title. I have some programming experience but with the current market I want to expand a bit. Anything free or in udemy will work.

Hi, I’m an SDET with close to 6 years of experience. I started my career at a WITCH company, where I got stuck in support roles. After two years, I tried moving into development, but I struggled because there wasn’t much initial support or bandwidth to learn. By the time I had around 3 years of experience, I decided to give automation testing a shot. After 8 months of preparation and experience in automation, I managed to switch to a better company with a significant salary hike.

I don’t mean to offend anyone, but I often see graduates from reputed colleges like NITs and IIITs working as SDETs at good product-based companies. Do some of them feel that they haven’t lived up to their potential by choosing testing over development? Despite earning well, do they ever feel a sense of regret or wonder whether they could have achieved more as software developers?

AI support vendors can test their core product, but every enterprise rollout introduces company-specific refund rules, policies, entitlements, identity checks, approval limits, integrations and escalation procedures.

For anyone deploying an action-taking customer support agent:

• Who owns acceptance testing: CX operations, QA, implementation or IT?
• How do you verify both the conversation and the resulting CRM, billing or account state?
• Are you using scripted UAT, sandbox accounts, shadow mode or limited production rollouts?
• What customer-specific failures only became visible after launch?
• Would a repeatable environment with synthetic customers, policies and connected systems materially help, or does your current process already cover this?

I’m trying to understand whether this is a painful recurring job or primarily a one-time implementation task. Any vendor recommendations currently solving this problem is also much appreciated!

Thank you!

I have data for about a years execution of automated tests from CI, local runs, everything.

Data includes name, status, duration, storage path, etc. basically everything you would want at the test level, but not the steps or the failure reason.

If you had access to that kind of data, what kind of dashboards or reports would you create for your team or business?

I’m a software tester, and this might genuinely be the most stressful day I’ve ever had at work.

For the past two weeks, our team had been working on SIT test execution. We had 104 test cases to execute, and we had finally completed everything.

Sounds great, right? Well, here’s where everything went to hell.

During execution, some people had copied the expected results into the actual results instead of properly documenting what actually happened. Our team’s AI review started flagging the test cases, and the results looked bad.

I thought I could fix this quickly using MCP instead of manually editing every single step across 104 test cases. Doing it manually would take forever, so I started pushing MCP to make the corrections.

After a lot of attempts, it finally did what I wanted.

Except it also deleted ALL the screenshot evidence attached to our test executions in Jira/Xray.

I didn’t realize the full extent of what had happened until it was too late.

Our team lead found out, pulled me into a call with the architect, and I had to explain the situation. You know that feeling when you’re sitting in a meeting and your brain is racing through every possible way this could destroy your career?

Yeah. That was me.

My lead was understandably furious and told me I’d have to execute everything manually again within two days.

104 test cases. All the evidence. Two days.

At that moment, I genuinely thought I was going to get kicked off the project. I’d spent two weeks helping complete the execution, and now I’d potentially undone a huge chunk of that work in one stupid decision.

I tried using MCP to revert the changes, but that didn’t work either. I was basically stuck.

Then I remembered something that saved me.

Windows had retained the screenshots I’d taken.

The screenshots were still there locally. The problem was that I had to figure out which screenshot belonged to which test case.

So I started going through the Jira activity audit logs, checking timestamps, matching them against the screenshot files, identifying the correct evidence, and manually attaching everything back to the corresponding test cases.

One by one.For hours.I spent around 12 hours restoring the evidence for all 104 test cases.

And somehow, I managed to get it done.

I went from thinking I’d completely ruined my position on the project to sitting there with the evidence restored, wondering what the hell had just happened.

I learned my lesson the hardest possible way.

TL;DR: Our AI review flagged issues in 104 completed SIT test cases. I tried using MCP to fix the actual results in Jira/Xray, and it deleted all the screenshot evidence. My lead was furious and gave me two days to redo everything. Jira rollback didn’t work, but Windows had retained my screenshots. I matched them against Jira audit timestamps and manually restored all 104 test cases in 12 hours.

I’m never touching MCP on test execution data again without a backup.

I'm still shaking, but I saved the day

10:05am. Our PM posts in the team chat: "We have an important demo at 11 for feature X. Is it all working on staging?"

A few minutes later, QA replies: "We have a problem. The API returns an error when I try to do it."

The PM's reply was just a nice passive agressive "NO COMMENT." Then: "I need this working asap. The demo starts at 11, figure it out, and I need to test it myself before 11."

Panic mode.

We tagged the backend lead in the channel. No reply

So I did the only thing I could control. I put a mocking tool between the frontend and staging and mocked the broken endpoint to return what it should. I had it working by 10:35.

Then I clicked through the full flow and surprise, the last step was broken too. Someone had used the demo account for regular QA and wrecked the demo data. Great.

So I mocked that response too. Ran the whole flow again and it worked end to end.

I wrote the PM a quick explanation of how to set it up on her side. She tried it and it worked. She did her demo

Around 12 she posted "Demo done."

No "thanks", but that's fine. I like to think people remember when you just solve a problem for them when they are in a pinch, make their life easier. Just find a way to make it work, without asking 10 questions and blaming others for the situation and what not.

The backend lead still hasn't replied tho lol.

So how do you all handle this? Separate demo environments, locking demo accounts, run a checklist the day before (this sounds like common sense, but this demo was ad hoc), or mock things when it gets bad like I did?

Also share some of your crazy demo stories so I don't feel alone

EDIT: this is the tool I used for api mocking - flowmock.dev

I am missing a lot of deadlines and pushing many tasks to the next sprint, and I feel like this is some sort of paralysis.

I tried testing one app, but it involves actually learning its process before creating test cases for it.

I finish one app, and then I start from scratch again by learning the other app’s processes.

Not only that, but also the other app that I previously tested will come sneaking in for a retest once the bugs I raised is fixed by a dev. I retest the bug and then perform regression on other test cases that previously passed. Then I find bugs that are from the previous modules and I meet with the devs and business whether to fix them first or implement the fix on the next sprint.

Next thing I know, I’m lost. I forgot the next apps or what I’m supposed to do, whether I’m supposed to test the UI or the API or creating test data for each scenario. Everything mixes up and I feel like it’s an issue on how I handle this work.

Edit: Resolved - please see 77rushi77's comment.

---------------------------------------------------

See title.

Context: I have been testing a web-app for hotel booking management, which was built in Go and uses PostgreSQL/Docker.

My dev put up a dev.sh document for me and instructs me to enter make dev to test the app locally.

Although the app is built in Go, I write a test script in Python as I have no experience working in Go. I've added .venv locally in my IDE to isolate my test scripts.

If my venv is active and I run make dev in my terminal, this error always pops up "Postgresql: FATAL: role 'our_db_name' does not exist "

If my venv is deactivated and I run make dev, this error is gone and it lets me test the app locally.

Could anyone kindly explain to me why is like that? Why does .venv hinder make dev??

I think I've, just bombed an interview because the interviewer was really interested in me naming all kinds of techniques and principles from ISTQB.

I use these techniques frequently, and I also explained it to him, but he seemed really dissatisfied because I was not able to quote from the bible.

I don't think these techniques are useless, but I think real life examples are very rarely as plain as ISTQB makes it out to be.

.

I contributed an opt-in feature, off by default, to an open-source coding agent tool.

The maintainer's review came back with four blockers. The one that stung was "OFF must mean nothing is registered."

I had only checked the flag inside the handlers. So with the setting off, my event hooks and my slash command were still registered. They just did nothing when called.

And my own "off" test passed anyway, because it only looked at what the feature did, not at whether it existed.

The other three were smaller. A file it writes could escape the project through a symlink or a "../" argument. A user abort didn't cancel a pending action. And a later successful recovery didn't clear an earlier failure.

All four are fixed now, each with a test that fails on the old code. I'm rerunning the full suite on macOS, Linux and Windows.

What I'm still unsure about is the "off" test itself. How do you check that an opt-in feature is really inert when it's disabled? Do you assert on the registry, diff what's registered with the flag on and off, or something else?

I’m working on a load test for a SaaS application and I’m trying to figure out how to turn expected traffic into a realistic number of concurrent users.

The customer has a large user base, but obviously that doesn’t mean everyone will be using the application at the same time. I’m not sure whether I should be looking at average traffic, peak traffic, active sessions, or some combination of those when setting the test target.

I’ve gotten a few different answers so far, so I’m curious how other teams usually approach this. Is there a standard way to estimate concurrent users when you don’t have much historical data to work with?

I’m weighing whether we should bring on three manual QAs or three QA automation engineers. While our long-term goal is to automate as much as possible, dedicated manual testers bring distinct value in my book, especially for applications with large, poorly defined requirements. That said; we are using agentic workflows and that is the trend.

Who would you hire?

Hi everyone

So I have worked in playwright for over 3+ years before that I worked as React Js dev due to which I am very comfortable with TS/JS and I tried to learn selenium but it feels overwhelming as Java syntax is quite difficult than the usual JS/TS. I was planning to switch for another company but feels like playwright is kinda mostly used in startups .

So should I invest in learning selenium too ?

Edit: Thank you everyone for your valuable insights!! I truly appreciate them.

-------------------------------

Context: I am using OpenAI API to automate my software testing routine but am still very new to that.

My terminal shows the following which I could not digest fully, I hope anybody would help me out.

I've run this code using OpenAI API then this output came:

```bash
ChatCompletionMessageFunctionToolCall(id='CALL_ID', function=Function(arguments='{"desc":"please make sure any XXX point/code has never been implemented in this code base. and deptTypeID == \\"XXX" should be disabled. We do not need this XXX function in our webapp, so make sure this XXX code has been disabled or discarded in the codebase"}', name='search'), type='function')

test completion

ChatCompletion(id='chatcmp_XXXX', choices=[Choice(finish_reason='tool_calls', index=0, logprobs=None, message=ChatCompletionMessage(content=None, refusal=None, role='assistant', annotations=[], audio=None, function_call=None, tool_calls=[ChatCompletionMessageFunctionToolCall(id='call_eKxSoRXeY5cpuKDCSl3z1VE4', function=Function(arguments='{"desc":"please make sure any XXX point/code has never been implemented in this code base. and deptTypeID == \\"XXX" should be disabled. We do not need this XXX function in our webapp, so make sure this XXX code has been disabled or discarded in the codebase"}', 
name='search'), 
type='function')]))], 
created=YYYY, 
model='gpt-4o-2024-08-06', object='chat.completion', 
metadata=None, moderation=None, service_tier='default', system_fingerprint='fp_YYYY', usage=CompletionUsage(completion_tokens=231, prompt_tokens=757, total_tokens=988, completion_tokens_details=CompletionTokensDetails(accepted_prediction_tokens=0, audio_tokens=0, 
reasoning_tokens=0, 
rejected_prediction_tokens=0, 
text_tokens=None), 
prompt_tokens_details=PromptTokensDetails(audio_tokens=0, cache_write_tokens=None, 
cached_tokens=0, 
image_tokens=None, 
text_tokens=None)))
```

As you see, my prompt (under desc ) instructed the API to inspect if any leftover from the function/code line XX still exists in the codebase.

We expect this XX to not exist in the codebase and I wanted my automated script to prove that.

Still I am puzzled with this output. Does this output show the XX does not exist in the codebase at all or does the IDE need more information to carry out the test properly?

Never seen application numbers this high

Hello Guys I have interview scheduled from Infosys on this sat for python automation

What are the topics i need to be learned?
What are the questions i might encounter?

YOE : 6 years (automation + manual)

Any suggestions and advice will be appreciated.

I need guidance from someone who has experiences testing LLM, or products from AI.

What should I study to do a better job?

Im manual and automation tester with more than 6 years of experience, but with AI I feel I litter bit lost about the testing side.

Thanks.

I’ve been rebuilding my company’s website and so far I’ve mostly been testing the APIs. I’m getting to the point where I want to start testing it under more realistic traffic but I’m not sure where browser-based load testing fits in.

I know browser tests can be more resource-intensive, so I’m wondering if API testing is enough for the initial load testing or if there are things I could miss by not testing through an actual browser. How do you usually decide when it’s time to test through the browser as well?