Eliya Hasan

ABHI Microfinance Bank, Ltd. • 6K followers

Most QA problems aren’t about tools or people, they’re about processes.If your testers are chasing bugs manually, your devs are guessing coverage, and your releases feel like fire drills, that’s not a resource issue. That’s a design flaw.Process is the real framework. Get that right, and everything else starts to click.#ProcessEngineering #SoftwareTesting #QualityOps #TestAutomation

24

2 Comments

Maaret Pyhäjärvi

CGI • 12K followers

Great that you have a tool to take in selenium scripts to your commercial platform. Do you also have a tool to take them out of your commercial platform? This makes an inconvenient conversation for a fluid chat when networking amongst a lot of tool vendors at #TestMuConf. Why are the commercial tool vendors at large staying silent on the lock in that means the user organizations tests are unusable when the user organization needs to scale down. The maneuverability is significantly reduced when locking into a platform. It is also interesting how commercial tools make the case of faster implementation. Watching people time and time again, discovery of features on a lot of these commercial tools is not an easy task for everyone. As long as we understand constraints, they can play in our advantage. They allow for focus. They allow for one set of definitive answers. But they also mean that we pay rent for the tools to maintain access to what we invested on, and might be better though as renting access over purchasing a tool.

9

Don Schuerman

As CTO and Vice President of… • 16K followers

TLDR: The arrangement of dots in this picture validates Pega's strategic role in orchestrating and automating business outcomes in an AI- and agent-driven world.Longer thoughts: FINALLY!!!For years, we've been telling anyone that would listen that...·     "Umm, maybe RPA isn't a strategic, long-term automation technology." ·     "You know, processes and workflows still kind of matter."·     "No, agents aren't going to magically figure out the rules on their own, nor do you want them doing that."It's great to see this validation from Gartner. Here’s what this report confirms:·     RPA is great, but only as part of a larger orchestration platform (Told ya so!).·     Also, those who have spent years building orchestration platforms might be a little better at it than those who have been focused on building little screen-scraping bots. (Told ya so!)·     Being able to orchestrate AI and agents towards outcomes is essential to getting real value from overhyped tech (Told ya so!).I guess what I’m saying is that the arrangement of dots on this picture – and this picture's very existence – validates what those of us at Pega have been working towards for years. And that feels pretty good.Exciting times, indeed!

564

70 Comments

Brijesh DEB

Infosys • 48K followers

I have been schooled a few times by some of our fellow testers. I hear this often from them:“Yes, critical thinking, testability, risk analysis, and discovery matter. But those things don’t get you a job. What gets you hired is automation or AI skills.”That is true. It is also the clearest sign of how badly our industry has lost its way.Leaders defend this by talking about profitability, margins, speed, and investor confidence. The truth is simpler. It is fear. Hiring for tools looks measurable. It looks fast. It looks good on a board slide. But it is a short term mask that hides long term fragility.Speed without direction is waste. Margins without resilience are temporary. Investor confidence built on trends is fragile by design.Scripts can run all day. Dashboards can flash green. None of that will save you when the real unknowns surface. The only thing that will is a tester who can think beyond the script. Tools extend capability. Testers create insight. One without the other is imbalance.Leaders: if your hiring strategy stops at tool proficiency, you are not building strength. You are buying fragility and calling it efficiency. That may please investors for a quarter, but it will cost you customers in the long run.Testers: automation and AI are skills you should learn, but never at the cost of your core. Your ability to challenge assumptions, uncover risk, and connect quality to business impact is not a luxury. It is your edge.This state of affairs is sad, but not irreversible. Leaders can change how they write job descriptions. Testers can change how they showcase their value. Only then will we stop confusing trend chasing with progress.#softwaretesting #softwareengineering #testingcareers #qualityleqdership #criticalthinking #qualityengineering #brijeshsays

79

20 Comments

Customizo | ServiceNow Elite Partner

12K followers

Automation Test Framework (ATF) isn’t just a feature. It’s a time-saver!ServiceNow QAs who master ATF free themselves up from repetitive manual testing and focus on edge cases, performance, and UX validation.Pro Tip: Treat ATF as your regression safety net. Build it early and update often!

10

Ben F.

Loop Software & Testing… • 15K followers

