Discover how to navigate the common challenges of implementing UTAM, from mindset shifts for QA engineers to managing dynamic UIs and limited ecosystems. This blog provides practical solutions to enhance productivity, reduce costs, and accelerate release cycles, backed by real-world case studies and credible sources. Learn how UTAM can transform your Salesforce testing strategy to ensure your applications are robust, reliable, and ready for any challenge they may face in today's fast-paced digital landscape.

Discover a comprehensive guide to End-to-End (E2E) testing, covering the Test Pyramid, expert insights from Fowler and Dodds, and practical strategies for enterprise architects. Learn how Salesforce and UTAM streamline E2E testing for seamless workflows and robust automation.

This post is my attempt to reach out to Salesforce with a full narration of a bug in Security.stripInaccessible() method with protected custom settings only. Also, this could help any ISV Partners using Security.stripInaccessible() with protected custom settings and running into issues.

In the world of web development, especially when it comes to building Single Page Applications (SPAs) with frameworks like Angular, one concern stands out: protecting your intellectual property (IP).

In the ever-evolving world of web development, Angular continues to support developers. This guide dives deep into leveraging Angular within Visualforce to create dynamic single-page applications (SPAs).

As suggested by Salesforce docs, one can use services like requestb.in or inspectb.in to test outbound messages. But these services are pretty generic so they just return 200 / OK response for any inbound…

You can easily run into this error if you are trying to perform DML on setup and non-setup objects in the same transaction. Non-Setup objects can be any one of the standard objects, like Account or any custom object.

Here are a few examples of the Setup Objects:

This post is about an issue that comes with Apex-managed sharing, i.e. System.SObjectException: Field is not writeable: Sobject__Share.RowCause. We faced this problem recently and tried searching…

To merge these Apex-CRUD-FLS-Validator APIs with Force.com ESAPI, I discussed with Yoel Gluck. Yoel maintains the Google Code project for ESAPI and is “Salesforce's Lead Product Security Engineer”. In our discussions about adding these new APIs to the Force.com ESAPI project, we devised a plan to merge the APIs…

Force.com IDE is already doing a decent job on top of Eclipse. It provides a nice Visualforce editor with syntax highlighting and code indentation based on the standard Eclipse HTML Editor. I recently tried to create a couple of Visualforce code templates/snippets to quickly assist in creating the pages and was successful in that attempt. The rest of the post describes how.

Dear Apex developers, who are using HTTP Restful Classes know that testing the callouts is not allowed in Apex. People came up with their own smart ways to handle this restriction.

All Apex developers creating Visualforce pages with drop-downs and checkboxes use the Apex SelectOption class. On most occasions, instances of this class are created out of records in a database that we can query in a desired alphabetical order

This post is for guys who are planning to release their app on App Exchange and are looking forward to clearing the security review in one shot! This post aggregates all the good links and information you should have in hand.

While fixing security issues for a customer, I came across a very interesting and powerful security API from Salesforce, i.e., Force.com ESAPI. As per the Google code description, this API…

This might be a requirement, if you are developing some complex navigation…

I saw this tweet today about the apex-fast-xml-dom library. Unfortunately, it's true that FastXMLDom can’t support CDATA sections as of now. This is because FastXMLDom is a wrapper on top of Spring’10 Apex DOM classes, and DOM classes don’t support CDATA sections.

Apex programming WSDL can be downloaded from the “Setup” area of your Salesforce org. Just land on the “App Setup > Develop > API” page. Instructions to download are shown below: