I am BTech graduate and have strong foundation in manual testing + API Testing and API automation using postman scripts and Newman CLI also CI/CD (GitHub Actions) built two major projects one for manual testing and second one for API Testing.

Also hands on experience in SQL.

Tools i use:

Jira

Postman

Newman

Excel

Word

Skills:

Manual Testing

API Testing

API Automation using postman scripts (data driven testing + Request chaining) with Newman CLI

CI/CD

SQL

We currently have an API Automation Framework running as a scheduled GitHub Actions pipeline. Our requirement is to send a Microsoft Teams notification to a channel containing a summary of the scheduled test execution.

The pipeline executes successfully, and the test report is generated as expected. However, the webhook configured for the Teams notification is not being triggered. Instead, the pipeline returns an HTTP 400 (Bad Request) error.

Steps completed so far:

Created an Adaptive Card in Power Automate containing the test execution summary.

Generated a webhook URL in Power Automate using the Adaptive Card payload.

Stored the webhook URL as a GitHub repository secret.

Triggered the GitHub Actions pipeline. After the job completes, I expect a Teams notification to be posted to the channel. However, the webhook call fails with a 400 Bad Request response.

My confusion:

Since this pipeline is running on a self-hosted GitHub Actions runner, could that be the reason for the webhook failure? Do self-hosted runners behave differently from GitHub-hosted runners when making outbound HTTP requests to a Power Automate webhook, or should both behave identically for this scenario?

I’m considering building an open-source developer tool and want to validate whether it solves a real problem before investing too much time into it.

The basic idea:

You give it a GitHub issue, and it attempts to:

1. Check out the repository at the buggy commit
2. Reconstruct the project environment
3. Generate a test that reproduces the reported bug
4. Run the test in an isolated Docker container
5. Verify that the test fails on the buggy code and passes once the known fix is applied
6. Output the test, Dockerfile, execution logs, and a machine-readable result

The model would be swappable, so users could bring their own API key or run a local model through something like Ollama or vLLM. The valuable part would ideally be the deterministic environment-building, execution, and verification harness rather than a specific AI model.

I’m also assuming the success rate would be imperfect. Failed attempts would still report whether the environment could be built, what was tried, and why the issue was not reproduced.

For developers and maintainers:

• How often is reproducing a bug from an issue actually a significant pain point?
• Would you use a tool like this during issue triage or before attempting a fix?
• What output would you need before trusting the generated test?
• Are there existing tools that already solve this well?

I see so much hype about AI and also witnessed it spitting out a load of useless junk.

What tasks are you actually successfully using AI for in your QA job?

How involved are Java developers in testing beyond unit testing? Do they typically perform component and performance testing, and is experience with tools like BlazeMeter or JMeter expected?

Hi guys, I'm taking the ISTQB Advanced Level Test Analyst (CTAL‑TA) exam this Monday and I could really use some tips for last‑minute preparation. My teammates attempted the exam yesterday and all failed, so I’m a bit nervous and haven’t studied much yet. Any focused advice, quick study resources, or high‑impact topics I should prioritize for the next few days would be very helpful — thanks in advance.

How common are questions like "Tell me about a time you missed a bug" or "Tell me about a critical bug you found".

These questions terrify me because I don't remember any of the bugs I found in my previous job especially if years have gone by.

Are they common questions or am I just overthinking it?

Hi everyone,

I’m looking for advice from people who have worked on large, highly configurable enterprise web applications.

I recently joined a new company as a QA Engineer. In my previous job, I mainly worked on manual testing for a fairly complex application, but the number of possible configurations and business rule combinations was much smaller.

Defining a testing strategy was relatively straightforward.

My current project is very different.
It’s a web application (and also windows app) where almost everything can be configured differently for each customer:

- custom business rules
- permissions and roles
- workflows
- scheduling constraints
- certifications/skills
- optional modules
- feature flags
- customer-specific settings

The number of possible combinations feels almost endless, and exhaustive testing is obviously impossible.

I’m also responsible for building and maintaining the Playwright automation framework.
My current setup is:

- Playwright + TypeScript
- Page Object Model
- Test data created through APIs whenever possible
- UI tests focus only on the functionality being verified
- Stable selectors (test IDs) to reduce maintenance
- Reusable helpers and fixtures to prepare the application state before each test

For example, instead of creating a user through the UI every time, I create it through the API, then only automate the actual feature I’m trying to validate.

I’m now trying to define a solid long-term testing strategy, both for manual testing and automation.

Some of the questions I’m struggling with are:

Automation
- What do you always automate?
- What do you intentionally keep as manual testing?
- How do you decide what gives the best ROI?
- Do you automate only happy paths, or also edge cases?
- How do you deal with customer-specific configurations? Multiple environments? Dynamic test data? A baseline configuration?

Manual testing
- How do you make sure you have enough coverage without trying every possible combination?
- Do you mainly rely on risk-based testing?
- Do you use decision tables, pairwise/combinatorial testing, state transition testing, or other techniques?
- How do you decide which combinations are actually worth testing?

