StickyMinds

The new year is here, and in the world of QA, "business as usual" no longer exists. With the rise of AI-native development and autonomous agents, the "top of your game" is a moving target. 🎯 That’s why events like #STAREAST 2026 are so crucial

Grab Jesse, jump in the RV, head west (or east, or north, or south... we don't actually know where you are right now) and meet us at #STARWEST next week!

Untestable? Seems a little extreme. Or is it? 😁 Join me @TechWell 's @STARWEST next week. Plus it is at #Disneyland! starwest.techwell.com/program/concur…

Want to keep up with the latest in software testing and QA? The #STARWEST virtual conference happening Sept 24-25 has both a free and an upgraded option for attending. Check it out here: starwest.techwell.com/virtual-attend…

Only a few days left for the #STAREAST 2026 Call for Speakers. We want to hear your story. Submit to speak before Sept 7 here: stareast.techwell.com/speak-stareast #callforspeakers #qualityassurance #softwaretesting #conferences

Exciting changes are coming. A brand new StickyMinds will launch soon and we can't wait to share it with you. The new @StickyMinds will encompass all things software engineering including the latest #agile #DevOps #security #AI #softwaretesting and more.

Just a reminder that #STARWEST is happening in just under 2 weeks. Can't join the premier #softwaretesting conference in person? We have a virtual options (including a FREE pass) starwest.techwell.com/virtual-attend…

To see whether a change in the code has affected other existing features, we need to perform #regressiontesting. But how do you make time for another test cycle? For Shuja Naqvi, it meant getting involved earlier in the SDLC: well.tc/5e8s

A good tester is a problem finder as well as a problem solver. Nicholas Snogren explains how finding bugs requires exploratory testing superpowers, like X-ray vision: well.tc/5e2s

After a developer fixes some code, does the responsibility for retesting belong to the dev or the tester? And if the bug is no longer there, how do you classify and close it? Read and weigh in: well.tc/5e2e

Risk-based testing helps us handle our limited resources by prioritizing risks. Here are some practical tips, examples, and steps you can use to adopt risk-based testing: well.tc/5e2n

Automated testing often returns "failures" that are not actually failures. Whether they are false positives or false negatives, @mheusser says we need a way to fix the automation tooling. well.tc/5e2h

How to Accelerate Your Release Cycles with #AgileTesting - Akshaya Choudhary well.tc/5d93 #agile #testing

The Hidden Costs of #Automation - Ajay Balamurugadas well.tc/5d94 #testautomation #testing

"The cornerstones of communication around quality in #agile delivery are the definition of ready and the definition of done." Balazs Schaffhauser well.tc/5dnf

Whether you’re a software tester, business analyst, or someone who needs to come up to speed rapidly on a subject, we often lack the luxury of having a SME available to answer questions. When that’s the case, we have to become our own #SME.—@sullytester well.tc/5guz

"When people do not have good luck with automation, it is hardly ever because of the tool being used, but almost always because of the wrong automation strategy, wrong expectations, and wrong adoption of #automation." - Akash Bhatia well.tc/5fuz #testautomation

In this interview @JannaLoeffler talks about how #testers are often not comfortable saying “I don’t know,” and about how they should get out of their comfort zone to ask for help: well.tc/5fua

The growing role of AI in DevOps: @jenfultonbrown well.tc/58e7

Uplifting QA teams through metrics @DilrubaMalik well.tc/58e8