Jon Robinson

Let’s talk QA metrics — because guessing ain’t it! From tracking defect density to checking test coverage, the right numbers help you spot what’s working (and what’s not) real quick. Metrics = your secret weapon to kill defect leaks, boost automation ROI, and make smarter moves that actually improve your testing game. Why settle for ‘meh’ when you can go full-on QA legend? Numbers don’t lie, so let’s measure what matters and level up together. #QATesting #MetricsThatSlap #QualityGoals #TechVibes"

20

2 Comments

Coded tests? As flexible as putty at first. It’s actually rapid set concrete that becomes a constraint on your business This is an argument for the BUSINESS VALUE VELOCITY that AI enabled natural language testing enables (Not just the superior cost of ownership). To misquote The Martian. You’re going to have to “AI the sh*t out this” to create, maintain and accelerate the market place velocity now required to delight, excite and attract customers and employees (yes them). No matter what. Dragging a ships anchor of legacy test coding and creating even more “instant legacy” just won’t cut it.

1

Isn’t it wild that even seasoned testers are losing their jobs these days? It’s tough out there. And when you’re applying for that next role, you’re probably up against them, too. 🫢 So, how do you make sure you stand out in a market that’s more competitive than ever? That’s where Katalon Academy comes in. With FREE certifications, you can prove your hands-on experience using Katalon Studio—a skill that’s in high demand for automation testing roles. No exams, no pressure—just practical tasks that let you show off what you can really do. With over 8,000 certificates issued, plenty of testers are already using these credentials to boost their LinkedIn profiles and get noticed by recruiters. In a market like this, getting certified isn’t just a nice-to-have—it’s your edge. Build credibility, stand out, and grab that next opportunity before someone else does. 👇👇👇 https://lnkd.in/edGB4EX8 #KatalonAcademy #TestAutomation #SoftwareTesting #LearnAutomation #KatalonStudio #APITesting #WebTesting #CareerInTech #AutomationTools #QualityAssurance #WorkwithTestGuild

37

2 Comments

I'm writing a book about Software Testing & QA Strategy. As part of my research, I'd love to talk with QA managers & directors about the challenges you face in QA leadership and how you solve those issues. I'd also love to hear from testers in the trenches whether you're focused on manual or automated testing. What are the the tools and technologies you love or hate? What are your daily frustrations? Finally, I'd like to hear perspectives outside of QA - from developers, product owners, SRE, and senior management. How is testing perceived in your organization and what could make it better?

75

14 Comments

Quality must be integrated from the start of the development process, it's an afterthought that Involve QA from the start, plan for edge cases, and build excellence into every step to prevent issues before they arise. #quality #development #productquality

3

2 Comments

“Software Testing isn’t our number one priority right now, so we’re just going to ignore it until it is.” I hear something like this from most software teams. And it’s a huge mistake. Here’s why. First, I get the impulse:  -Software Testing generally and Test Automation specifically aren’t things anyone wants to nerd out about (except me!) - At a startup, you have to let small fires burn. That’s just the nature of the game - Most people think that investing time and money in Software Testing is DIRECTLY COMPETITIVE with investing in new features & product development But here’s why it’s a bad idea: - Quality ALWAYS comes back to bite you - And if you don’t invest in Test Automation early, it gets more difficult & more expensive to get Test Automation working later - When Software Testing is an emergency, and you need to automate it… it’s not something you can snap your fingers & it’s fixed Plus - it is easier than ever to invest a little in Software Test Automation and get a ton out of it. We’ve seen dozens of customers investing thousands of dollars - not hundreds of thousands - and getting a full test automation regression suite set up in weeks (not years), thanks to AI. I believe more teams are going to invest earlier in Software Test Automation thanks to AI. I hope that’s the case - because by the time Software Testing is your number one priority… it’s usually a BIG clean-up job.

7

1 Comment

Here's why everyone in tech HATES Software QA and Testing: - Non-technical execs don't understand why QA/testing exists… isn't it engineering's job to write quality software? - Engineering leaders view QA/testing as a necessary evil, and test automation is slow, expensive, and boring - Developers get resentful when their code gets thrown back at them with 26 bugs they didn't consider (a.k.a "my baby is ugly" phenomenon)  - Sales doesn't realize QA/testing exists - Testers start to hate QA/testing when they're constantly underfunded and overworked Anyone I miss? p.s. ok ok, almost everyone, two notable exceptions: experienced/wise eng leaders, great/innate testers

23

1 Comment

Very good post 👇🏻 The “when” is now easily solved with Gen AI autonomous script creation. Find out more at www.qaaas.ai

2

