Hi everyone!
I’ve been working in QA for about 5 months. So far, I have experience with Manual Testing and API Testing using Postman, but I have zero experience in Automation.

I’d like to start learning Test Automation, and I’m currently considering Playwright.

What would you recommend for someone starting from zero in Automation? I don’t mind if the resource is free or paid — my main priority is finding something that gives me a strong foundation and teaches things properly, rather than just following tutorials without understanding.

Also, what do you think about the freeCodeCamp course “Software Testing Course – Playwright, E2E, and AI Agents”? Is it good for a complete beginner in Automation, or would you recommend starting with something else?

I’d also really appreciate hearing about your own experience:
How did you start learning Automation?
What was the best resource/course you used?
Is there anything you wish you had learned earlier?

Thanks in advance!

Any ideas or Suggestions on AI certifications for a software tester? ISTQB has gen AI certification. Any other recognized certifications? Let's share...

8+ years in QA (product → Shopify agency → back to product), now at an AI startup. Curious if my current workflow is normal or if I got lucky with tooling.

The old way, for years:

1. Receive reqs
2. Write test plan/test cases
3. Manually test
4. Log bugs

Depending on the feature, this could eat hours, days, sometimes weeks.

How I work now:

1. Drop the feature into Claude
2. Have it generate the test cases/test plan
3. Have it actually run the tests on the PR or staging
4. I manually cover whatever it couldn't (rare)
5. Claude leaves feedback/pass notes and updates my test run

A feature that used to take days can now get through in a few hours, even when it's pretty complex.

