如何解决Salesforce Apex测试类无法覆盖全部代码的问题？

Hey there! Let's walk through exactly how to get 100% test coverage for your myclass Apex controller. The key here is replicating the runtime context your controller expects—including page parameters and test data for your custom objects.

Step 1: Create Test Data for Your Custom Objects #

First, you need to insert valid test records for CustomObject1 and CustomObject2 since your controller runs SOQL queries against them. Make sure to populate any required fields and set up the relationship between them (I’m assuming your truncated SOQL for listvar filters CustomObject1 records related to the CustomObject2 from the page parameter).

@isTest
private class myclassTest {
    static testMethod void testMyClassConstructor() {
        // Insert a CustomObject2 record first
        CustomObject2 testObj2 = new CustomObject2(
            Field1__c = 'Test Value' // Populate all required fields here
        );
        insert testObj2;

        // Insert related CustomObject1 records that match your controller's SOQL filter
        List<CustomObject1> testObj1List = new List<CustomObject1>();
        testObj1List.add(new CustomObject1(
            Name = 'Test Record 1',
            Field1__c = 'Sample Data 1',
            Field2__c = 'Sample Data 2',
            Field3__c = 'Sample Data 3',
            Field4__c = 'Sample Data 4',
            Field5__c = 'Sample Data 5',
            // Replace with your actual lookup/master-detail field linking to CustomObject2
            Related_CustomObject2__c = testObj2.Id
        ));
        insert testObj1List;

Step 2: Simulate the Page Parameter Context #

Your controller pulls the id parameter from the current page, so you need to set that in your test class using ApexPages.currentPage().getParameters(). Then create a StandardController instance and initialize your myclass.

// Set the page parameter to our test CustomObject2's Id
        ApexPages.currentPage().getParameters().put('id', testObj2.Id);

        // Create the StandardController and initialize your controller class
        ApexPages.StandardController sc = new ApexPages.StandardController(testObj2);
        myclass controller = new myclass(sc);

Step 3: Verify Logic & Ensure Coverage #

Add assertions to confirm that your listvar was populated correctly. This validates your controller’s logic and ensures the SOQL query and assignment code is executed (and thus covered).

// Assert that listvar is not null and contains the expected records
        System.assertNotEquals(null, controller.listvar, 'listvar should be populated with records');
        System.assertEquals(1, controller.listvar.size(), 'listvar should contain our test CustomObject1 record');

        // Optional: Verify specific field values match your test data
        System.assertEquals('Test Record 1', controller.listvar[0].Name);
        System.assertEquals('Sample Data 1', controller.listvar[0].Field1__c);
    }
}

Key Tips for Full Coverage #

• Stick to test-only data: Never rely on existing org data (Salesforce defaults to SeeAllData=false for tests, which is best practice).
• Replicate all runtime dependencies: Your controller depends on the page id parameter—without setting it, the first SOQL query would fail or return null, leaving that code uncovered.
• Assert every critical path: Assertions don’t just validate functionality—they guarantee that the code paths you want to cover are actually executed. If you skip them, you might miss edge cases where code isn’t running as expected.

If your truncated SOQL for listvar has additional filters (like specific field values), adjust your test CustomObject1 records to match those filters so the query returns them. That way, every line of your controller’s constructor (including both SOQL assignments) will be executed and covered.

内容的提问来源于stack exchange，提问作者Erik