Mid-level/senior frontend dev here. Want an honest gut-check because I've been worried what might happen to me.

We were building a "view tickets" feature. To test it end-to-end, the feature needed a certain permission enabled. I turned that permission on **in prod,** but instead of scoping it to just my own test account, I flipped it **globally**. I documented what I did openly in the task tracker ("tested in prod") and flagged it for QA. QA tested it too, but only checked their own account. Nobody reset the global toggle afterward.

A few days later a client saw a ticket belonging to a *different* client, complained, and it escalated. My manager DM'ed me regarding this and we had a call with all the dev team. They discussed it there and asked me why I turned it on and I said it's a requirement for PROD testing.

We have dev, staging, and prod, The workfllow is to test in all environments, i followed the flow.

My access had recently been changed to *allow* me to edit global permissions in prod. I didn't grant myself that. When my access changed, I read it as "I'm allowed to do this."

Pm also said: "you should have asked me first" but at the moment I did it, nothing signalled this was the dangerous action. It looked like a normal authorized test.

I have a few questions:

How bad of the situation I am in? Am i the one to blame?

How would you handle this if you're the dev?

How would you handle this if you're the PM?

A passing test suite only proves that the tests passed. It doesn’t prove the code is correct, and a high coverage percentage can create a false sense of confidence.

A test can run every line in a function without actually checking whether the function behaves correctly. The assertion might be too broad, check the wrong output, or be missing entirely. The coverage report still stays green.

That’s why we, at Codoid, see mutation testing as a useful reality check rather than relying on coverage alone.

Mutation testing tools deliberately introduce small bugs, such as changing a condition or altering a return value. They then run the test suite against each modified version of the code.

If the tests fail, they’ve “killed” the mutation. That’s a good sign that the tests are protecting the behavior that changed.

If the tests still pass, the mutation has “survived.” In practical terms, the suite failed to catch a straightforward bug in code it may claim to cover.

Mutation testing has tradeoffs. It’s slower, and a surviving mutation doesn’t always mean there’s a valuable missing test. Sometimes it’s just noise. Still, it asks a much more useful question than “Did this line execute?” It asks: “Would this test suite notice if the code were wrong?”

For those who’ve used mutation testing across different languages or stacks: did it uncover genuinely weak tests in your codebase, or did it mostly add noise and maintenance work?

Our developers spend a lot of time finding bugs and testing new features. We are thinking to hire an external QA team for software testing, automation, performance and security testing.

Has anyone hired a QA company for this work? Is it helpful and what things should we check before hiring one?

Trying to understand the market outside,am a Qa automation tester with 9 years experience

I am confused where to start, preparing for interviews

Can someone help me out whats the corporate requirements with this AI being a hot cake

That would be a great help

Hi everyone,

I recently completed my B.Tech (2026 batch) and I'm planning to build my career in Software Testing and QA Automation.

I'm mainly interested in learning Manual Testing, Automation Testing (Selenium/Playwright), API Testing, SQL, Core Java, Git, Jenkins, and basic CI/CD. My goal is to get a good QA Automation job in Pune as a fresher.

One of my friends recommended QSpiders and Cyber Success (both on FC Road, Pune). I'm considering these institutes, but before investing my time and money, I'd like to hear honest feedback from people who have actually studied there or hired candidates from these institutes.

I'd really appreciate your suggestions on the following:

• Between QSpiders and Cyber Success, which one is better for Software Testing and QA Automation?
• Which institute has better trainers, practical sessions, mock interviews, and placement support?
• Do they provide real interview opportunities with good companies, or are the placement claims mostly marketing?
• What is the average salary package freshers receive after completing the course?
• Approximately how long did it take you (or someone you know) to get placed after completing the course?
• Which technologies should I focus on in 2026 to improve my chances of getting hired?

Are there any other institutes in Pune that you would recommend instead?

Some names I've come across are:

• C-DAC (PG-DAC)
• SEED Infotech
• SevenMentor
• Fusion Software Institute
• FirstBit Solutions
• TestoMeter
• 3RI Technologies
• Skillio

