Custom Test Issue and Understanding Grandparent Rollups

[rygramer]

Hey @jamessimone, sorry to bother you again. Moving this over to a discussion rather than an issue because it's entirely possible I'm missing the boat somewhere.

I'm having trouble understanding how to configure Grandparent Rollups: https://share.vidyard.com/watch/UudmSyaRa27C7dDQPWWC5z?

And I mentioned that I wanted to write some tests to better understand, but got hung up on the most basic test:

@isTest
public class RollupTest {
    @isTest
    public static void test1(){
    	Grandparent__c gp = new Grandparent__c(
            AmountfromChildren__c = 0
        );
        insert gp;
        
        Parent__c p = new Parent__c(
            Grandparent__c = gp.Id,
            AmountfromChildren__c = 0
        );
        insert p;
        
        Child__c c = new Child__c(
            Parent__c = p.Id
        );
        insert c;
        
        test.startTest();
        
        c.Amount__c = 5;
        update c;
        
        test.stopTest();
        
       // I would expect this to return 5.00, but it returns 0.00
        system.debug([SELECT AmountfromChildren__c FROM Parent__c LIMIT 1]);
    }
}

Log from that test -
apex-07L780000008vQ2EAI.log

[rygramer]

FWIW, I moved the logic from flow to triggers and it works perfectly.

I did find a slight error in my configuration - in Grandparent Relationship Field Path, I put Parent__r.Grandparent__r.AmountfromChildren__c, but it should have been Parent__r.GrandParent__r.AmountfromChildren__c (capital P in GrandParent). Capitalization is important.

The test still isn't working as expected.

[clint-rosetree]

I had this same issue and fought it for hours. Is this documented somewhere that I missed?

[jamessimone]

@clint-rosetree it's one of the first things mentioned in the README. For people writing unit tests against Apex Rollup, how do you think I can best document this feature? Should I have another section in the README?

[clint-rosetree]

Yeah, I followed the README for installation and everything worked live, but it just didn't cross my mind while later re-writing legacy test classes that the custom setting wouldn't be accessible. I've grown too accustomed to CMDT, I guess.

I would have definitely benefited from a simple section about writing test classes against the framework that just mentioned we have to include that one line in the @testsetup.

Thanks James!

[jamessimone]

Excellent feedback - I'll include that callout within the README in the next version. Thanks!

[jamessimone]

Here's the updated README - let me know if either of you have feedback. Thanks again for the nudge, I always appreciate guidance on improving the documentation (which I know is quite dense, already! 😅)