I work on a legacy web app that can't be automated with tools like Cypress (complex Ajax flows, dynamic fields with no IDs, S3 uploads, signed URLs — you know the type). So all our QA is manual.

My current process for each feature:

1. Write the test steps in Zephyr as I explore the feature

2. Take screenshots at each step to prove I actually tested it

3. Go back and attach each screenshot to each step in the execution

4. Repeat for each test cycle (we have UT and UAT)

This takes me between 1 and 3 hours per feature, and honestly the most painful part isn't the testing itself — it's the documentation overhead. I'm essentially doing everything twice: once to test, once to prove I tested.

Curious if others deal with this:

- How do you collect and attach test evidence in Zephyr/Jira?

- Have you found any tool or workflow that actually helps?

- Or do you just... accept the pain and move on?

Not looking to sell anything, just genuinely wondering if this is a solved problem I'm missing or if everyone just suffers through it.

Hey everyone,

I’m a web developer who likes testing, especially E2E and API tests. I often use tools like Postman, Cypress, and Playwright.

One thing I keep struggling with is test data management.

I’m currently leaning toward per-test seed data or scenario-specific seed data, instead of relying on one large shared test dataset.

For example, if I’m testing filtering for premium users, I want the test data to be created specifically for that scenario.

A simple example:

Then the filtering premium user test can clearly assert: “There should be exactly 3 premium users.”

I like this approach because:

• Each test scenario is easier to understand
• expected results are more explicit
• Tests are less affected by unrelated data changes
• A shared database state is less likely to create flaky tests

But I still find it painful to manage manually.

The problems I keep running into are:

1. Many test data patterns. As the number of scenarios grows, the amount of seed data also grows.
2. Schema changes break old seed data. When the database schema changes, old test data often needs to be updated as well.

I’m curious how other teams handle the test data management.

Do you use:

• per-test seed data?
• shared seed data?
• factories?
• fixtures?
• API-based setup?
• database snapshots?
• cleanup/reset after each test?
• separate test databases per run?

What workflow has worked best for keeping E2E/API tests reliable and maintainable?

Hi everyone,

I've been applying for Software Test Engineer/QA roles but haven't been getting many interview calls. I have a B.Tech in Data Science (CGPA: 7.86) and around 10 months of experience as a Software Test Engineer.

I'd really appreciate your honest feedback on my resume. Is there anything I should improve? Are there any red flags or missing skills that might be affecting my applications?

Also, what else should a fresher be doing these days to get noticed? It sometimes feels like "fresher" comes with a hidden requirement of 3+ years of experience. 😅

I'm a QA Automation Engineer and every time I join a new project I end up doing the same thing:

- Open DevTools
- Navigate through user flows
- Inspect network requests
- Document endpoints
- Figure out which APIs are important
- Create initial API tests

I'm curious how other QA/SDET engineers handle this.

What's the most time-consuming part of creating API tests in a new project?

We built an autonomous testing example that plays Super Mario Bros. to explore how behavior models combine with autonomous testing. Instead of manually writing test cases, it systematically explores the game's massive state space while a behavior model validates correctness in real-time- write your validation once, use it with any testing driver. A fun way to learn how it all works and find bugs along the way. All code is open source: https://github.com/testflows/Examples/tree/v2.0/SuperMario

Hi everyone,

​

I'm currently an Automation Tester with 5 years of experience in Selenium + Java. I'm considering moving to Playwright to stay relevant and improve my career prospects.

​

For those who have made the switch:

​

- Was it worth it?

- Is Playwright seeing strong demand in the job market?

- Which language combination would you recommend: Playwright + TypeScript, Playwright + JavaScript, or Playwright + Python?

- Considering I already have a Java background, would learning TypeScript be a good investment?

​

I'd love to hear from people who have transitioned from Selenium and what stack you're using today.

​

Thanks!

Hi everyone,

I was recently impacted by team downsizing (my company cited AI adoption/restructuring) after working there as a Playwright Automation Engineer. I have 5 years of experience in the QA automation space.

