|
| Nice
post
Zan.
I
wen
|
|
 |
|
 |
Nice post Zan. I went down this same path when I started worinkg with Grails several years ago. I felt better for using a similar testing approach, but I found that (re-)reading the unit tests when I revisited them was a much slower activity then reading actual prose (i.e. first name is nullable'). Since the tests were harder for me to read, it was also more difficult for me to refactor both my tests and application when the need came about.In order to eliminate/reduce the testing boiler plate and to make reading tests easier (i.e. something a non developer can read), I ended up creating the Grails Domain Expectations Plugin :Oddly enough, both the examples you and I use involve a Person class Please take a look and send me your thoughts. Since you have thought about constraints a fair bit, I'm really looking forward to any feedback that you can provide.
|
 |
|
 |
|
|
|
|
|
|
(VISITOR) AUTHOR'S NAME
Erlin
MESSAGE TIMESTAMP
16 december 2014, 12:35:04
AUTHOR'S IP LOGGED
117.169.1.86
|
|
|
|
