Best Practices for Writing Apex Test Classes with 100% Code Coverage

Deploying code to a Salesforce production org requires maintaining a minimum average test coverage of 75% across all Apex classes. While 75% is the threshold, the industry standard for critical data-parsing wrappers is **100% coverage**. In this guide, we walk through how to build robust, complete test coverage for your generated JSON Apex wrapper classes.

Why Test JSON Wrapper Classes?

Testing wrapper classes is essential to verify that your data deserialization behaves as expected under different circumstances, such as when processing empty payloads or unexpected parameter data types. Failing to assert these conditions leads to fragile, bug-prone API integrations.

Structure of a Generated Wrapper Test

A standard test class generated by **json2apex** validates the parsing logic. Below is a breakdown of the standard test pattern for a wrapper class named CustomerWrapper:

@isTest
private class CustomerWrapperTest {
    
    @isTest
    static void testParse() {
        // Setup a mock JSON string representing the service response
        String jsonMsg = '{"name": "John Doe", "email": "john@example.com"}';
        
        // Execute the parse method
        CustomerWrapper wrapperObj = CustomerWrapper.parse(jsonMsg);
        
        // Assertions to verify correct parsing
        System.assertNotEquals(null, wrapperObj, 'The parsed object should not be null');
        System.assertEquals('John Doe', wrapperObj.name, 'Names must match');
        System.assertEquals('john@example.com', wrapperObj.email, 'Emails must match');
    }
}

Mocking HTTP Callouts with Wrapper Classes

Salesforce tests cannot perform real HTTP requests. Instead, developers must mock the HTTP responses using the HttpCalloutMock interface. Wrapper classes make this process clean and straightforward because you can serialize your mock classes to generate the mock response bodies:

@isTest
public class CustomerCalloutMock implements HttpCalloutMock {
    public HTTPResponse respond(HTTPRequest req) {
        // Create mock instance using the wrapper class
        CustomerWrapper mockWrapper = new CustomerWrapper();
        mockWrapper.name = 'Mock User';
        mockWrapper.email = 'mock@example.com';
        
        HttpResponse res = new HttpResponse();
        res.setHeader('Content-Type', 'application/json');
        res.setBody(JSON.serialize(mockWrapper)); // Serialize directly
        res.setStatusCode(200);
        return res;
    }
}

Best Practices for Apex Unit Testing

1. Always Use Assertions

Do not write unit tests simply to satisfy the 75% coverage requirement. Ensure you write explicit System.assertEquals() or System.assertNotEquals() assertions to verify that data parsing operates correctly under all scenarios. Code that runs without assertions is called "test code smell" and does not validate business logic.

2. Test Edge Cases

Verify how your wrapper class handles empty strings, null values, or missing JSON parameters. A robust test class should ensure that the system handles these scenarios gracefully without raising unexpected runtime exceptions.

3. Maintain Separated Test Data

Do not hardcode massive JSON structures multiple times across different test methods. Store sample payloads in reusable static variables or dynamically construct objects using test data factory classes to keep your test code clean and maintainable.

Conclusion

Writing reliable unit test classes is as critical as writing the core integration code itself. By employing generated test wrappers, executing thorough assertions, and mocking HTTP callouts properly, you ensure your Salesforce org remains stable, scalable, and easy to deploy.