Unit test accessing private variables

Question

I have a unit test class Tester; I want it to access private fields of a Working class.

class Working {
    // ...
    private:
            


        

Answer 1

I agree with Trott's answer, but sometimes you're adding unit tests to legacy code that wasn't designed for it. In those cases, I reach for #define private public. It's just in unit tests, and it's just for when refactoring is too expensive to bother. It's ugly, technically illegal, and very effective.