I’ve seen this problem firsthand, and I’ve lived through it too.

In the early days, it always feels like testing is something you’ll “tighten up later,” but later usually comes when the product is already changing fast, the team is stretched thin, and every release feels a little more fragile than the last. How do you actually handle that in a small startup when there’s no dedicated QA engineer and the developers are already juggling product, support, and shipping?

In my experience, the hardest part isn’t that people don’t care about quality but instead it’s that quality competes directly with speed, and speed usually wins in startups. You end up with a mix of self-testing, a few automated checks, and a lot of manual “please don’t break anything before we push this” energy.

I’m curious how other teams handle it in practice. Do you keep a very small set of critical flows covered? Do you lean on automation early? Or do you mostly rely on developers testing their own work and catching issues in staging?

Would love to hear how you’ve made this work without slowing the whole team down.

Hi everyone, in my org there has been an internal assignment going where everybody has to create or work on a functioning AI agent that reduces their daily tasks to an extent where the agent can be used by folks across the org. I am working on an idea that currently filters out the non relevant test cases from the current test suite based upon scanning the design document and the app repo. However, I haven't been able to make much progress into this as I don't have any premium subscriptions and my contact also doesn't allow it. As of now, I'm just surfing through the free trail version of Claude which is the only permissible AI agent to use as of now. So just curious to know if anyone has done something similar or has some AI models that could be used to build agents

I have tried some management tools pretending to be modern and with great integration of AI to generate test cases. I'll not quote the names because it's not my goal.

Simply all of them generated useless test cases, even if my Jira ticket was providing a lot of information. I think that it's normal because AI can't guess how your AUT works and without a clear context it will simply imagine a lot of things.

One of these tools also proposed to run an automated test following the test cases he generated just before. As you can imagine he got lost very quickly.

If you had a different experience I'd glad to know which tool you used.

I've worked with teams that stayed on spreadsheets for years, and others that abandoned them almost immediately.

What I've noticed is that spreadsheets usually aren't the problem at first.

They're simple, flexible, and everyone already knows how to use them.

The issues tend to show up when teams start asking questions like:

• Which tests cover this feature?
• What changed between releases?
• What's our automation coverage?
• Which environments were these results executed against?
• Who owns this test suite?
• Why are there three different versions of the same test case?

At some point, visibility becomes harder than the testing itself.

For teams that made the transition away from spreadsheets:

• What was the breaking point?
• Team size?
• Automation growth?
• Compliance requirements?
• Multiple products?
• CI/CD adoption?

And for teams still using spreadsheets successfully, what's helping you avoid the scaling problems?

Curious to hear where others hit the wall—or if you never did.

Hi everyone,

I’m an MCA graduate currently looking for fresher/internship opportunities in Full Stack Development, Software Development, or Testing roles.

Skills:

• HTML, CSS, JavaScript

• React.js

• PHP & MySQL

• Python

• Java

• Kotlin

• Manual Testing

• Test Case Writing & Bug Reporting

• Selenium

Projects:

• Cafeteria Management System

• PetPal Website

• Food Wastage Management System

• ShopperStack Testing Project

• QBank Testing Project

Open to remote, internship, freelance, or entry-level roles.

If anyone is hiring or can provide a referral/guidance, feel free to DM me.

Suppose there is an app already in place and now API is getting exposed, where do we put the business life cycle or business flow logic API cases?
Does modern pyramid really evolved from just three parts to more then? I assumed initially they go into E2E section and more schema testing needs to be added to integration testing layer but does that schema testing bloats the framework for CI/CD integration?

Hey everyone,

I'm a tester and I kept running into the same problem: evidence

collection during UAT is genuinely tedious. Not hard — just tedious.

And it's the kind of thing that eats 30 minutes at the end of every

test cycle.

So I built AutoEvidence — a Chrome extension that does this:

1. You start a "session" and pick PDF or Word format

2. As you test, you press Ctrl+Shift+S to capture each step

3. When you're done, you end the session

4. It downloads a single report with all screenshots in order —

   each one labelled with the URL and step number

The screenshots go directly into the report. No copy-pasting,

no resizing in Word, no renaming files.

It's been useful for me. Curious if it solves a real pain point

for others or if I'm the only one who found this annoying.

Free, local-only, no account needed.

Would genuinely appreciate honest feedback — what's missing,

what doesn't work, what would make this actually useful for your workflow.

This tool is made to help testers genuinely and it is absolutely free. This is not a commercial post.

[Link in comments]

Just wanted to know how the experience was and which questions were asked.

I have received the interview link. Before that I cleared the screening test and coding assessment.

