Activity
Mon
Wed
Fri
Sun
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
What is this?
Less
More

Owned by Matviy

AI & QA Accelerator

580 members • Free

Manual QA → QA Automation → AI-Powered SDET. Pick Your Path. Join AI & QA Accelerator.

Memberships

Data Alchemy

37.8k members • Free

AI Masters Community with Ed

12k members • Free

[Archived] KubeCraft (Free)

11.3k members • Free

The Aspinall Way

28.6k members • Free

Skoolers

189.9k members • Free

57 contributions to AI & QA Accelerator
AI Coding Agents for QA: Part 3 — IDE Tools
In Part 2 I covered CLI tools. They work. But for QA automation especially if you're just starting... they're simply the wrong tools. ──────────────────────────────────────── 𝐘𝐨𝐮 𝐒𝐞𝐞 𝐄𝐯𝐞𝐫𝐲𝐭𝐡𝐢𝐧𝐠 ➤ CLI gives you output on a screen. A wall of text. ➤ IDE tools show changes line by line, inside your actual files. Right in front of you. In Cursor specifically, you accept or reject each change individually. One line at a time. That matters for beginners. When something goes wrong, you see exactly what changed and where. You can ask the AI to explain the change while looking at it. Not a printout. The actual code that helps you to actually learn. ──────────────────────────────────────── 🔹 𝐖𝐡𝐚𝐭 𝐂𝐮𝐫𝐬𝐨𝐫 𝐀𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐈𝐬 Cursor is a fork of VS Code. Fork means: a copy of an existing code, taken in a new direction. VS Code is Microsoft's editor. Cursor took that foundation and rebuilt it for AI from the ground up. Compare that to Copilot. Copilot is a plugin bolted onto VS Code. It was added after the fact. Not designed to be there. That difference shows up in practice. Cursor was built with AI as the core. Copilot was added on top. ──────────────────────────────────────── ⚡ 𝐌𝐮𝐥𝐭𝐢𝐩𝐥𝐞 𝐌𝐨𝐝𝐞𝐥𝐬, 𝐎𝐧𝐞 𝐓𝐨𝐨𝐥 Cursor gives you access to models from both Anthropic and OpenAI in one place. Claude Sonnet. Claude Opus. GPT-4o. You pick per task. ⤷ Hard problem or complex refactor? Use Opus or GPT Codex ⤷ Quick fix or small helper? Use something cheaper. That lets you control spending and get the best output without switching tools and having 2 subscriptions. Pricing is also transparent. You know what you're paying. No surprises. ──────────────────────────────────────── 🌐 𝐓𝐡𝐞 𝐁𝐮𝐢𝐥𝐭-𝐈𝐧 𝐁𝐫𝐨𝐰𝐬𝐞𝐫 Cursor has a browser built directly into the IDE. 1. Open any page. 2. Click on elements: buttons, inputs, dropdowns, etc. 3. Ask Cursor to extract the best locators for your test automation. Hunting for locators manually is one of the most tedious parts of UI testing. This feature cuts that work significantly.
AI Coding Agents for QA: Part 3 — IDE Tools
2 likes • 6d
@Rey Mallari You’re 100% right. All of this is still new. Truly capable AI agents only started showing up at the end of 2025, so right now is a golden opportunity to get in early as the job market shifts. The people who understand this space will have a major career advantage and safety over the next decade.
Open to talk about your toughts on vibe coding and ai powered testing
Hi Everyone I am Rahul I have 12 years of experience in QA healthcare e-commerce domains and leading QA teams and now working solo freelancing from last 1 year with ai powered testing in playwright with mcp and agents with testings skills want to know how can these frameworks can be improved or optimised. Also tried vibe coding with different tech stacks to put my imagination to the reality in with saas products in Healthcare and e-commerce domain. Happy to chat on any topics or opportunities
3 likes • 12d
Hi Rahul, great to have you here. Here are the three things you should do to improve your AI agent’s performance quickly: 1. Make sure you set up your AGENTS.md file properly and keep it updated. If you discover a new issue with the AI, document it in AGENTS.md so the next run knows what not to do and how to handle it correctly. 2. Create a docs folder with files that describe your framework architecture, explain your project, outline constraints, and include other important context. Link these documents from AGENTS.md so the AI agent can discover them easily. 3. Whenever you work on tasks, always create a plan first. The more detailed the plan, the better the results will be. Make sure to include examples of similar tasks or tests in the plan as well. These are the easiest things to implement, but there is much more you can do.
AI Coding Agents for QA: Part 2 — Types of the AI Coding Agent
In Part 1 I promised to tell you which tools actually work. Let's start by ruling one category out. ──────────────────────────────────────── 🚫 𝐒𝐭𝐨𝐩 𝐔𝐬𝐢𝐧𝐠 𝐂𝐡𝐚𝐭 𝐀𝐩𝐩𝐬 𝐟𝐨𝐫 𝐂𝐨𝐝𝐢𝐧𝐠 ChatGPT, Claude.ai, Gemini — these are not coding tools. I know. You can paste code into them. You can ask questions. It feels like it should work. But here's the problem: these tools were trained to answer everything. Recipes. Health advice. Legal questions. Your Playwright test suite. Coding task. Those tools treat them all the same way. They also have zero access to your repo. They don't know your folder structure, your test helpers, your naming conventions — nothing. So every answer is generic. It could fit any codebase, anywhere. Generic = useless for real coding work ──────────────────────────────────────── ✦︎ 𝐂𝐋𝐈 𝐯𝐬 𝐈𝐃𝐄: 𝐖𝐡𝐚𝐭'𝐬 𝐭𝐡𝐞 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐜𝐞? Coding-specific tools split into two types: ► CLI — you run them from the terminal, inside your repo ► IDE — they live inside your editor (Cursor, VS Code, etc.) CLI means Command Line Interface. You open your terminal, go to your project, and run something like: `>_ claude -p "add a login test to the checkout suite"` The agent reads your actual code, understands your project, and does the work. ──────────────────────────────────────── ✦︎ 𝐓𝐡𝐞 𝟒 𝐂𝐋𝐈 𝐓𝐨𝐨𝐥𝐬 𝐘𝐨𝐮 𝐍𝐞𝐞𝐝 𝐭𝐨 𝐊𝐧𝐨𝐰 🔹 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 built by Anthropic It has three models for three use cases: - Opus — the most powerful. Complex refactors, hard bugs, architecture decisions. Expensive. - Sonnet — the daily driver. Fast, accurate, handles most coding tasks and documentation well. - Haiku — fast and cheap. Good for the small jobs only: renaming files, adding a helper, generating a fixture. Pricing works on a "window" system. You buy a plan ($20 / $100 / $200 per month) and each plan comes with a usage limit. That limit resets every 5 hours and every week. In practice: burn through your limit at 2pm, wait until 7pm for the reset. It sounds annoying. Once you learn to match the model to the task you rarely hit the cap.
AI Coding Agents for QA: Part 2 — Types of the AI Coding Agent
1 like • 12d
@Art Martinez 100% agree, the difference is night and day
(New Members Start Here) Welcome to AI & QA Accelerator!
👋 Hey there! 𝐖𝐞𝐥𝐜𝐨𝐦𝐞 𝐭𝐨 𝐀𝐈 & 𝐐𝐀 𝐀𝐜𝐜𝐞𝐥𝐞𝐫𝐚𝐭𝐨𝐫. AI is changing Software Development. And it is changing QA with it. QA Engineers who know how to use AI will: ⬩Deliver in days what used to take two weeks ⬩Do work that used to require deep expertise. With AI, basic knowledge can produce senior-level results ⬩Get instant AI feedback on tests, code, and debugging decisions The same applies to Software Developers. AI multiplies their delivery speed. QA becomes the bottleneck. That's why companies are fighting to hire QA Engineers who can match that speed. 💡 In fact, as of early 2026, many companies started adding AI coding tasks to their interview process. QA Engineers who ignore AI won't just fall behind, they risk losing their career entirely. That's not doomsaying. In 2026, tech companies laid off 55,775 people (https://www.trueup.io/layoffs). So, are those layoffs because AI is replacing people? No. AI is not replacing anyone. People who use AI are replacing people who don’t. Unlike the transition from Manual Testing to QA Automation, which took a decade, this shift is happening fast. Capable AI Coding Agents only became real in late 2025. Just a few months later, the entire tech world had changed. That's what this community is about. It's for people who see this shift and understand that right now is not just a pivotal moment for them. It's a short golden window to become one of the first truly AI-Powered QA Automation Engineers / SDETs and set yourself up for a long, safe, and extremely high-paying QA career. ──────────────────────────────────────── 𝐀𝐛𝐨𝐮𝐭 𝐌𝐞, 𝐚𝐧𝐝 𝐰𝐡𝐲 𝐈 𝐚𝐦 𝐛𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐭𝐡𝐢𝐬 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐭𝐲 I'm 𝐌𝐚𝐭𝐯𝐢𝐲, a Vegas-based 𝐏𝐫𝐢𝐧𝐜𝐢𝐩𝐚𝐥 𝐒𝐃𝐄𝐓 with 𝟏𝟎+ 𝐲𝐞𝐚𝐫𝐬 𝐨𝐟 𝐞𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞. I’ve worked across startups and large enterprises, building QA automation frameworks and testing infrastructure across pretty much all modern stacks and tools. In 2025 I introduced AI coding agents into my team's QA Automation workflows. The team adopted it. Management noticed.
(New Members Start Here) Welcome to AI & QA Accelerator!
1 like • 15d
@Ahmed Z Hi and welcome. I DMed you with the guidance
1 like • 13d
@Reshma Mansinghani 👋 hi, welcome! This is my he perfect place to learn automation! If you have any questions- feel free to DM me
📌 AI & QA Accelerator Memberships: Everything You Need To Know
𝐓𝐡𝐞 𝐐𝐀 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧 𝐆𝐚𝐩 𝐍𝐨𝐛𝐨𝐝𝐲 𝐓𝐚𝐥𝐤𝐬 𝐀𝐛𝐨𝐮𝐭 ⤷ You've finished another online course ⤷ You understand a Testing Framework ⤷ You've built a few test scripts, maybe even completed a portfolio project But when you look at job postings asking for "2+ years of QA Automation experience," you freeze. 𝐓𝐮𝐭𝐨𝐫𝐢𝐚𝐥 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞 𝐢𝐬𝐧’𝐭 𝐭𝐡𝐞 𝐬𝐚𝐦𝐞 𝐚𝐬 𝐣𝐨𝐛-𝐫𝐞𝐚𝐝𝐲 𝐬𝐤𝐢𝐥𝐥𝐬. 𝐀𝐧𝐝 𝐞𝐦𝐩𝐥𝐨𝐲𝐞𝐫𝐬 𝐤𝐧𝐨𝐰 𝐢𝐭 𝐭𝐨𝐨. ──────────────────────────────────────── 🚩 𝐖𝐡𝐚𝐭’𝐬 𝐀𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐌𝐢𝐬𝐬𝐢𝐧𝐠: The gap between “𝐈 𝐥𝐞𝐚𝐫𝐧𝐞𝐝 𝐚𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧” and “𝐈 𝐜𝐚𝐧 𝐝𝐨 𝐭𝐡𝐢𝐬 𝐣𝐨𝐛” comes down to 3 things: ❶ Structured, real-world training that goes beyond basics. ≫ Most courses teach tools. They don't teach you how to think like an SDET and QA Automation Engineer, build frameworks from scratch, or integrate CI/CD pipelines the way companies actually use them. ❷ Proof of competency that employers trust. ≫ Saying "I know Playwright" on your resume means nothing without verified credentials. Employers need tangible evidence you can do the work. ❸ Deliberate practice on the exact skills interviews test. ≫ You can't Google your way through a technical interview. You need to have answered these questions dozens of times before you walk into that room. 📌 𝐓𝐡𝐚𝐭’𝐬 𝐰𝐡𝐲 𝐰𝐞 𝐛𝐮𝐢𝐥𝐭 𝐐𝐀 𝐀𝐮𝐭𝐨𝐓𝐞𝐬𝐭 𝐀𝐜𝐜𝐞𝐥𝐞𝐫𝐚𝐭𝐨𝐫 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠: 𝐀 𝐜𝐨𝐦𝐩𝐥𝐞𝐭𝐞 𝐬𝐲𝐬𝐭𝐞𝐦 𝐭𝐡𝐚𝐭 𝐜𝐨𝐦𝐛𝐢𝐧𝐞𝐬 𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞𝐝 𝐭𝐫𝐚𝐢𝐧𝐢𝐧𝐠, 𝐯𝐞𝐫𝐢𝐟𝐢𝐞𝐝 𝐜𝐞𝐫𝐭𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧, 𝐚𝐧𝐝 𝐀𝐈-𝐩𝐨𝐰𝐞𝐫𝐞𝐝 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐩𝐫𝐚𝐜𝐭𝐢𝐜𝐞 𝐭𝐨 𝐭𝐚𝐤𝐞 𝐲𝐨𝐮 𝐟𝐫𝐨𝐦 𝐳𝐞𝐫𝐨 𝐭𝐨 𝐣𝐨𝐛-𝐫𝐞𝐚𝐝𝐲 𝐦𝐢𝐝-𝐥𝐞𝐯𝐞𝐥 𝐒𝐃𝐄𝐓 𝐨𝐫 𝐐𝐀 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫 𝐢𝐧 𝟑-𝟒 𝐦𝐨𝐧𝐭𝐡𝐬 𝐇𝐞𝐫𝐞’𝐬 𝐇𝐨𝐰 𝐈𝐭 𝐖𝐨𝐫𝐤𝐬 ──────────────────────────────────────── 🎓 𝐓𝐡𝐞 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠: 𝐐𝐀 𝐀𝐮𝐭𝐨𝐓𝐞𝐬𝐭 𝐀𝐜𝐜𝐞𝐥𝐞𝐫𝐚𝐭𝐨𝐫 Three volumes that take you from fundamentals to job-ready: - Volume 1: QA Automation & DevOps Fundamentals + Git + GitHub CI/CD - Volume 2: Python + Playwright + Framework Building + CI/CD Integration - Volume 3: Job Search, Resume & LinkedIn Strategies, Interview Prep (Behavioral + Technical + Coding) This isn't a crash course. It's a career transformation program designed around what companies actually hire for. ✅ 𝐓𝐡𝐞 𝐏𝐫𝐨𝐨𝐟: 𝐕𝐞𝐫𝐢𝐟𝐢𝐞𝐝 𝐂𝐞𝐫𝐭𝐢𝐟𝐢𝐜𝐚𝐭𝐞 𝐨𝐟 𝐂𝐨𝐦𝐩𝐥𝐞𝐭𝐢𝐨𝐧
📌 AI & QA Accelerator Memberships: Everything You Need To Know
1 like • Nov '25
@Gerald Hernandez correct, `QamiAI` was built exactly for this use case - to safely give you the experience and knowledge to nail the real interview
0 likes • 15d
@Maxim Pascov thank you very much for the feedback!
1-10 of 57
Matviy Cherniavski
6
1,165points to level up
@matviy-cherniavski-2205
Principal SDET. I teach QA Engineers to use AI Coding Agents to plan, write, and verify real test automation.

Active 28m ago
Joined May 22, 2025
Las Vegas, NV
Powered by