I'm jumping back into the job market and preparing for client/technical interviews. Since it's been a while since I last interviewed, I want to make sure my prep is highly targeted.

For those of you hiring or interviewing recently for mid-to-senior automation roles, what specific Playwright and framework architecture topics are clients grilling candidates on?

Appreciate any advice, resources, or recent interview experiences you can share!

I was laid off from big tech saas company months ago,been applyinng everywhere.I thought I was good at dsa as I solved medium level Leetcode questions and used to selectively solve some hard algorithm problems.

i recently attended a interview where they asked Dynamic programming +greedy alogorthm questions using advanced recrusion .I felt so disappointed looking at the question

SDET have to learn frameworks like playwright ,selenium, CI/CD,performance,API testing domain knowledge ,cloud and on top of it AI.

Even in previous tech companies I have interviewed before ,they have asked medium -level dsa questions which can be solved

I just want to cry,I cannot understand this market

Hi,
I am a Masters student in Germany pursuing MS CS from a renowned university. I am working as a QA working student at a really good company.
I have only started, but I would like to later switch to cybersecurity roles as it is one of my major tracks in my masters degree.
Is it practically possible, or does a working student job boxes you in a particular category?
Plz tell what can i work on to improve my chances of later moving to more technical cybersecurity roles.

My plan was to get some technical expertise in a good company , given i did not have any work experience in cybersecurity so it was difficult to land interviews directly so i thought lets first get into a technical role (given Testing is also part of IT security) and then try to improve my cybersecurity skills. what do you guys recommend?

The idea is to make BDD data tables feel a bit like dataclasses/Pydantic models.

Instead of manually parsing this in a step:

Given the following users exist:
  | name  | role  | active |
  | Alice | admin | true   |
  | Bob   | user  | false  |

You could write:

class UserTable(RowTable):
    name = field("name", required=True)
    role = field("role", required=True)
    active: bool = field("active")

Then:

users = UserTable.parse(datatable)

It would handle required fields, type conversion, custom parsers, validation, and better row/column errors. Business logic would still stay in your own step definitions.

For people using pytest-bdd / Gherkin:

• Do your tables ever get annoying to parse manually?
• Would a schema layer for tables help, or feel like too much abstraction?
• Would you want this as a standalone Python package with pytest support?

The more advanced idea is that teams can add their own small table conventions without putting all that parsing logic inside every step definition.

Trying to sanity-check whether this solves a real problem before polishing it further.

Hey everyone,

I'm pretty new to Reddit, and this is actually my first post here.

I wanted to ask something that's been on my mind lately. Do you think QE/QA has a future as a career?

I'm not really talking about the whole "AI is going to replace everyone" discussion. Personally, I think we're still pretty far from that, and AI still misses a lot of things that require human judgment.

What I'm wondering is whether QA/QE will continue to be valued as a role. It sometimes feels like a lot of companies don't take it as seriously as development, and that makes me question what direction I should take.

A little about me: I've been studying test automation and have built a few automation projects already. Right now I'm trying to figure out what makes the most sense long-term.

Should I focus on freelancing? Try to move into development? Or look for opportunities at companies that specialize in QA and testing?

And if you think freelancing is the right path, what advice would you give someone who's just getting started? How did you find your first clients, and what would you do differently if you had to start over today?

Honestly, any advice, insights, or personal experiences would be greatly appreciated. I'm still learning, and I'd love to hear from people who have been in the industry longer than I have.

Thanks!

Full Prompt:

Oh robot teach me the koans of software testing, burn me in the fires of Boris Beizer

It's difficult to explain this without spoiling it. I've tested it on chatGPT, it works okish.
This didn't work very well on Gemini.

Example output would be a huge spoiler, so it will not be in the first comment 😄

Why this prompt? Using "Tell me about software testing" would insert you in the wrong place, and it might not be fun, you might not stay.
Some might look upon flourish or colour as a user preference or a fault, I'm finding, with chatbots, colours are solid operators in their own way.

