Art Kiryukhin

📖 Playwright Test Automation Best Practices for QA Engineers This article provides practical best practices and setup tips for building efficient, stable, and maintainable Playwright test automation suites, covering aspects such as project structure, fixtures, mocking, parallel execution, and flaky test mitigation. #Playwright #E2E #TestAutomation #FrontEnd

2

😱 “Can QA just quickly approve this?” In their minds, QA is a straight line: ➡️ Send document ➡️ Get approval ➡️ Move on Nice. Simple. And completely fictional. Because the real QA path isn’t a straight shot from A to B. It’s a series of well considered steps. i Before anything gets the seal of approval from QA, someone has already mentally walked through a whole chain of questions: 🤔 What is this really changing, and why now? 🤔 What does this touch — process, equipment, risk, training, validation, suppliers? 🤔 Does this clash with an existing SOP, WI, or form somewhere else in the system? 🤔 If an auditor asks “show me the story behind this,” will the evidence make sense? We’re not “being difficult.” We’re just trying to make sure today’s quick win doesn’t become tomorrow’s deviation, recall, or regulatory slip up. Good QA work can often appear invisible because the bad thing… never happens. No batch failure. No deviation. No “how did this get approved?” email. No warning letters. Just a quiet system that keeps functioning, safely, for patients and for the business. So when somebody says, “Can you just quickly approve this?”, we chuckle. Not because it’s really that funny. No, (it’s really not very funny.) But because the contrast between the straight line in their head and the reality of the carefully connected line QA is drawing is, let’s say… striking. Yes, it’s not as simple as a single straight line. But it’s this line that connects today’s shortcut to tomorrow’s consequence. It’s this line that chooses patient safety and long-term quality instead of quick wins. 💭 What’s one thing you wish people knew about what it really takes for QA to approve something? Share it below and help demystify that squiggly line 👇

1,493

60 Comments

Quality Assurance (QA) can be learned by *anyone*, but whether it's the right fit depends on the individual's interests and mindset. QA *is for you* if you: * Enjoy finding problems and figuring out how things work. * Pay attention to details. * Like improving processes or products. * Are curious, analytical, and patient. * Want to be involved in the software development lifecycle without necessarily writing complex code. QA might not be ideal if: You dislike repetitive tasks (especially in manual testing). You’re not interested in logic or analytical thinking. You’re only looking for a highly creative or artistic role. Good News: Beginner-friendly: It’s one of the easiest entry points into tech. No coding needed at first:Manual QA doesn’t require programming, though automation and career growth often do. Career growth: You can move into roles like Automation Engineer, Test Architect, or even Product Manager or Developer with time. #qa #sqa #tester

1

Most QA engineers spend days (sometimes weeks) just setting up test environments. 🕒 By the time everything’s ready, the product’s already changed. What if setup was instant? That’s exactly what this webinar covers. You’ll see how AI can instantly understand your Playwright project, identify test cases, and generate stable, production-ready tests in minutes. Plus, you’ll learn how to integrate them directly into your CI/CD workflow without rewriting your existing setup. Join our webinar with Tal Barmeir, Sapnesh Naik, and Rebecca Villalba from BlinqIO. 👇👇👇 https://lnkd.in/eT8AKgwN #ai #multilingual #testing #qa #blinqio #autonomous #ttm #aitestengineer #vibetesting #aitesting #softwaretesting #TestGuildWebinar #WorkWithTestGuild

34

Most SR&ED claims don't fail because of weak tech 👇 They fail because of missing documentation. Versioned design docs, commit messages that explain intent, and tagged sprint notes matter as much as the code itself. Here's a practical guide on building SR&ED-ready documentation that your future self (and your CFO) will thank you for. 🔗 https://lnkd.in/gE5wRugi Oh, and Canada Revenue Agency - Agence du revenu du Canada will thank you too. Make sure your SR&ED applications are defensible. #SRED #IRAP #RDTaxCredits #CRA

1

How do you test a product when there are no specs, no docs, and no clear requirements? If you’ve ever been told, “Just test whatever’s there,” this article is for you. At Certiva QA, we know the struggle is real and common. But guess what? These kinds of projects are also where great QA engineers truly shine. In this article, we break down ✅ How to approach testing without formal documentation ✅ Exploratory techniques that actually work ✅ How to ask the right questions to uncover hidden risks ✅ What we do at Certiva QA to thrive in ambiguity Being a great tester isn't just about executing test cases. It's about thinking critically when there’s little to go on. Read the full article here: https://lnkd.in/dBtcXAZT #QualityAssurance #SoftwareTesting #ExploratoryTesting #AgileTesting #QATips #NoSpecsNoProblem #CertivaQA #QAengineer #TestingWithoutRequirements #RealWorldQA #BugHunting #TestLeadership #QACommunity #TestSmart

6