|
i was once involved in a project where somebody was obsessed with unit testing, but got it horribly wrong. according to them, unit testing was vital, but it meant that the entire project had to be based on mvc, because otherwise unit testing couldn't be done. all the code followed the mvc model, down to the lowest level it could. there wasn't just one model, one view, and one controller. every component of everything had a model, a view, and a controller, each in its own source file. imagine, if you will, a button on the screen. each component of that button and everything to do with that button had its own model, view, and controller. almost the worst poo poo that i have ever seen. i was asked to take a look at the code because i know a bit about flash/flex and they had performance problems. my professional opinion was: "lol"
|
#
¿
Aug 3, 2014 13:34
|
|
|
|
| # ¿ Apr 27, 2024 02:33 |
|
|
all types of automated testing loving own
|
|
#
¿
Aug 3, 2014 13:36
|
|