Salesforce Fact #63 | test class tip

It is always a best practice not to use org data in test class. Instead we should create our own data for testing.

However, if we need to get a particular record during our testing we can get that using SOQL. But the records will be like read only. Any changes made to the record in the test class would not be reflected in the original record.

In this example, we are fetching one account named 'test' in the test class. Now, although we are changing the name of the account and also updating the same, also the assert is successful, the original record is unchanged.

Attached are the screenshots.



 

Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more