Timeline for Method visibility for testing partial mocks
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2013 at 21:41 | comment | added | user40980 | Consider also asking codereview.SE about this with actual (rather than faked) code. For example Review of the testing code that I have written using easymock/junit | |
| Aug 22, 2013 at 21:38 | comment | added | dardo | Thinking there's reasons for both protected and default, just depending on how you're using the class! Thanks for the comment, rep Wisconsin! =) | |
| Aug 22, 2013 at 21:36 | vote | accept | dardo | ||
| Aug 22, 2013 at 21:34 | answer | added | ptyx | timeline score: 1 | |
| Aug 22, 2013 at 21:29 | comment | added | user40980 | That looks reasonable... and not bad. There's a standard refactoring in eclipse for making all variable access for the object through the getters / setters. I might go protected in case you ever subclass it and people won't fuss about it being without a modifier. | |
| Aug 22, 2013 at 20:39 | history | asked | dardo | CC BY-SA 3.0 |