function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Cloud AtlasCloud Atlas 

Test Class for a Small Trigger

Hello guys,

I have written the follwing trigger to sum two fields ..
The reason I couldn't use a WF / Process / Formula is due to the sheer size of the formula as the fields being added are themselves formula , which are also getting calculated from other fields..
So the total character size is getting exponential and its not working ..
Hence the trigger ... But the problem I am facing is that for such a small trigger , the test class is getting enornmous as the fields are formula and I cannot simply insert values to it..

Does any one know of an easier approach to writing a test class for this trigger ...
Both "Pageview Comp" and "Session Comp" are formula fields ...
trigger UpdateVariableFee on Monthly_Activity__c (before insert, before update) {
        if(trigger.isInsert || trigger.isUpdate){
            for(Monthly_Activity__c obj{       
                obj.Variable_Fee_Sum__c = obj.Pageview_Comp__c + obj.Session_Comp__c;
Any help is appreciated.
Please follow this code and do neccessary changes:
    private class testUpdateVariableFee {
    static testMethod void testBeforeInsert() {
        Monthly_Activity__c objMA = new Monthly_Activity__c();
        //objMA.Pageview_Comp__c=some value;
        //objMA.Session_Comp__c=some value;
        /* assign values to objMA mandatory fields */

        insert objMA;

        List<Monthly_Activity__c> result = [select Variable_Fee_Sum__c,Pageview_Comp__c, Session_Comp__c from Monthly_Activity__c limit 1 ];
        System.assertEquals(result.Variable_Fee_Sum__c ,(result[0].Variable_Fee_Sum__c.Pageview_Comp__c + result[0].Session_Comp__c);

Gulshan Raj
Amit Chaudhary 8Amit Chaudhary 8
Hi ,

I will recommend you to start using trailhead to learn about test classes

Also please check below post

You write a test class for this the same way that you would any other:

- Set up some data for the Trigger to access (in this case it looks like Monthly_Activity__c  )
- Instantiate the Trigger- by insert or update
- Execute a method/methods
- Verify the behaviour with asserts.

Please try below code in your code
private class UpdateVariableFee_Test 
	static testMethod void myUniteTest() 
        Monthly_Activity__c obj = new Monthly_Activity__c();
			//obj.Pageview_Comp__c='Test'; // Please add value according to data type
			//obj.Session_Comp__c='Test'; // Please add value according to data type
			// Add all required field
        insert obj;

        List<Monthly_Activity__c> result = [select Variable_Fee_Sum__c,Pageview_Comp__c, Session_Comp__c 
											from Monthly_Activity__c 
											where id 
        System.assertEquals(result.Variable_Fee_Sum__c ,(result[0].Pageview_Comp__c + result[0].Session_Comp__c) );

Please follow below salesforce Best Practice for Test Classes :-

1. Test class must start with @isTest annotation if class class version is more than 25
2. Test environment support @testVisible , @testSetUp as well
3. Unit test is to test particular piece of code working properly or not .
4. Unit test method takes no argument ,commit no data to database ,send no email ,flagged with testMethod keyword .
5. To deploy to production at-least 75% code coverage is required
6. System.debug statement are not counted as a part of apex code limit.
7. Test method and test classes are not counted as a part of code limit
9. We should not focus on the  percentage of code coverage ,we should make sure that every use case should covered including positive, negative,bulk and single record .
Single Action -To verify that the the single record produces the correct an expected result .
Bulk action -Any apex record trigger ,class or extension must be invoked for 1-200 records .
Positive behavior : Test every expected behavior occurs through every expected permutation , i,e user filled out every correctly data and not go past the limit .
Negative Testcase :-Not to add future date , Not to specify negative amount.
Restricted User :-Test whether a user with restricted access used in your code .
10. Test class should be annotated with @isTest .
11 . @isTest annotation with test method  is equivalent to testMethod keyword .
12. Test method should static and no void return type .
13. Test class and method default access is private ,no matter to add access specifier .
14. classes with @isTest annotation can't be a interface or enum .
15. Test method code can't be invoked by non test request .
16. Stating with salesforce API 28.0 test method can not reside inside non test classes .
17. @Testvisible annotation to make visible private methods inside test classes.
18. Test method can not be used to test web-service call out . Please use call out mock .
19. You can't  send email from test method.
20.User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage we can access without (seeAllData=true) .
21. SeeAllData=true will not work for API 23 version eailer .
22. Accessing static resource test records in test class e,g List<Account> accList=Test.loadData(Account,SobjectType,'ResourceName').
23. Create TestFactory class with @isTest annotation to exclude from organization code size limit .
24. @testSetup to create test records once in a method  and use in every test method in the test class .
25. We can run unit test by using Salesforce Standard UI, IDE ,Console ,API.
26. Maximum number of test classes run per 24 hour of period is  not grater of 500 or 10 multiplication of test classes of your organization.
27. As apex runs in system mode so the permission and record sharing are not taken into account . So we need to use system.runAs to enforce record sharing .
28. System.runAs will not enforce user permission or field level permission .
29. Every test to runAs count against the total number of DML issued in the process .

Please let us know if this post will help you
Cloud AtlasCloud Atlas
Hey Gulshan and Amit ,
Thanks for the response... But you both missed the essence of my query ..
I had already tried a similar trigger on my own..
But even you both are missing the point that you cannot insert values into "FORMULA" fields..

//obj.Pageview_Comp__c='Test'; // Please add value according to data type
//obj.Session_Comp__c='Test'; // Please add value according to data type

So I wanted to find out if anything could be done to bypass writing all related objects/fields to get the values in Pageview_Comp__c and Session_Comp__c..
These 2 fields get their values from two seperate formula , which captures its value from another object... and those fields capture values from a third object ..
That is why I had to go for a trigger instead of a simple formula field.

Thanks for pointing out about formula field, I missed that part.

I would suggest to generate data using test setup method  of all formula related object first. This will populate some value inside your formula field. Then you can use system.assert to compare value.

Please follow trailhead to learn how create test class:

and about test setup

This will help you.

Gulshan Raj