So — is this just a quirk of working at an AI-native company, or is this becoming the norm in QA now? Would love to hear how manual QA folks elsewhere are (or aren't) using AI in their day-to-day.

Writing test cases manually takes a lot of time, especially when we are working on different features. Is there any simple AI tool that can create test cases from requirements or screenshots, manage testing progress and also help track bugs in one place?

It would be better if the tool supports both manual and automated testing. Please suggest a good option.

Bit of context. I spent 3.5 years testing billing and tax platforms, one for a US utility and one for a tax form validation tool in Poland. Functional, mobile, API, some automation. Finished a Master of IT in Australia this year and I'm now job hunting in Melbourne.

The job ads are telling me almost nothing useful. Half of them want a "Quality Engineer" who is really a developer, half want a test analyst with eight years in one specific domain, and the rest read like they were written by someone who has never met a tester.

4 things I'd like a reality check on from people actually working here:

1. Is a dedicated QA role still a real thing, or are teams increasingly pushing testing onto developers alongside their own work? I keep hearing both and I can't tell which one is the market and which one is LinkedIn noise.
2. Does 3.5 years read as mid-level to hiring teams here, or does overseas experience get discounted enough that I'm effectively starting again? Someone in the industry told me directly not to bother with grad roles, but I'd like to know if that's the general view.
3. When a team does interview for a pure QA role now, what is it actually testing? Live coding, framework design questions, or more scenario based?
4. Also curious about the AI thing. I've been told the differentiator right now is being able to show where you've used AI to solve real testing problems, not just "familiar with AI tools". If that's true, what does that actually look like in your work? Genuinely asking, because I'd rather build the skill properly than bolt a buzzword onto my resume.

Happy to hear anything, including that I'm asking the wrong questions.

Is it really possible to land at least a 5lpa job as a fresher in the software testing field in accordance with the current market situation and the impact of artificial intelligence making it difficult to catch up to the expectations of recruiters

I’m currently looking for Manual QA / Software Testing opportunities. I have 3.7 years of experience in software testing and am based in Bengaluru. I’m an immediate joiner and open to relevant opportunities in Bengaluru or remote roles.

If anyone knows of openings, referrals, hiring managers, or companies currently hiring Manual QA/Test Engineers, I would really appreciate your help. Any leads or suggestions are welcome.

Hello community, is there anyone using AI for software backend testing. If yes then please explain the how's and when and tools to be used and type of project or features applicable for this AI.

For front-end or UI based application, AI has huge potential but for backend i haven't seen any tutorials guides or posts in the internet or people from my network.

If someone has good idea on this please let me know.

James Bach writes about who is responsible for software quality. Excerpt: "In opposition to my idea that software testing should be a role, and not just a task, I am sometimes told that True Agile does not permit this. Why? Because, in Agile, “quality is everyone’s responsibility.” This statement is sometimes issued as if it were a moral truism that is beyond argument. Or sometimes as a moral achievement that is unique to Agilists, as if it had never occurred to earlier generations of software developers to help each other build nice things. Either way, it doesn’t make sense to me. The first response that comes to my mind is “I’m talking about testing, not quality. Why are you dragging quality into this?” Testers do not assure quality. Testers CANNOT assure quality. Testers do not now and never have “owned quality” in any way."

But even if we set that aside, quality should not be considered “everyone’s responsibility.”

I’m recruiting for a senior QA/Test Manager to lead quality assurance for a large-scale EHR SaaS implementation.

Contract details:

• September 3, 2026–August 31, 2027
• Up to 2,000 hours
• Austin, Texas
• Onsite Monday–Friday
• Candidates must already reside in Texas and be able to work onsite
• Client name is confidential at this stage

Key requirements:

• 11+ years in QA/Test Lead or Test Manager roles
• Strong EHR or healthcare SaaS testing experience
• Data migration, ETL testing, reconciliation and data validation
• Functional, integration, regression and user acceptance testing
• Experience testing clinical, scheduling, medication, documentation and billing workflows
• Test plans, traceability matrices, defect management and test evidence
• Azure DevOps, ALM or Jira
• Experience coordinating vendors and multidisciplinary teams

Experience with HL7, FHIR, HIPAA or public-sector healthcare systems would be especially helpful.

If you’re interested, send me a message with your résumé or LinkedIn profile and a brief overview of your EHR and data-migration testing experience.

Joanna@MaridenSearch.com

Company: Comply Ark

Mode: Remote

Duration: 3 Months

Stipend: 5k-7k/month

Please upvote and comment interested to get the apply link

Just read about a man from Australia using an OpenClaw AI Agent to book a gym reservation and the end result was a booking, but, at the expense of another gym member losing their reservation!

Most of the comments that I have read online have been towards the thinking of 'Bad AI'. I think that this is a result of a software defect in the gym club's membership booking program, no matter if a bot did it, if the person themselves found the flaw, or the front desk clerk.

My recommendation is to understand how (if) your organization is doing any testing with AI Agents, and if not, suggest that they start (note, this does not mean testing the AI artifacts that your company is developing, but, using AI to test your core products). As evident by the leaps forward AI is making, we as Quality Assurance Professionals can and should find ways to harness this and gain some productivity.

QA Engineer – Manual & Automation Testing

Experience: 1–2 Years
Location: Bangalore / Remote
Employment: Full-time/Freelancer

We are looking for a QA Engineer with 1–2 years of experience to join our engineering team and work on a modern e-commerce platform and mobile application.

The role will involve owning quality across web applications, APIs, and mobile experiences, with a strong focus on functional testing, automation, and real-world user experience.

What You'll Do

• Perform manual and functional testing of web applications and APIs.
• Design and execute test cases, test scenarios, regression and smoke test suites.
• Identify, document, track, and verify bugs through their lifecycle.
• Perform API testing and validate backend services and integrations.
• Build and maintain automation test cases for critical application workflows.
• Conduct regression testing for new releases and feature updates.
• Work closely with developers, designers, and product teams to identify issues early.
• Validate application performance, usability, responsiveness, and cross-browser compatibility.
• Participate in release testing and provide QA sign-off.
• Help improve QA processes, test coverage, and automation practices.

Requirements

• 1–2 years of experience in software QA/testing.
• Strong understanding of manual testing methodologies.
• Hands-on experience with automation testing.
• Good understanding of API testing and tools such as Postman.
• Experience writing clear and structured test cases.
• Good understanding of SDLC, STLC, bug lifecycle, regression testing, and test planning.
• Basic understanding of databases and SQL.
• Familiarity with Git and modern software development workflows.
• Strong attention to detail and a mindset for finding edge cases.

Good to Have

• Experience testing React Native / Android / iOS mobile applications.
• Experience with tools such as Appium, Playwright, Cypress, or Selenium.
• Experience with e-commerce applications, Shopify, payments, orders, inventory, or customer-facing applications.
• Familiarity with CI/CD-based automated testing.
• Basic understanding of performance and security testing.

What We're Looking For

Someone who doesn't just verify whether a feature works, but asks:

"What could go wrong?"

You should be comfortable exploring edge cases, breaking workflows, reproducing difficult bugs, and thinking from the perspective of a real customer.

You'll work closely with the engineering team on a product where quality, reliability, and mobile app performance are key priorities.

Apply if you're excited about building and testing products used by real customers and want exposure to modern web, API, mobile, and automation testing.

​

I'm a 10-month-experience QA working as the only QA in a fintech startup, currently responsible for 3 loan apps and 2 aggregator platforms.

I know I'm not an excellent tester yet. I struggle with structure, memory, domain knowledge and sometimes thinking of edge cases. I'm working on those things.

But I'm struggling with the environment too. Testing is often expected to be completed in 2–4 hours, while I'm also expected to maintain the QA process, report bugs, track fixes, and ensure coverage. Requirements aren't always clear, but when I ask questions, I'm sometimes told to figure it out from competitor products. At the same time, I'm discouraged from spending too much time with developers because apparently I'm “wasting their time.”

I've been told QA is basically on its own. I was also told by someone from product that “you have to decide how many balls you can dodge.” That really made me realize that I'm not sure I want to work this way long-term.

I understand that 100% bug-free software is impossible and edge cases will always exist. I'm not expecting perfection. What I want is clear expectations, reasonable time to test, and enough collaboration to understand the product and make good decisions.

I'm not trying to blame everything on management — I genuinely have a lot to improve as a tester. But after weeks of feeling constantly scrutinized and struggling to keep up, my confidence is getting drained and I'm seriously considering an alternate career path.

For experienced QAs: is this normal startup/QA reality, or am I in an unhealthy setup? And if you've been in a similar situation, did changing companies change your experience of QA?

Hi everyone,
I'm looking for ideas and experiences around creating realistic test data for a new Case Story feature.
Case Story provides a chronological view of everything that has happened on a case and across its related case hierarchy. Rather than users navigating to multiple areas of the application, it brings together events such as documents, tasks, contacts, emails, notes, comments, status changes, and other key activities into a single timeline to help users quickly understand the history and progression of a case.
The challenge isn't just generating large volumes of data. We need data that reflects how cases evolve over time, including realistic sequences of events, updates, and changes, so the timeline feels representative of real customer usage.
A few questions:
Have you used APIs, automation, SQL scripts, or other approaches to generate large volumes of realistic test data?
How have you simulated historical data and record changes over time rather than just creating static datasets?
Are there any tools, frameworks, or utilities you'd recommend for creating varied, timeline-based test data?
For performance testing, have you found volume, variety, or historical depth to be the biggest factor?
Our current focus is on creating realistic case hierarchies with a good mix of documents, tasks, contacts, emails, notes, status changes, and other events occurring over weeks, months, or years. We suspect that the quality, variety, and history of the data may be more important than pure volume alone.
Would love to hear how others have approached similar challenges and any lessons learned. Thanks in advance!