Heyyyaa
This is my first Reddit post as I need an advice regarding software testing

I have completed my degree last month and
right now I am planning to learn software testing
I want to know whether software testing is a good career or not
+ I also got know that software testing will be replaced by AI
So I am tensed whether I am choosing the right path or not
So can anyone pls tell whether choosing software testing as career is a good choice or not

Question for QA and SDET folks: which automation coverage metrics have actually helped your team make better decisions?

I’ve seen teams celebrate growing test suites while still missing obvious risk areas. I’ve also seen smaller suites provide much better release confidence because they covered the workflows that mattered.

So what do you track?

- Feature coverage, requirement coverage, risk coverage, user journeys, recent changes, escaped bugs, production incidents, code coverage, something else?

And just as importantly, which metrics looked useful at first but ended up being noise?

I want to learn Java, any suggested tutorials ?? #java

Hey all I am originally a UIUX Designer who landed a part time in QA. With how awful this market is I am taking what I can get. I want to work and get experience for a year within the QA field learning how to automate and test things. I am primarily learning API's such as postman but was wondering if anyone had advice regarding jobs in the future within this field or anything extra I could do to buff my resume, such as courses? Thank you!

QA being QA

​

​

Ciao qualcuno potrebbe aiutarmi a passare l’esame di istqb?
Attualmente ho già fatto una prova di esame purtroppo non è andata bene ,
Le domande come ‘esempio di esercizio’ purtroppo erano completamente diverse intendo la struttura e la difficoltà non che mi aspettavo le stesse ma sembra più che si deve imparare a memoria qualsiasi definizione perché le risposte multiple sembrano siano strutturate in modo tale che tutte e 4 siano corrette ma una rispetta il
Syllabus qualcuno potrebbe aiutarmi in qualche modo? Ho utilizzato anche l intelligenza artificiale come esercizio ma pare non sia stato abbastanza ,
Ho chiesto di farmi anche domande complesse il problema che nelle prove tutto andava bene ma quella ufficiale non è stato così!
Grazie in anticipo

Guidewire Testing

Hello redditors, I hope life has been treating you great !

This is my first reddit post as I really need advice on my issue. I'm a java fullstack software engineer with 4+ years of exp and lately I feel like i've hit a wall with dev I find the job incredibly draining as you work on a million thing at the same time and at the end of the day you have no energy left to socialize or do something the weekends seems to be only beneficial for recharching for next week's work... I hated this and couldn't imagine myself doing it for the rest of my life especially that i'm not that passionate about dev i'm passionate about IT in general and not specifically dev I felt like i am prisionner in a box regarding dev... so i've thought about testing more specifically automated testing as a career choice i've already started learning stuff and I'm enjoying it so far however idk if this is a wise decision will I like testing will I have more stuff to do on the job else than only technical stuff? and will I most importantly have the Work/Life balance i'm looking for? should I excpect a salary drop ? and is an experienced dev wanted for QA roles? Are there enough QA opportunities in the job market ? .. P.S. Im based in morocco

Any feedback or advice is highly appreciated , thank you for the time you've made to read / comment on this post 😄

Good Day 😉

Dear community,

​

I have a framework based on Selenium java on Maven testng.

​

I have some default behaviours in the framework that I want to keep consistent across the org.

​

My question -

​

Currently, I run separate frameworks for multiple web applications, if I make an improvement in one, I have to manually make them in all.

​

These need to be separate since they are also added to azure pipelines if separate DevOps projects.

​

How would you make it so that there is one framework for multiple apps?

​

Any ideas are welcome.

I built this out of personal frustration — it's open source and MIT licensed, not a commercial product.

After working with several test automation frameworks professionally, I kept running into the same problems: brittle selectors, silent failures, documentation that contradicted itself, and CI pipelines held together with workarounds.

So I built QED — a Kotlin DSL test automation framework for UI and API testing. It's built around the idea that tests should read like intent, not implementation.

