Hi Satya, Mark as best answer, If it resloves !! Follow the CamelCase Java conventions, except for VF pages and components start with a lower case letter. Triggers:
<ObjectName>Trigger - The trigger itself. One per object.
<ObjectName>TriggerHandler - Class that handles all functionality of the trigger
<ObjectName>TriggerTest
Controllers:
<ClassName>Controller
<ClassName>ControllerExt
<ClassName>ControllerTest
<ClassName>ControllerExtTest
Classes:
<ClassName>
<ClassName>Test (These might be Util classes or Service classes or something else).
Visualforce pages and components:
<ControllerClassName>[optionalDescription] (without the suffix Controller). There might be multiple views so could also have an extra description suffix.
Object Names and custom Fields
Upper_Case_With_Underscores
Variables/properties/methods in Apex
camelCaseLikeJava - more easily differentiated from fields Test methods in test classes
test<methodOrFunctionalityUnderTest><ShortTestCaseDesc> - For example, testSaveOpportunityRequiredFieldsMissing, testSaveOpportunityRequiredFieldsPresent, etc.
Mark as best answer, If it resloves !!
Follow the CamelCase Java conventions, except for VF pages and components start with a lower case letter.
Triggers:
- <ObjectName>Trigger - The trigger itself. One per object.
- <ObjectName>TriggerHandler - Class that handles all functionality of the trigger
- <ObjectName>TriggerTest
Controllers:- <ClassName>Controller
- <ClassName>ControllerExt
- <ClassName>ControllerTest
- <ClassName>ControllerExtTest
Classes:- <ClassName>
- <ClassName>Test (These might be Util classes or Service classes or something else).
Visualforce pages and components:- <ControllerClassName>[optionalDescription] (without the suffix Controller). There might be multiple views so could also have an extra description suffix.
Object Names and custom FieldscamelCaseLikeJava - more easily differentiated from fields
Test methods in test classes
- test<methodOrFunctionalityUnderTest><ShortTestCaseDesc> - For example, testSaveOpportunityRequiredFieldsMissing, testSaveOpportunityRequiredFieldsPresent, etc.
check these stack exachnge converstion for more infohttps://salesforce.stackexchange.com/questions/890/what-is-a-good-set-of-naming-conventions-to-use-when-developing-on-the-force-com
check GitHub Repo
https://github.com/cfpb/salesforce-docs/blob/master/_pages/Salesforce-Naming-Conventions.md
Mark as resloved if it helps :) :)
Thanks,
Bhanu Prakash
visit ForceLearn.com