Showing posts with label Best Practices. Show all posts
Showing posts with label Best Practices. Show all posts

Wednesday, 7 August 2019

[#Blogged] Best extensions to use to improve your Salesforce Experience -Part 01

Salesforce(Salesforce.com) is a CRM (Customer Relationship Management) which bring companies and customers all together.

Salesforce created the 1-1-1 Model of Integrated Philanthropy, where companies contribute 1% equity, 1% of their product and 1% of employee hours back to the community.

Salesforce Ecosystem which is called #SalesforceOhana consists of world-class Developers, Consultant and Administrators all over the globe.

Salesforce Products

Sales Cloud

Service Cloud

Platform

Marketing Cloud

Commerce Cloud

Community Cloud

Quip

Demandware

Heroku

MuleSoft

with over 100,0000+ customers.

Most recently, the software company acquired MuleSoft for $6.5 billion and Tableau Software for $15.7 billion.

Install and manage extensions

Open the Chrome Web Store.

Find and select the extension you want.

Click Add to Chrome.

Extensions will let you know if they need certain permissions or data. To approve, click Add extension

Extensions are add-ons which help improve Salesforce Experience by Amazing Developers & Companies.

1 - Salesforce inspector

62,461 users

Productivity tools for Salesforce administrators and
developers to inspect data and metadata directly
from the Salesforce UI

Extension Link: https://bit.ly/25BUQuR

2 - Salesforce advanced Code searcher

38,736 users

By using the advanced quick find you can get your code few clicks shorter. Also, you can search any string your code

Using this extension you can search your code components your salesforce instance:

1) Apex Classes

2) Apex Triggers

3) Visualforce Pages

4) Visualforce Components

Extension Link: https://bit.ly/2GL3eDM

3- Salesforce API Fieldnames

38,026 users

The extension shows the API field names on detail pages

Small extension to toggle between API field names and labels on salesforce detail pages.

Before:


Extension Link: https://bit.ly/2T6vx4z



4 - ORGanizer for Salesforce

20,862 users

The ORGanizer Chrome Extension (BETA) lets you forget about your Salesforce.com® username and passwords and help you to recognize Salesforce.com® tabs on your browser.

With Salesforce ORGanizer you can:

- Store your frequently used accounts (basic encryption for the password, details on the guide): username/password/ login URL / landing page

- Login an account on a new tab, window and window on incognito mode or get the full login URL for other browsers



- Change an ORG tab and title to instantly recognize which tab belongs to which ORG

- Use the built-in Quick Link tool to quickly access your most used standard Salesforce links

- Create your personal ORG's quick link library to handle special links

- Use the Quick Links tool to make a global search or open a custom relative link (e.g. from a copied Salesforce ID) or login to another ORG

- Use the Quick Console right inside your Salesforce tab to have quick.

Extension Link: https://bit.ly/2f0R2DZ

We would continue to showcase more extensions for #Salesforce in our Upcoming BlogPost/



Wednesday, 1 August 2018

[#Blogged] Apex Test Class Best Practices

You have to cover at least 75% but getting 100% must be the prime focus.
Never code to get the percentage cover.

  • All test methods should reside in a separate class from the class in which the method being tested resides.
  • These classes should be appended with the word Test followed by the name of the class being tested, e.g. OpportunityServicesTest.Some people use Test in front which is confusing and would consume more time while deploying/packaging.
  • These classes should all use the @isTest annotation.
  • Each method in the production class should have, at a minimum, one corresponding test method in its test class and should be appended by “test.”
  • There should be a minimum of “Null Pointer Exception test” as part of negative testing for each method, especially the methods that accept parameters.
  • A method without an assert statement is not considered a test method. A large number of relevant assert statements increases confidence in the correct behaviour of business logic.
  • There should be a comment with each assert statement explaining what is being tested and what the expected output is
  • Only use isTest(SeeAllData = true) on class methods in exceptional cases where there are sobjects that don't allow DML operation e.g. PriceBook creation.
  • System.runAs will not enforce user permission or field level permission.
  • All test data creation should be done from a Utility class. This allows for a streamlined creation of test objects that adhere to all the validation rules.
Resources :