Timeline for Where we should put validation for domain model
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2015 at 19:17 | review | Late answers | |||
| Sep 30, 2015 at 5:17 | |||||
| Mar 4, 2015 at 21:49 | comment | added | P. Roe | Many times objects only appear difficult to construct. For instance in this case you could bypass the public constructor by creating a Wrapper class that inherits from the class being tested and allows you to create an instance of the base object in an invalid state. This is where using the correct access modifiers on classes and constructors comes into play and can really be detrimental to testing if used improperly. Additionally avoiding "sealed" classes and method except where appropriate will go a long way to making a code easier to test. | |
| Feb 21, 2014 at 21:24 | history | answered | Paul | CC BY-SA 3.0 |