@TestVisible Annotation in Apex

In Salesforce, the @TestVisible annotation makes private or protected variables and methods visible in test classes. This annotation allows you to access and manipulate these elements for testing purposes without changing their access modifiers, thereby maintaining encapsulation and security in production code while enabling thorough testing.

Here is an example 

public class MyClass {
    // Private member variable
    @TestVisible private Integer myPrivateVariable = 09;

}

@isTest
 private class TestVisibleClassTest {
    @isTest static void testExample() {
        // Access private variable annotated with TestVisible
        Integer i = MyClass. myPrivateVariable;
        System.assertEquals(09, i);

    }

 }

Here are the key points about the @TestVisible annotation:

Visibility: @TestVisible makes private or protected variables, properties, and methods visible in test classes, allowing you to access them directly in test methods.

Encapsulation: Salesforce enforces encapsulation by default by restricting access to private and protected members of a class. However, @TestVisible relaxes this restriction specifically for test classes, enabling comprehensive testing without compromising code integrity.

Usage: You can apply the @TestVisible annotation to variables, properties, or methods you want to expose for testing. It's often used with the @isTest annotation to define test methods and classes.

Limitations: While @TestVisible provides flexibility for testing, it's essential to use it judiciously. Exposing too many internal elements can lead to test code dependency on implementation details, making future code changes more challenging.

Security Considerations: Although @TestVisible allows access to private and protected members in test classes, it doesn't affect the security or visibility of these members in the production code. They remain private or protected as intended, ensuring data integrity and security.

Best Practices:

Use @TestVisible sparingly and only when necessary for testing purposes.

Document the rationale for exposing members with @TestVisible to maintain clarity and understanding for future developers.

Avoid exposing sensitive data or critical business logic with @TestVisible to prevent unintended access or manipulation in test classes.