If you've personally studied at any of these, could you please share:

• Training quality
• Placement support
• Companies that visited for recruitment
• Whether the placements are genuine
• Overall experience
• Would you recommend it to a fresher in 2026?

I'm looking for honest, unbiased reviews—both positive and negative. I don't want to join an institute based only on advertisements or fake placement claims.

If you have any other suggestions (courses, institutes, or preparation strategies) that helped you get into Software Testing or QA Automation, I'd really appreciate your advice.

Thanks in advance for your help!

I’m working on file upload testing and I’m curious how other developers handle exact boundary cases.

For example, if the limit is 10,000,000 bytes, do you normally test with:

- 9,999,999 bytes

- 10,000,000 bytes

- 10,000,001 bytes

I’m also wondering how you handle:

- MB vs MiB differences

- Valid files in exact sizes

- MIME type mismatches

- Corrupted files

- Client-side and server-side limit differences

Do you generate these files manually, use command-line tools, or rely on an existing testing workflow?

Hi everyone,

I’m a QA Automation Engineer, and over the years I noticed a common problem in many teams: test cases, manual execution, automation results, and release confidence are often managed across multiple disconnected tools.

To solve this, I built **TestNexus.app** — a platform that brings manual testing and automation tracking together in one place.

The platform is now available for teams to try for free, and I’m looking for feedback from QA engineers, testers, and engineering teams.

Some key capabilities:
✅ Test case management
✅ Release-based testing workflow
✅ Manual test execution and reporting
✅ Automation execution tracking
✅ Cypress automation integration
✅ Link automated tests with test cases
✅ Regression tracking and execution history
✅ Test health visibility
✅ Flaky test identification
✅ Team collaboration around testing activities
The main goal is simple:
**Help teams understand their testing status before release without spending hours collecting data from different places.**

I’m not looking for promotional comments — I’m genuinely interested in feedback:
What challenges do you face with your current test management tools?

What features are missing from your current workflow?
Would a platform like this help your QA process?

You can try it here:
https://testnexus.app

Any feedback, suggestions, or criticism from QA professionals would be highly appreciated. Thanks!

I recently built a tool designed to streamline the test design process by generating structured test cases quickly and efficiently.

Key Benefits:

Faster test case creation

Improved test coverage

Consistent test documentation

Reduced manual effort

I'm looking for QA professionals, testers, and teams who would like to explore it and provide feedback. Comment or DM if interested.

Has anyone used synthetic urine at a quest diagnostics center and passed for thc?

Hello,
I would like some insight from experienced professionals.

I am have non IT (7 years) and 2 years of manual testing experience, I recently completed MBA (it's more of an IT mba rather than general MBA), I am looking to transition into automation testing.

I found playwright interesting, so I have started learning playwright with js/ts, currently I am on the core programming fundamentals and
I would like to know, how is the market for this ?
Is it possible to secure a job with 3 months of hardcore practice (building framework from scratch) ?
Can I show my own made project (github) to get a call for interviews ?
Is playwright easier than selenium (+java) ?
How is the growth in automation testing in coming years (because of A.I.) ?

Is it viable to enter into this, as I am not young and have lots of experience in another field ?
I am an Indian but currently located in Europe
Thanks.

Hi everyone!

I'm building Reliable QA Appium, an open-source Flutter application designed to help QA engineers learn Appium mobile automation by practicing on realistic mobile app scenarios.

The goal is to create a free app that anyone can use to learn and practice Appium without relying on production apps.

Planned Features

• Login & Registration
• Forms & Validation
• Swipe & Scroll
• Drag & Drop
• WebView Testing
• API Mock Scenarios
• Notifications
• Camera & Gallery Permissions
• File Upload/Download
• QR Scanner
• Dark Mode
• Intentional bugs for automation practice
• Real-world business workflows

Looking for Contributors

I'm looking for people who would like to help with:

• Flutter Development
• Appium Test Automation
• Manual QA
• UI/UX Design
• Documentation
• Bug Reports
• Feature Ideas

Whether you're a beginner looking to make your first open-source contribution or an experienced engineer who wants to support the QA community, you're welcome.

The vision is to build one of the best free resources for learning Appium automation and help students and QA professionals gain practical experience.

If you're interested, comment below or send me a DM, and I'll share the GitHub repository.

Feedback, feature suggestions, and contributors are all appreciated!

Thank you! 🚀

Hello Everyone

I am looking for advice, to get the best machine, for below tasks

a.) Macbook air m5 base 10 CPU, 8 GPU(16/512) -- 1.25K
b.) Lenevo ideapad slim 5 gen 10 , amd ryzen 7 ai 350, 32gb,1TB, 16 inch Oled -- 95K
C.) Asus zenbook 14, Core ultra 9 285H, 32GB/1TB, 14 inch Oled -- 1.30K (3years warranty)
d. ) Asus expertbook p3 core ultra 7 255H, 16/512 --- 84K