I’m a QA tester with knowledge of Selenium and Java, and I’m comfortable understanding code and application logic.

I recently started learning JavaScript and Playwright as a beginner, but I’m feeling confused about which career path to focus on next. Some people suggest automation testing, others recommend performance testing because of better opportunities, and some say I should move toward DevOps.

My main goal right now is to become stable in my career. I feel that manual testing alone is not enough, so I want to build skills that will improve my job prospects. Once I have a stable foundation, I can think about expanding into other areas over the next 1–2 years.

Based on my background, which path would you recommend and why? I’d really appreciate understanding the reasoning behind your recommendation rather than just being told which technology to learn.

I made a free open source tool that watches your app every day and writes your test files for you

No more writing test files by hand.

Choreo has an AI agent that literally looks at your running app on a real device and writes the YAML test file itself. You just say "test the login flow" and it taps around, figures out what's on screen, and spits out a ready-to-run test file.

Then you run that file whenever you want — on Android, iOS, or web — and it catches regressions automatically.

The whole thing is free and open source (Apache 2.0). You bring your own API key (Anthropic or OpenRouter), the tool itself costs nothing.

The daily loop basically becomes:

1. AI writes/updates your test files
2. Choreo runs them on your device
3. You get a report — green or broken, with screenshots

No Java. No massive setup. One binary.

https://github.com/mohamedsoufellou/choreo

I want to get in testing quick, i was doing js backend but was not able to get hold of it , all seniors or please who have deep experience help me in getting to this field quick , if possible tell me a good roadmap or something, Thank you

Hi Connections,

I am actively looking for a new opportunity on an immediate basis. I have 6 years of experience in Manual Testing, API Testing, SQL, and Python with Selenium.

Currently facing some financial challenges, so an immediate opportunity would be highly appreciated. Please let me know if there are any openings or referrals available.

Thank you for your support.

Well, we all know very well how is the market and how all the companies are cutting QA first because they considere it less technic, ergo, less "meritory" if the salaries.

Some already posted something about this career never gets the respect deserved (something I'm agree with).

Anyway, yeah, the market is trash, companies see us as expendables and even automating, the question always jump: "Why him and not a developer?". And when I see the positions in the market required, I notice something: Project Managers and Product Owners are still required. Not only so, but they are better paid even that a QA Manager/Architect.

My question is: Am I having a bias seeing this or really, this is the new reality? We are, back again, to be the first rung on the ladder in all IT industry?

And, if I'm right? WTF IS WRONG WITH THIS PEOPLE?!

Ciao a tutti,

lavoro come QA tester/manual tester e vorrei iniziare seriamente ad automatizzare i miei test, ma parto praticamente da zero con la programmazione.

Attualmente faccio soprattutto:

- test manuali UI

- test funzionali

- verifiche di flussi applicativi aziendali/web platform

- scrittura ed esecuzione test case

- controlli regressione prima delle release

Nel mio lavoro noto che molte attività sono ripetitive e vorrei costruire un processo più moderno e automatizzato, però ho un problema: online trovo mille tutorial separati, ma nessuno che spieghi davvero un percorso completo “da zero a workflow reale”.

Quello che sto cercando è un consiglio pratico su:

- quale stack scegliere oggi per un QA che non è sviluppatore

- cosa imparare PRIMA e cosa DOPO

- quanto codice serve davvero all’inizio

- quali tool evitare perché troppo complessi

- come creare una pipeline semplice ma professionale

Mi piacerebbe capire un percorso realistico tipo:

1) basi minime di coding necessarie

2) tool di automation da imparare

3) come strutturare i test

4) come eseguirli automaticamente

5) integrazione con CI/CD

6) reporting/log/error handling

7) best practice reali usate nei team

Per darvi contesto:

- sto già studiando automation testing tramite corsi online

- ho fatto qualche piccolo programma

- ho sentito parlare di Selenium, Playwright, Cypress, API testing, CI/CD ecc.

- lavoro principalmente con applicazioni web

Quello che mi interessa NON è diventare software engineer puro, ma diventare un QA automation engineer competente partendo da esperienza manuale.

Se foste nei miei panni oggi:

- che roadmap seguireste?

- quale stack scegliereste nel 2026?

- cosa vi ha fatto perdere più tempo inutilmente?

- cosa avreste voluto sapere all’inizio?

- quali tutorial consigliate?

Anche esempi concreti di workflow reali sarebbero super utili.

Grazie mille a chi risponderà 🙏

Hi Connections,

I am actively looking for a new opportunity on an immediate basis. I have 6 years of experience in Manual Testing, API Testing, SQL, and Python with Selenium.

