This is not an issue with Mockito, but with plain old java. From where you are calling the method, you don’t have visibility. That is why it is a compile-time issue instead of a run-time issue. A couple options: declare your test in the same package as the mocked class change the visibilty of the … Read more
Yes you should write JavaDoc for private methods, and even when it is only for yourself. In 3 years when you have to change the code, you will be happy that you documented it. If you leave the company, or have to work on another project, your co-workers will be happy to have a documented … Read more
The definition of aggregate changed since C++17. Before C++17 no base classes Since C++17 no virtual, private, or protected (since C++17) base classes That means, for B and D, they’re not aggregate type before C++17, then for B{} and D{}, value-initialization will be performed, then the defaulted default constructor will be called; which is fine, … Read more
It is useful when you want to have access to some members of the base class, but without exposing them in your class interface. Private inheritance can also be seen as some kind of composition: the C++ faq-lite gives the following example to illustrate this statement class Engine { public: Engine(int numCylinders); void start(); // … Read more
Here’s the really simple example (with no error checking) of how to use ReflectionClass: function accessProtected($obj, $prop) { $reflection = new ReflectionClass($obj); $property = $reflection->getProperty($prop); $property->setAccessible(true); return $property->getValue($obj); } I know you said you were limited to 5.2, but that was 2 years ago, 5.5 is the oldest supported version and I’m hoping to help … Read more
I think everyone hammered the point of an interface having only public members, no implementation details. What you are looking for is an abstract class. public interface IOrange { OrangePeel Peel { get; } } public abstract class OrangeBase : IOrange { protected OrangeBase() {} protected abstract OrangePips Seeds { get; } public abstract OrangePeel … Read more
For models, the idea is that the public methods are the public interface of the class. Public methods are intended to be used by other objects, while protected/private methods are to be hidden from the outside. This is the same practice as in other object-oriented languages. For controllers and tests, just do as you please. … Read more
You can inherit the class you are testing on your test class. [TestClass] public class Test1 : SomeClass { [TestMethod] public void MyTest { Assert.AreEqual(1, ProtectedMethod()); } }
Yes, it’s almost the same. The protected modifier specifies that the member can only be accessed within its own package (as with package-private) and, in addition, by a subclass of its class in another package.
Python has no privacy model, there are no access modifiers like in C++, C# or Java. There are no truly ‘protected’ or ‘private’ attributes. Names with a leading double underscore and no trailing double underscore are mangled to protect them from clashes when inherited. Subclasses can define their own __private() method and these will not … Read more