Testing low code versus pro code

One of the key benefits of the Salesforce platform is its declarative, low-code tools. The declarative approach makes some changes, such as adding fields, really simple and almost trivial. With this quick pace of change, it is easy to get swept along and forget that any testing is required. In this example, the field itself is only one element. It needs to be on the correct page layouts, be visible and editable by the right Users, and be checked to ensure that if it is a required field or has validation, existing processes do not break. These other elements can be easily overlooked but have significant security and integration implications. No system-enforced process requires declarative changes to be tested. However, as the capability of the low-code tools increases, as seen with the automation capability of Flows, there is a move to introduce testing options. Now, you have options to debug your Flows and for some types of Flows, you can also create...