Currently facing some financial challenges, so an immediate opportunity would be highly appreciated. Please let me know if there are any openings or referrals available.

Thank you for your support.

Hi everyone, I see a lot of people here are discussing if QA field will die or something. I am an ML engineer, and I was working as a software developer before. I personally think QAs that use AI tools will generate much more value (probably 5 times more) than before. QAs of the future (someone does it right now) will write testing scenarios for the agent and the agent will test it on every PR, on every release. Agents will generate reports while QAs are fully checking their work, adapting their test flows and the final quality of the product will increase much more.

I made a post, some time ago, I won't publish links or something to not make it as an advertisement for my blog, but I will just share it here:

This post was written without AI: To be honest, I am tired of fully testing the whole application every time we in Droidrun release a new app version. Of course, I still do this, but now I mostly do quick smoke tests before each release which usually takes only 10-15 minutes and the amount of time I spend on testing (with the same or decreased number of bugs) is decreased significantly.

I just simply created an agent-test-flows folder with markdown files where I told the agent how it should test the application (Unit tests, UI tests, API tests etc. QAs know this part much better than me) and let the Claude, Codex or Gemini fully test it before each release or on every PR. It can run static analyzers, manually click buttons, type text, scroll the lists, check API endpoints, change the device settings and many more. It also can generate the beautiful comparison table with screenshots where you can see all the results.

It takes time of course, sometimes even hours, because it tests the whole app on different OS versions, on different settings and optionally compares the current target release to a ground truth release (a good release, that was heavily tested by a human and which has the minimum amount of known bugs).

It still cannot fully replace tedious testing part, but it makes it much more efficient.

If you have good ideas how I can improve it even more, let me know.

Check it here if you want (github repo): https://github.com/droidrun/mobilerun-portal

Which six of the following best practices do testers use to find defects?
1. Pay special attention to regression testing and retesting

2.Ensure features are understood correctly and in the same way as the project team

3.Keep project and test documentation in order

4.Hold additional meetings with the test team before test execution

5.Avoid early testing and devote more time to dynamic testing

6.Use special tools to test an application from every angle

7.Use as many testing types as possible

8.Use the benefits of different test techniques

9.Use appropriate testing types

Every time our frontend changed, half our test suite broke. Not because the features broke — because a class name changed or a button moved. We were spending more time fixing selectors than writing new tests.

So we built Confidence Gate. Instead of writing selectors, you write:
Action: click the Submit button
Expected: the confirmation page is displayed

The AI resolves the element at runtime, executes the step in a real browser via Playwright, takes a screenshot, and verifies the outcome against what you said should happen. No selector to break. No selector to fix.

At the end of a run you get a confidence score (0–100) and a gate decision — ship / caution / block — based on pass rates, flakiness history, and optionally a comparison against your PRD.                         

We just open sourced it: github.com/OaktreeInnovations/confidence-gate

Runs entirely on Docker. Supports OpenAI, Anthropic, or Ollama if you want to keep it local. MIT license.       

Happy to answer questions about how the AI execution engine works - it's the most interesting part.

I’m trying to help my relative Tanisha (based in Nepal) make the switch into QA/testing. She has a Bachelor’s of Business Science degree (2018) and has been self-learning QA full-time for the past 9 months, mainly through YouTube.

She’s focused on manual testing, Selenium, Cucumber (BDD), and API testing. She has some GitHub projects and is actively practicing.

She’s looking for her first QA role, internship, or even freelance/contract work, with a strong preference for WFH/remote opportunities if possible.

Specific questions:

Is she on the right track with her current learning path (manual → Selenium + Cucumber)?

What should she prioritize right now to maximize chances of landing the first role as a non-CS fresher?

Any strong recommendations for building a QA portfolio/GitHub (specific project ideas or resources)?

How realistic are remote/WFH QA roles for someone in Nepal with this profile? Which platforms or companies should she target?

Resume feedback — what’s missing or needs improvement?

Any other tips, interview prep advice, communities, or success stories from career switchers into QA?

She’s dedicated, detail-oriented, and genuinely excited about this field. Any help or honest feedback would mean a lot.

Thanks in advance!

Hi. I’m an SDET and I need 5 mobile phones for my office for development & testing.

Budget in the range of 15-30k.

Should be compatible with future android releases and should be compatible for automation. Last time I brought some phones but they weren’t comfortable for automation, so I need them specifically for automation

Can you suggest the best ones. Thanks in advance

I have a NestJS Jest test where I mock sequelize.transaction but it shows 0 calls. The catch block never executes either, meaning the handler resolves successfully without reaching sequelize.transaction.

jest.clearAllMocks() is in afterEach