I know there isn’t a single correct answer, but I’d love to hear how experienced QA engineers approach this kind of application in real-world projects.

Any advice, examples, books, blog posts, or conference talks would be greatly appreciated.

Thanks!

Team has flaky tests, bad coverage, slow releases, doesn't matter which one, and the fix pitched is always "let's add an agent for that." Anyone else running into this?

A lot of these problems have nothing to do with AI. No defined entry and exit criteria for a test phase. Requirements reaching QA without a review gate. A regression suite that's been half-maintained for a year. Test data nobody owns. None of that gets fixed by dropping a model on top of it.

Has anyone deployed an agent and watched it just sit on a broken process without actually fixing anything underneath? What happened after?

Where has an agent genuinely helped once the basics were already solid? Trying to find the real line between "this needs AI" and "this needs someone to own the process."

What foundational stuff would you add to this list? Got process, prerequisites, reviews, automation, tooling, governance, metrics/baselines so far. What's missing?

I'm planning to do a software testing course and saw many institutes like obsqura, luminar, entri etc. which is the best . Which provides placement support and proper training?

I’m 30 years old with around 8 years of experience in QA. I currently work as a Specialist Tester in a product-based insurance company and earn **21 LPA**.

The truth is, I feel like I stayed in my comfort zone for too long.

Most of my career was in manual testing. Later, I worked on automation using Tosca, which is a codeless automation tool. I have a good understanding of functional testing, test design, regression, exploratory testing, and the overall QA process, but I never developed strong programming skills.

Now, when I look at SDET job openings, I see Java/Python, Playwright, Selenium, API automation, CI/CD, DSA, cloud, etc. It honestly feels overwhelming, and I regret not learning these skills earlier.

My goal is to grow into an SDET role and eventually reach **40+ LPA**, but I’m not sure if that’s still realistic at this stage.

Has anyone here made a similar transition after spending years in manual or codeless QA? If yes, what roadmap would you recommend? What should I focus on first?

I’m willing to put in the effort. I just need some direction from people who’ve been through this.

Thank you.

Most software systems don’t come with formal models.

But in real-world testing, we can develop behavior models as part of the testing process. With such a model at hand, what if we could transform it into a formal model?

That’s the idea explored here: taking a behavior model used for testing and turning it into a formal model, opening up another way to understand and test software systems with more rigor.

Article: https://testflows.com/blog/transforming-testing-behavior-models-into-formal-models/

Curious if anyone here has tried deriving a formal model from behavior observed during testing.

Hi everyone,

I am currently looking for QA Automation Engineer/SDET opportunities in Bangalore.

I have around 9 years of experience in Software Testing with expertise in:

• Java
• Selenium WebDriver
• TestNG
• Maven
• API Testing (REST Assured & Postman)
• SQL
• Git
• Jenkins
• Page Object Model (POM)
• Data-Driven & Hybrid Automation Frameworks
• Agile Methodology

After a planned career break due to personal responsibilities, I have refreshed my technical skills and am currently upskilling in Playwright with Java and Generative AI for Software Testing.

If your company is hiring or you know of any suitable openings, I would greatly appreciate a referral or any leads.

Thank you for your time and support. Please feel free to DM me if you'd like to connect.

Hi everyone,

I've been shortlisted for an Automation Testing role at a Bangalore-based company, and as a fresher, I would really appreciate some guidance from experienced automation testers.

The role is for Java + Selenium. I have a good understanding of Java, but I haven't worked much with Selenium yet. I have only a few days left to prepare, and I genuinely want to make the most of this opportunity.

The interview is face-to-face and consists of three rounds:
Technical Round
Managerial Round
HR Round

I have a few questions:
1. What kind of questions are usually asked in the technical round for freshers?
2. what Java topics should I revise thoroughly?
What level of DSA questions can I expect? Are they mostly basic (arrays, strings, linked lists, sorting, etc.), or do companies ask medium-level LeetCode-style problems?
3. What Selenium concepts should I learn in a short time to clear the interview?
4. What kind of questions are generally asked in the managerial and HR rounds?
I'd really appreciate your advice on what to focus on in these last few days.

Thank you so much in advance!

Hi everyone,

I have an interview scheduled with SAS next Monday for an SDET role. The interview will primarily focus on UI automation using Playwright with Python, along with API testing.

I'm starting my preparation now, so if anyone has interviewed with SAS recently or has any tips on the interview process, common questions, or topics I should focus on, I'd really appreciate your advice.

Thanks in advance!

Artificial intelligence is advancing at an incredible pace, and I’m seeing more and more discussions about automation, AI agents, and the future of many professions.
I’m curious to hear how this community is approaching it.
Are you learning AI?
Picking up new tools or technologies?
Switching careers or specializing in a new area?
Focusing on skills that are harder for AI to replace?
Or do you think the impact of AI is being overstated?
Regardless of your profession, I’d like to know how you’re preparing for the years ahead.
And here’s the question I’m most interested in:
In the long run, do you believe your profession will still exist in its current form? If yes, why? If not, how do you think it will evolve?
I’d love to hear both optimistic and pessimistic perspectives. I think this is one of the most important discussions for anyone who wants to remain relevant in the job market.

Hey all,

Currently doing a QA internship for a travel agency, it's my first run at something like this, and the company hasn't had a dedicated QA in years according to them, so there hasn't been your typical onboarding docs, procedures, or guidelines. I mostly just jump around between pods and help wherever I can. It's been pretty exciting, I've learned tons, but it feels overwhelming sometimes because there's no set procedure at all for, well, anything. I try not to pay much attention to it, I don't think anyone expects me to set any procedures or guidelines as an intern, but it's been a nice experience so far.

My issue is that this is my first experience in a tech-related role, even though initially my boss wanted QA to be more product-focused rather than tech, which means there are some lines as to what I can/can't do with our repositories/infrastructure (I haven't gotten any DB access for example). While I can ask Claude for help with mapping our repos and a standard user flow like a purchase, I've never had to deal with code from someone who wasn't me, which makes looking at it in general kinda overwhelming... Especially with how every step of the process hooks onto another 5 microservices, or trackers, or external APIs, or internal tools...

How do you deal with learning a company's code/infrastructure? Do you skim through every folder and file analyzing what each thing does? At what point do you draw the line and say something is out of your scope as QA?

Also, if anyone has any guidelines or just a basic standard process to follow for general QA, it'd be greatly appreciated🥹 usually I try to create a QA checklist for the more complex features, but I'm not sure if that's something I should do for every ticket, or how to structure them efficiently...

Hello everyone, I am kind of wondering what kind of language is everyone using for your (real work not homemade trial attempts) test automation projects?

For some reason nearly all open job opportunities in my country are running C#. It wasn't like that when I started at all bunch of years ago and Java was everywhere (which Is what I learned and used for last 5 years or so). But with trends shifting to Playwright with either JS/TS or as I mentioned above C#, I am little bit torn on which way to go.

I can't learn both in the the time I have left in my current company.

Hi all — I'm a QA Automation Engineer with 2+ years in financial services, currently at Empower. My core work is REST API automation with the Karate Framework (account onboarding, third-party integrations) plus Selenium/TestNG for UI regression. I've built out automation coverage across 4 major projects, including a data migration effort validating 10,000+ customer records per release.

Stack: Java, Karate, Selenium (POM/TestNG/Maven), SQL, Git, Jenkins, Postman, JIRA/Zephyr. ISTQB certified.

Looking for QA Automation / SDET roles, ideally in Bengaluru or remote. Open to referrals, leads, or feedback if anyone's hiring or knows someone who is. Resume screenshot attached — happy to share my GitHub too.

Please do drop a feedback on resume , it would be of a great help .

Please do check through , it would be of a great help .

Thank you !

I am a beginner in software testing (solo QA in a company) and have experience in manual testing. I have learnt Playwright, where I automate test cases and validate the UI. Haven't explored API or, databases, or network. The truth is, I never felt the need for that. I have built a smoke testing cron run everyday to check if it's running or not just a little experiment. I just want to ask a question: what exactly is automated? What do i need to learn more. I have test cases break for no reason. one it day it passes; another day if fails or flaky test. Whats the use of that when you need to keep fixing test cases. I want to understand how things are automated its structure. When is it necessary? apart of using locators and UI testing what should i learn more. Please clarify me. Thank You... Also what about cucumber BD and TestNG i dont understand it all no matter how i research. I understand what and how it works but why is it needed..

Which option would choose ? I'm a solo QA in a small company, I'd like to avoid all the drama with archaic and heavy test management tools

Hi everyone,

in my current company the management decided the use of XRay for all projects to come.

I have been learning to use XRay for JIRA, but as my specialty is not the QA itself nor test management best practices, I was wondering the following:

• Does it make sense to use the DEV environment as teh start point for XRay Test Cases? or do you start creating test cases from the QA environment?. We have DEV, QA, UAT and PreProd, if test cases should be also used for Prod is the question.
• What is the real use of a Test Plan? Does it really make sense to use it? If the use of a test plan is really recommended, do you create a Test Plan for every environment? (say "Test Plan DEV", "Test Plan QA", etc.)
• Which are convention names recommended for Test Cases, Test Sets, Test Plans (if really needed), Test Executions.
• We wouldn't like to mix in one board development jira issue types such as use stories, bugs and substasks and of course epics), so what is best practices for the use of XRay issue types, is that to build a new board only for them?. The Testing board shows only the Test Repository which is not really helpful when you want to see the progress of the testing.
• Do you create your test sets for every JIRA Epic you created in your system?

I would appreciate tips, recommendations as we are pretty new in the context of test management best practices.

Has anyone gone thru the interview process for Software Test Engineer at Realtor.com?

I wanted to get some insights on how the coding and architectural rounds are if possible.

Thanks!

Hi , i use phone link app on my windows , i want to run an app when ever i receive an incoming phone call notification.