如何在Java中访问私有类成员？

Question

I have data model classes that contain private fields which are meant to be read-only (via a getter function). These fields are set by my JPA persistence provider (eclipselink) during normal operation, using the contents of the database. For unit tests, I want to set them to fake values from a mockup of the persistence layer. How can I do that? How does eclipselink set these values, anyway?

Simplified example:

@Entity
class MyEntity
{
    @Id
    private Integer _ix;

    public Integer ixGet()
    {
        return this._ix;
    }
}

Answer 1

Can you just Mock the Entity itself, providing your own implemenations of the getters?

You could create an anonymous extension in your mock persistence layer:

MyEntity x = new MyEntity() {
    public Integer ixGet() { return new Integer(88); }
};

Answer 2

You need to use the Reflection API. Use Class.getField() to get the field, then call setAccessable(true) on that field so that you may write to it, even though it is private, and finally you may call set() on it to write a new value.

For example:

public class A {
    private int i;
}

You want to set the field 'i' to 3, even though it is private:

void forceSetInt(Object o, String fieldName, int value) {
    Class<?> clazz = o.getClass();
    Field field = clazz.getDeclaredField(fieldName);
    field.setAccessible(true);
    field.set(o, value);
}

There are a number of exceptions that you will need to handle.

Answer 3

You can use a test library like Mockito to access objects internal state in read and write mode. For example with Mockito use:

//read
Integer i = Whitebox.getInternalState(myEntity,"_ix")
//Write 
Whitebox.setInternalState(myEntity,"_ix", 123) 

Answer 4

You can use a mocking framework like powermock to by pass encapsulation. In powermock you'd use Whitebox.setInternalState(..) to set a private member.

A less invasive method would be to mock the getter method. Whether this is feasible would depend on what else depends on the internal state but if it is enough, it's the cleaner solution.

Answer 5

Some methods I've used in the past:

• Make _ix protected, create a subclass where you implement a setter
• Make a constructor taking the value for _ix as a parameter
• Use reflection

Answer 6

Another option, if you really hate to make things public, is to create a subclass for testing, and provide public access there.

You have a few options:

• Create stubs to replace your entity (extract an interface first)
• Use Reflection
• Add a public setter for testing
• Keep your tests within the package and use a default scope

For a bunch of useful techniques, have a look at Michael Feather's book, Working Effectively With Legacy Code

Answer 7

You can add constructor with parameter for your read-only variable. Don't forget to add a default (zero parameter) constructor.

@Entity
class MyEntity
{
    @Id
    private Integer _ix;

    public MyEntity(Integer ix) {
        _ix = ix;
    }

    public MyEntity() {
        /*
         * Default constructor
         */
    }

    public Integer ixGet()
    {
        return this._ix;
    }
}

Answer 8

The constructor is a best way I think. If this entity has to be really readonly (not allowed to create new instances in production code at all) you can make constructor with package access and use it only within the tests. And there is a possibility that even if you make your default constructor private or with package access, your persistance provider still be able to work with such entity, but not sure though - check with eclipselink docs.