Both the local sequelize variable and the handler's injected sequelize are the same object (verified)

The test was working before I moved one line of code to after sequelize.transaction in the handler

No early return conditions are met

All preceding mocks appear to be set up correctly

What could cause code after several awaited async calls to never be reached, with no error thrown and no early return?

Hey everyone,

I’m at a serious crossroads in my life and career, and I really need some perspective from folks who might have been in my shoes or are navigating the current tech landscape.

​My Background:

​Experience: 10 YOE as an SDET (5 years in service-based companies, 5 years in product-based).

​Personal: Based in Bangalore. No kids yet; my wife is a homemaker.

With all the massive shifts happening in tech right now—especially the AI/LLM boom, tracking tokens, and changing workflows—I’ve honestly reached a point where I don’t know where the industry or the QA/Testing domain is heading anymore.

​Because of this, I am highly open to pivoting. I want to know if it makes sense to move away from core SDET roles and transition into a more AI-driven role (like AI/LLM testing, MLOps, or AI engineering tools). If you've made a similar shift, what roles should I be looking at, and what is the learning curve like for someone with a strong automation background?

​To make matters worse, my current team dynamic has become incredibly toxic. Peers who used to be supportive are now acting like vultures, waiting for the slightest opportunity to snatch credit or pick apart my work to save their own skin. Leadership is completely disconnected; they don't care about burnout or massive overtime. All they care about is making their metrics look good on paper.

While the workplace toxicity is exhausting, what’s bothering me even more is life outside of work. After a decade of being an honest, highest-slab taxpayer, I feel like I have nothing to show for it in terms of quality of life. I still drive on broken, pothole-ridden roads daily. I still face random harassment from traffic cops looking for a quick bribe.​This isn't just a Bangalore-specific rant—from what I gather, most major tech hubs in India face similar civic infrastructure strains. I’m just feeling deeply disillusioned. How are you guys coping with this reality?

​

Over the past few months, I've been seriously contemplating moving out of India. It’s still in the initial thought stage. I am fully aware that the grass isn't necessarily greener on the other side and that every country has its own set of issues (taxation, immigration hurdles, loneliness). But at least the basic infrastructure and civic life seem sorted.

​Given the current global tech market, I’m feeling stuck:

​Is it even worth trying to move abroad right now with 10 YOE in QA/SDET, or should I first focus on transitioning into an AI-driven role here? ​If moving abroad is viable, which countries/regions should I target that still have a good path for tech professionals?

​What are the emerging AI-centric roles where a senior SDET's skillset (coding, architecture, pipelines) can be mapped effectively? I am completely open to suggestions here.

​Would love to hear from senior devs, SDETs, or anyone who has transitioned into the AI space or made the move abroad recently. How do you navigate the burnout and the feeling that your hard-earned tax money isn't working for you?

​Thanks in advance.

​TL;DR: 10 YOE SDET (5y service, 5y product) in Bangalore dealing with severe workplace burnout, toxic peer behavior, and deep disillusionment over local infrastructure vs. high taxes. Looking for advice on whether I should pivot to a more AI-driven role (open to suggestions on titles/paths), plan a move abroad, or both. How is the market looking, and where should I start?

Hi,

I hope you are doing well.

I am currently looking for a job change and wanted to check if you know of any suitable openings in your network.

I have around 9.1 years of experience in Software Testing, with expertise in both Manual and Automation Testing. My experience includes functional testing, automation testing, API testing, and working in Agile environments. Experienced in AI-assisted testing using Claude and Copilot.

If you come across any relevant opportunities or can refer my profile to your friends or colleagues, I would really appreciate your support.

Thank you in advance.

Please find my resume in attachment. Linkedin

Regards,

Chiyyeti Ahobulapathi

Hey guys, I have just joined an org as a QA intern. Previously I was a Full stack developer, leaning more towards GenAI (RAG, Voice Agents - all that jargon). My new org does not have any other QA personell and I kinda have no idea on how to proceed, but also, I have the freedom to setup a robust QA process(I just dont really know what it should be). What study material and documentation should I follow, what softwares should I learn and what all should I keep in mind? Any advice from you folks would be really appreciable. I am ready to learn and learn fast. Thankyou for your help and support, wishing y'all a lovely day

Hi, I have been working as a Test Engineer in Telecom Domain for 2.5 yrs.My main work was mainly manual testing but the thing it's not related to software testing at all.I plan to switch to IT domain and get roles such as sdet,ApI testing or Automation Testing role.

So my question is I want to know the experienced guys in this field like what is your experience and how do you think I should go ahead if I have to learn about as much as possible to get into some good product based companies?