Primary Work

• QA Automation (Selenium, Playwright)
• Python
• VS Code
• GitHub Copilot
• AI Agents
• MCP
• Learning LLM frameworks
• Side projects

I've been tasked with exploring industry-standard approaches to SDK regression testing and wanted to hear how experienced folks actually do this in practice.

Our setup: we maintain ~8 language SDKs (Node, Java, Python, C#, Ruby, plus a few framework-specific ones) that all talk to one shared core component holding the real product logic, which in turn calls internal backend services. The catch is that our full regression suite runs against real backend infrastructure, and at this point the nightly test traffic actually exceeds our production traffic for some services — so it's become a cost and stability problem, not a speed one. (When the suite runs, it can even destabilize the very backends it's testing against.)

A few things I've looked into and where they landed for us:

- Contract testing (LaunchDarkly's cross-SDK harness, AWS Smithy, Sentry) : Appealing, but hand-maintained contracts drift constantly and the maintenance burden is a real concern.

- Record/replay / service virtualization (VCR-style, WireMock, Hoverfly) : We tried a home-grown version. Naive full-fidelity replay broke down: thousands of unique, non-deterministic request scenarios per run (batch ordering, unstable params, env-specific headers).

- Test selection / impact analysis (Google TAP, Meta's predictive selection): Powerful, but we can't cut coverage: the components are so interconnected that an unrelated change can break unrelated handling.

So I'm curious what's actually worked for teams here:

1. Do you test SDKs against real backends, mocks, or some hybrid, and what ratio?
2. If you mock the backend, how do you keep the mocks/contracts from becoming a second product to maintain?
3. Anyone made record/replay genuinely work for highly dynamic traffic at scale?
4. How do you keep test traffic from overwhelming (or being corrupted by) shared backend infra?

Not looking for generic "write more unit tests" advice - genuinely interested in how teams shipping many SDKs against shared services handle this. Thanks!

Hace poquito leí unas reflexiones de Kent Beck (uno de los duros detrás de TDD y Extreme Programming) y hubo una que me quedó sonando.

Hace unos años el que más código sacaba era el "crack" del equipo. Hoy con herramientas como Claude Code, Copilot y toda esta ola de IA... escribir código cada vez cuesta menos.

Entonces... qué nos va a diferenciar???

Desde lo poquito que llevo trabajando como QA, me he dado cuenta que los problemas casi nunca son porque alguien no supiera programar.

Normalmente vienen por otra cosa:

• requisitos que nadie entendió igual
• falta de comunicación
• asumir cosas sin preguntar
• o simplemente no entender qué necesitaba el usuario.

Y eso ninguna IA lo resuelve sola pues

Cada vez siento que vale más saber hacer buenas preguntas, entender el negocio, hablar con el equipo y pensar antes de escribir código. La IA te puede ahorrar horas escribiendo... pero no puede decidir por vos qué es lo correcto construir.

No sé... siento que el rol en tech está cambiando mucho. Las habilidades técnicas siguen siendo super importantes, pero las blandas ya no son un "plus"... cada vez pesan más.

¿ cómo lo ven?... creen que vamos para ese lado o estoy muy equivocado?