Ok, everyone has an unpopular take. Here is mine. Your testing is flawed. All of it. Automation? Flawed. Manual? Flawed. BDD? Flawed. Code coverage? Flawed. Entrance or Exit? Flawed. Performance? Flawed. Environment? Flawed It's all flawed. Why? Because the moment you put something into Production, that is a series of variables you CANNOT duplicate in test scenarios. Because there are dozens of other systems out there that you have to play nice with, and you CANNOT duplicate these in test environments, Because the customer has expectations that the moment you flip the switch, things will work out of the box and everything will sync up nice and everyone will be happy. Until Mary can't get to the Company Payroll systems because no one mentioned that tidbit in Discovery calls. You CANNOT duplicate Mary. And, there is a flaw in this post. Did you find it?

1

5 Comments

There are many people out there that say creating an Auto Qa platform is easy, just some basic prompts. I’ve heard it’s just a GUI on top of an llm, anyone can do it. Good luck. The amount of time and skill to create prompts that cover ever single situation is a level of prompting your can only get by having a team doing it every day for 8 months on a single use case. I think anyone that is building “interfaces” on top of llms that really work well are doing amazing work. You have no idea how hard it is until you are trying to get an Ai model to understand the different business rules of hold compliance/business rules vs dead air vs silence for multiple companies with different rules for each one, and that’s one of the easier topics we solved for. That’s why I am so proud of what we are doing. It’s not easy, but we are doing it. #autoqa OttoQa #ai #callcenter #contactcenter #callcentergeek #cx

13

BDD vs. Traditional Frameworks: A Comedy 😂 Act 1: The Skeptics: "BDD? Gherkin? More work for no reason! I'd rather wrestle a kraken than write in plain English!" Act 2: The BDD Evangelist: "Hold on, my friends! BDD is like a well-organized toolbox, not a kraken's lair. Let me show you the light!" Act 3: Separation Anxiety (Solved): "With BDD, test cases and code are like a happily divorced couple – living separate lives but still getting the job done. No more Frankenstein test methods!" Act 4: Reusability Rhapsody: "Steps are like LEGOs – build once, use everywhere! Traditional frameworks? More like a jigsaw puzzle with missing pieces." Act 5: Hooks – The Heroes of the Hour: "Logging, cleanup? BDD's hooks swoop in like ninjas and handle it all behind the scenes. No more code clutter!" Act 6: Onboarding Nirvana: "Newbies, rejoice! BDD specs are your onboarding manual. Learn the features, copy the steps, become a testing superstar in no time!"

6

1 Comment

Do you know the best way to get started with Playwright? What is the best AI/LLM for Testers? Have you seen the mind-boggling Selenium stats? Find out in this episode of the Test Guild New Shows for the week of June 23rd. So, grab your favorite cup of coffee or tea, and let's do this.   Featuring automation awesomeness contributions from: Igor Dorovskikh Vasyl Shpak Engenious Playwright Bruno Lopes Ole Lensmar Testkube Kubeshop Jan Molak John Ferguson Smart BrowserStack Jason Arbon Sai Krishna Srinivasan Sekar Sudharsan Selvaraj Appium Nandan Mullakara Selenium 🤖 Jason Huggins Simon Stewart Gearset Kevin Boyle Juan Fumero Monica Beckwith   ** ALL LINKS IN THE COMMENTS BELOW ** #devsecops #automationtesting #softwaretesting #performancetesting

117

16 Comments

Maybe its just the algo, but I have seen a lot of debate on here around testing in CI/CD; folks blaming flaky tests, runner issues, environments, saying its a waste of time to automate contract and integration tests in sprint, etc. I do not rebut the health and reliability of your pipelines directly correlates to velocity, but imploring a strong test strategy in CI via the pyramid from a product's conception is paramount. As a QE architect on a project I was on paternity leave for 6 weeks during one of the busiest times of year. I came back to a perfectly healthy application and pipeline with brand new features as well as 0 regression. How did we do it? Well simple: people before processes and whole team ownership of Quality. Having a team of software and platform engineers with the same value on QA smooths and accelerates releases; you cannot change my mind on that. Our Quality Engineering team contributed directly to velocity in the form of automated checks and tests directly in the same feature branches that get promoted to UAT/Production daily, i.e. we do not release code that hasn't be vetted. I don't know what kind of bureaucracy folks are running into adopting industry leading best practices and I feel for you on that front. It starts with leadership; when your CEO, CTO, and VPs truly understand and value DevSecOps, they enable the PEOPLE at their organizations to lead with quality first. Solution and Product owners who bake time and point stories with quality testing in mind as well! Our team was able to build and maintain hundreds of tests because of how we operate with one goal: building a quality application!

