How Provar Can Help You with Root Cause Analysis

Published by Josh McNamara, January 20, 2022
Salesforce, Thought Leadership

I have spent my entire career helping enterprise companies solve complex challenges to scale, and the number one takeaway I have learned? From the top to the crop, everyone carries their fair share of weight when it comes to software delivery.

In this resource, we will cover how your support teams are essential to delivering world-class software. In addition, we walk through a real-case scenario to provide scalable strategies for your delivery and support teams, and finally, how Provar can help you become defect free.

We all know that your first line of defense is your help desk support team. The technology firefighters triaging right now problems for people who demand right now solutions.

For those of you already leveraging Provar to scale test automation for your Salesforce projects, we have a surprise for you. The next time you are doing root cause analysis on a reported potential production defect, consider rerunning the feature test script in production without leaving a footprint to get the whole story of impact.

Isolate your purview to seeing exactly what users, roles, and profiles are impacted through Provar’s polymorphic design by testing them all with just a click. Equipped with built-in screenshot capabilities, you now have the opportunity to identify the problem faster and more efficiently saving you, your users, and your team’s valuable, irreplaceable time. Looking for the defect? Just replay the script!  

Now that we have covered the importance of help desk teams as an essential part of your software delivery and how Provar can help, let’s walk through a real case scenario with some insights to bring back to your delivery teams. 

Meet Dewey: a Real-Case Scenario for Help Desk Teams

How many times have you leaders at the help desk received a similar late-night Slack message? 

Let’s meet Dewey Doneright, a new member to the help desk team and the above image is his first ticket. “Okay Dewey don’t panic. The ticket was raised by a department manager with key influence in the organization. You know you must be fast and effective here.” 

Dewey recalls rule number one from their training – it’s not a defect until you can replicate the reported problem and screenshot it. But Dewey can’t, the manager didn’t tell them exactly who could and could not access the account. They didn’t tell Dewey that this issue is potentially impacting the entire North American (NA) Sales group, which should have 500 users assigned.

As a help desk team member, Dewey can’t possibly be expected to individually review all 500 user assignments to the profile group and login as 500 different people individually to verify. But being the problem solver that Dewey is, they know that there must be an easier way.

The delivery team is using that new Provar testing automation tool where they can test dozens of profiles at once with just one script. Dewey decides to go into the testing project, locate the script they used for profile assignment and permissions for the new Account record type and run the test again. 

Dewey tells himself, “That way I can find out without creating any net-new records in the production environment. Perfect!” So, Dewey sets off to accomplish his goal, but soon learns that he does not have access to the Provar testing tool. Dewey contacts his new work friend and teammate, Marty, on the warranty team explaining the problem and Dewey shares his approach to identifying the potential root cause of the issue.

Admiring Dewey’s thoughtful approach, Marty runs the test and confirms that there are in fact 12 people in NA Sales who were added at the last minute after the production deployment. Since they were not assigned to the NA Sales group, they do not have access to the new Account record type. Marty attaches the screenshots to the reported defect. Dewey thanks Marty and rushes off to his daily team standup.

Dewey Faces His First Standup: Based on a True Story

Scrum Master: “Thanks for joining us, Dewey. What have you done? What are you doing? What are your roadblocks?”

Dewey: “I received a critical severity defect impacting the NA Sales group this morning. Tyler, the VP has reported that many of their sales users were not able to access and edit the new account record type “Commercial.”

“They have 500 users in their group and since I only have 24 hours to resolve the issue, I felt like there was an easier approach to reviewing all 500 users’ and their profile assignments and logging in as each one to confirm access wasn’t the best use of time, so I thought outside the box, while staying in it.”

“I don’t have access to the tool I wanted to use so I reached out to Marty on the delivery team, explained the situation and my suggested idea of rerunning the test scripts in production to check the user profile assignment of the NA Sales User Group. The tool identified 12 users who were added after the production deployment, but were never assigned. So it was a miss.”

“But before standup, I updated the 12 users to the correct profile assignment, and they now have expected read/write access to the new Account record type. I have updated the ticket, notified the reporter that the problem has been identified and resolved. I have also briefed our DevOps team on the situation, and they are updating the miss in their repositories so that all lower environments will be in sync.” 

Scrum Master: “Great work, Dewey Doneright! Let’s talk more offline about this testing tool you mentioned. Sounds like something that we could really use to help save us time in the future.”

As a leader, thanks to the polymorphic capabilities of Provar, our E2E solutions are here to support every member of your delivery teams, while saving the one thing that you can’t afford to live without – time. Although software defects are created by humans, it also takes a human using an intuitive tool to improve your delivery. Thank you to the help desk humans for all that you do to keep the lights on for the rest of us.

At Provar, we believe that testing Salesforce should be as easy as using it. Click here to learn more about how our unbreakable, polymorphic, E2E, and intuitive solutions can help you scale your Salesforce test automation.

We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

Scroll to Top