One reaction I keep seeing in QA (and engineering more broadly) to “the AI thing” is:“I’ve been around for all these changes. People have been saying QA is dead forever. We’re still here.”Just to be clear: I’m not saying QA is dead. I don’t think many serious people are actually claiming that. This reaction feels more like a knee-jerk defense than a real analysis.What’s challenging for me is that when you step back and actually look at the chain of change, this isn’t “just another iteration of the same tools.”For example:We can now write automated tests that don’t rely on the DOM, aren’t flaky, are deterministic, and get cheaper/faster over time. That alone breaks several of the historical constraints that made test automation hard.Within a few weeks, we transitioned a team that had been doing manual UAT into one where those same engineers were scripting automated tests before tickets were even ready, then essentially just hitting “play” when the feature landed.This was a team that had tried (and failed) multiple automation initiatives in the past because delivery pace always outstripped their ability to automate. Suddenly they had 200+ smoke and sanity tests built in a matter of days.I don’t know how you look at that and say, “Yeah, this is the same as before.”Part of this feels like how magazine layout professionals reacted for decades. Printing technology kept evolving, but the core process stayed the same: humans laying out pages by hand. Then computers showed up.Sure, you were still “laying out a magazine,” but it became a fundamentally different process with a different set of skills. Many people made the transition. The ones who said “this kills the art” or “this is a fad” mostly didn’t.This isn’t about QA disappearing.It’s about the work changing shape.And history suggests that when multiple constraints collapse at once, pretending it’s business as usual is the riskiest reaction of all.

17

7 Comments

Jeffrey Nolte

Nolte Worldwide • 7K followers

I used to think QA teams were essential. Now I see them as expensive band-aids for broken processes.For years at Nolte, I believed having dedicated QA was the mark of a professional operation.Then I realized something:If you need people whose job is to catch problems, it means your team isn't preventing them.The best engineering teams I work with now don't have QA departments. Instead:→ Developers own their code from start to finish→ Testing happens during development, not after→ Everyone takes responsibility for what shipsWhen you rely on QA to find your bugs, you're admitting your process is f*cked.Quality isn't something you inspect in at the end.It's something you build in from day one.

157

260 Comments

AutoRABIT

52K followers

#Salesforce security risks aren’t always external. They often come from within: permissions that were never scaled back, code pushed without review, or backups that don’t work when needed.These blind spots create vulnerabilities that erode compliance, slow recovery, and leave your environment exposed.Our new ebook, “Beyond the Surface: Mastering Security Hygiene in Salesforce,” breaks down seven overlooked areas where security hygiene fails and shows how to fix them with practical, proven tactics.https://bit.ly/47gbyXy

18

1 Comment

Provar

12K followers

Ever feel like you’re writing code just to test the code you wrote?That’s the trap teams fall into with traditional Selenium-based frameworks:🔹 More code = more maintenance headaches🔹 More code = more technical debt🔹 More code = testing your tests just to keep upProvar takes that burden off your team. Our low-code test automation means you spend less time managing the tests—and more time ensuring quality where it counts.Michael breaks down the full comparison here ➡️ https://bit.ly/4mXO4O4#testautomation #selenium #provar #lowcode #QA

22

Joe Colantonio

TestGuild • 35K followers

Manual test design can drain weeks of effort—weeks spent aligning requirements, writing scripts, and chasing traceability. 😪 Yet even with all that time, gaps slip through. Teams often end up over-testing the “happy path” while missing critical edge cases that cause real-world failures.In this new episode of the TestGuild Automation Podcast, I explore how GenAI can cut that manual effort down to minutes. With insights from Keysight Technologies’s AI experts, you’ll hear how AI-powered tools can transform natural language requirements into reliable, traceable test cases without sacrificing coverage or accuracy.🎧 Tune in here: https://lnkd.in/eGXYjTiH#AutomationTesting #SoftwareTesting #AIinTesting #GenAI #AITesting #QAAutomation #SoftwareQA #AutomationEngineer #ResponsibleAI #TestGuildPodcast #TestGuildMasterclass #LearnWithTesGuild #Keysight #KeysightGenerator

17

1 Comment

Shannon Whitley

6K followers