6

Engineering Managers are drowning in testing candidates—Who’s really failing here? Strangling your engineering team? That’s a death wish. Smart execs don’t play that game. Your product’s begging for attention, and you have customers you need to deliver to. But here you are, jamming the gears with testing candidates instead of focusing on delivering to your customers. Engineers spread thin? They hate the hiring circus. Watching hopefuls bomb tests? That’s just burning daylight. Time, resources, money—you’re torching it all. That’s where we step in. At Savant Recruitment we’re not just pushing resumes. We’re building business'. Our partnerships include: •ScaleHR •Flow, a Deloitte business •Communitech •CoderPad •Wages Corp •Viewpoint.AI + we are working on adding more to be your one stop shop for all your needs to GROW AND THRIVE. We will test your engineers in over 99+ Languages and Frameworks and take this all on my end, so you never have to see a candidate until they pass a technical. This has saved so much time, money, and headaches for execs who are serious about their business and their customers. Although we've been open for 2.5 years, this has been a decade in the making. Test, refine, iterate—again and again. Our gospel? Test till you can’t no more. The old motto is ‘Always Be Selling.’ I say ‘Always Be Testing.’ You can pitch till you’re blue—real power’s in the pivot and drive to do things majorly different and throw away all the old playbooks. We solve real issues that your business' are facing. Why? Because there's no 1 size fits all approach. So for every business problem, we aim to have a solution for it. Your leadership sucks? You come to me Your dev team isn't performing how they should? You come to me Need more incentives in your business? You come to me Can't make decisions? You come to me Want to hire a contractor without the headache of worrying about Payroll? You Come To Me Want to shake up your process and refine it reducing time to fill? You come to me Want to save money, time and headache? You come to me I'm the person you come to, who knows someone, who knows someone, who knows someone, and so forth. If you’re not shaking the status quo, you’re just another face in the crowd. I’m not here to blend in. My take might ruffle feathers. I’m not chasing a popularity contest; I’m chasing deliverables. We’re the ace up your sleeve, building teams that break barriers and doing all the heavy lifting so your Engineering Managers can set it and forget it. I’m after victories with companies that want to get out of this "go for bronze" culture, not validation. So, who's ready to leave "good enough" behind?

98

7 Comments

QA engineering might sound boring, but if you think that, you’ve got it wrong. Completely wrong. QA engineers are the ones who stop disasters before they happen. They’re the ones who keep everything from crashing down and make sure what goes out actually works. It’s not some checkbox-pushing job—it’s high-stakes. 1️⃣ Problem-solving every day: Bugs? They’re just challenges that sharpen your mind. 🧠 2️⃣ Own the quality: You’re the one making sure the product is rock solid. Without you, chaos reigns. 💥 3️⃣ Always improving: The best QA engineers are constantly leveling up, learning new tools, and staying ahead of the game. 🏆 So if you think QA is boring, think again. Real impact, real responsibility. That’s what QA is about. 💪 #QAEngineering #MasterOfQuality #TestingChampion

86

3 Comments

This is one of the most common reasons why teams fail to innovate in the Salesforce ecosystem. Release cycles takes too long and with a lot of rework that eats the room for innovation work. Most of the teams suffers from it. If this is your case, take a quick read. We have the solution.

15

Are your #QA processes slowing down for no apparent reason? You might be dealing with technical debt. Let me break it down: Technical debt in QA is the accumulation of "quick fixes" and shortcuts we take to meet deadlines. Think of it as borrowing time from the future. How does it impact QA efficiency? ☁Tests take longer to run ☁More false positives and flaky tests ☁Difficulty in adding new test cases ☁Time wasted on maintaining outdated scripts Identifying technical debt: 🔶Look for tests that frequently fail for no clear reason 🔶Check how long it takes to onboard new team members 🔶Count how many workarounds your team uses daily Quantifying the cost: ✳Track time spent on test maintenance vs. new test development ✳Measure the delay between finding and fixing bugs ✳Calculate the cost of missed bugs due to incomplete testing Reducing technical debt (without breaking everything): 1️⃣ Set aside "refactor time" in each sprint 2️⃣ Prioritize updating the most problematic areas first 3️⃣ Implement better coding standards for new tests 4️⃣ Gradually replace manual tests with automated ones 5️⃣ Invest in training to keep your team's skills current Remember, dealing with technical debt is like cleaning your garage or pantry. It's not glamorous, but it makes everything work better in the long run. What's your experience with technical debt in QA? Any tips to share? #QualityAssurance #TechnicalDebt #SoftwareTesting #ContinuousImprovement

5