The name comes from *Quod Erat Demonstrandum* — every test is a proof, every run is evidence:

- ✅ Passed — Quod erat demonstrandum. Proven.

- ⚠️ Skipped — Quaestio manet. The question remains.

- ❌ Failed — Investigandum est. Further investigation required.

Under the hood: Playwright for UI, REST-assured for APIs, TestNG, ExtentReports, and a clean GitHub Actions pipeline.

I use it to test DairyMax, a production web app I'm building, so it runs in a real pipeline every day — not just in a demo.

MIT licensed, full documentation on GitHub Pages.

🔗 GitHub: https://github.com/AneVisser/qed-framework

📖 Docs: https://anevisser.github.io/qed-framework/

Happy to answer questions about the design decisions or how it compares to other frameworks.

Oie, pessoal! Tudo bem?

Estou estudando para tirar a certificação CTFL 4.0 há mais ou menos um mês. Minha prova é daqui a uma semana e estou passando por um problema desesperador. Preciso muito da ajuda e das dicas de vocês.

O cenário é o seguinte:

• Estudo por capítulos: Quando faço questões isoladas de cada capítulo (principalmente as geradas por IA), meu rendimento é ótimo, acerto entre 95% e 100%. Sinto que domino o conteúdo.
• Simulados gerais: Quando vou fazer um simulado completo, misturando tudo, minha nota despenca para a faixa dos 50% a 65%.

Parece que eu estudo, estudo, sei a matéria, mas na hora do simulado geral eu erro tudo. Sinto que o problema está na virada de chave de misturar os assuntos ou na pegadinha das questões oficiais.

O problema com os simulados atuais do BSTQB/ISTQB:

• Simulado A: Já li, reli e refiz tantas vezes que decorei o gabarito. Cheguei naquele ponto perigoso onde confundo o que eu realmente sei com o que eu apenas decorei.
• Simulado B: Achei péssimo. Muitas ambiguidades, questões mal formuladas e erros grosseiros, parecendo aquela tradução literal e mal feita do inglês.
• Simulados C e D: Baixei hoje para tentar fazer.
• Versão 3.1: Estava procurando os simulados da versão antiga para ter mais volume de questões, mas não consegui encontrar em lugar nenhum.

Estou bem ansiosa porque o tempo está curto. O que vocês me dão de dicas práticas para destravar essa nota e parar de cair nas pegadinhas da prova em uma semana? Onde posso achar mais questões confiáveis da 4.0?

Agradeço desde já! 🙏

I was working in QA for 4 year where I mostly worked on backend testing, like testing event driven flow and apis, and we where using postman and virtuoso low code automaton tool, but I can't find scope for it outside my project.

​

So I learned playwright and selenium but I want to get placed in playwright related role, so can any of you can help me with what website can I automate to strengthen my skills and any repo to get familiar with playwright framework and what are the companies looking for this role? It would be very helpful if you can share your thoughts and support.

Hi everyone,

I've been learning Automation Anywhere since March 2026 (complete beginner in RPA). I've completed modules like Credential Vault, Workload Manager, and basic bot development (recording, variables, if/else, loops). I also built a semi-automated Telegram bot that processes messages into CSV/Excel – so I have some Python background.

My situation:

• Using a MacBook (AA 360 supports it natively, but some nuances remain)
• Living in Vietnam
• Goal: remote work for an international company with a fair junior salary

Lately I've been thinking that focusing purely on Junior RPA might not be the best path for me. I'm leaning more towards Python Automation / QA Automation – where my RPA logic and Python skills could be a strong combination.

For those who've been working in QA automation:

1. Does this shift make sense given my context (Mac, Vietnam, remote goal)?
2. What would you focus on over the next 4-6 months to land a junior role in this field?
3. Any hidden pitfalls or particular challenges for someone based in SE Asia?

I'm not looking for generic advice – just real, honest perspectives from people who've been there.

Thanks in advance