Salesforce: Unique challenges / considerations

Hi all,

I’m on a bit of a learning kick, and something I’d like to know more about is Salesforce. I’ve never worked with it before, or even used it, but I have worked with both completely purpose-built and customised-for-client CRMs.

Are there any particular challenges or special considerations you’ve come across when working with / testing Salesforce apps?

From what little I currently understand, there are ready-made components, add-on integrations, and the possibility to develop your own components. How does this affect the way you go about testing, compared to something built completely in-house? What’s pretty much the same?

I’m interested in anything you care to share on the topic. Thanks!

1 Like

The last time I tested a Salesforce app was for a flight & aircraft management system, I mostly interacted with the solution design, data models, explicit/implicit specs, database(SOQL), and several APIs(Soap) feeding or retrieving the data.
The GUI was quite painful to go through and mostly shallow checks have been done. So we got help from the flight support operations team to go through the flows.
I found the GUI heavy in settings and operations-specific flows(for about 20 types of users). The GUI is quite standard, and I felt it’s more about considering the user’s perspective and getting things done quickly.
I think it’s very useful if you stay long term on a product to learn the business domain very well and know the users, permissions, rights, flows, operations, use/interactions.

2 Likes