Dynamic CSV Strings in Workday with "Replace Delimiter"Have you created a set of calc fields that technically work, yet still feel clumsy or unfinished? You can't help thinking, "I know I can do better."  I had a working solution, but something about it didn't feel right. There were too many evaluate expressions, and the true/false calc fields involved too many other fields.The requirement was to pull all of the address lines for Address Line 2 through Address Line 9 and combine them into a single field.My first solution was serviceable. I built a string by checking if any of the fields were empty. If any preceding field was not empty, I'd add a comma delimiter to separate the data. The string had to be a variable set of commas with no unsightly gaps (ex: ",,").My second pass at the solution uses the Format Text calculated field type. I love the Replace Delimiter option -- It would almost be perfect if it supported regular expressions (including whitespace), but it's a huge step in the right direction.My most recent solution uses Format Text with Replace Delimiter to substitute characters to get to the final set of comma-separated values. The screenshot of my report shows the initial calc field of concatenated values with the final result of the delimited string.These are the steps for getting to the result.1. The first calc field is a Concatenate Text type that delimits all of the fields with non-standard characters to be replaced. I use the backslash to begin and end the string. Tildes are used in between each field.\Address Line 2~Address Line 3~Address Line 4~Address Line 5~Address Line 6~Address Line 7~Address Line 8~Address Line 9\2. After that, I use a series of Format Text fields to replace the tildes, starting with the greatest number possible if all of the fields are blank.Format TextSource FieldAddress Lines 2 - 9OptionsReplace DelimiterText Delimiter~~~~~~~Replacement Text~3. I then copy the Format Text calc field multiple times, reducing the number of replacements with each calc field. I repeat this step until I get down to 2 replacements. Notice the Source Field is a reference to the previous calc field.Format TextSource FieldAddress Lines 2 - 9 - Tilde Replacement 3OptionsReplace DelimiterText Delimiter~~Replacement Text~4. When I get to the final replacement calc field, I convert the tilde to the comma + space.Format TextSource FieldAddress Lines 2 - 9 - Tilde Replacement 2OptionsReplace DelimiterText Delimiter~Replacement Text,{invisible space}5. The final three calc fields clean up "Backslash Comma" -- "Comma{space} Backslash" -- and "Backslash" by itself. I provide one example below."Backslash Comma"Format TextSource FieldAddress Lines 2 - 9 - Tilde Replacement 1OptionsReplace DelimiterText Delimiter\,Replacement Text {empty}As always, this is just one approach. I'd love to hear how you've tackled similar requirements!

84

11 Comments

Sushmitha Narayan

Piramal Capital & Housing… • 3K followers

🚀 From Developer to Technical Program Manager (TPM) – Here’s How I Did It (And You Can Too!) 🚀Ever thought about transitioning from a Developer or QA role into TPM but felt unsure where to start?I’ve been there! It can feel like a big leap, but trust me—it’s absolutely possible with the right approach.Here’s what helped me (and can help you too):✅ Build a Strong FoundationBefore diving in, it’s important to understand what a TPM actually does—bridging technical execution with strategic planning.A great starting point?The Google Project Management Professional Certificate on Coursera.This course helped me grasp program management, stakeholder communication, and risk assessment—all key skills for a TPM.✅ Gain Practical ExposureOnce you understand the fundamentals, the next step is hands-on learning:💡 Volunteer to shadow a TPM at your company.💡 Take the lead on cross-functional projects that involve coordination, planning, and risk management.💡 If you see a gap in program management at your company, step up and fill it!✅ Network & Learn from TPMsOne of the biggest game-changers for me was talking to people already in the role:🚀 Reach out to TPMs on LinkedIn—most are happy to share insights and advice.🚀 Join TPM communities like TPM Trails, attend meetups, and get involved in discussions.🚀 Find a mentor or coach who can help you navigate the transition.✅ Get Hands-On ExperienceYou don’t need an official title to start thinking and acting like a TPM:✔️ Drive initiatives within your current team.✔️ Take ownership of cross-team communication and risk management.✔️ Show leadership in resolving blockers and driving alignment.✅ Take Action Today!If you're serious about making the switch, start today. Small, consistent efforts add up. The sooner you take that first step, the closer you are to landing your first TPM role!#TPM #TechnicalProgramManagement #CareerGrowth #ProjectManagement #Leadership #CareerTransition

74

5 Comments

Matt Pieper

Matt Pieper Photography • 17K followers

After careful consideration...I've decided I'm wrong about Flows.They're a powerful tool and perfect just the way they are.I've realized that there's no reason to add unit tests or better error handling.Because Salesforce was right, engineering excellence isn't needed for automations that drive critical workflows across an enterprise.Especially for money movement or regulated industries.So, this is my mea culpa.Apologies to all you #Flownatics and Salesorce product managers.#salesforce #flow #businesssystems #salesforceflow #awesomeadmins

150

67 Comments

NI (National Instruments)

265K followers

Should you build or buy a test executive for your test system? Before you decide, take the time to understand what the software does and how it can support your specific workflow needs. Our guide includes everything you need to make the right choice. Grab a copy: https://bit.ly/4mTuUIU

22