I like how you showed the process of refactoring in this series, but I wouldn't recommend multiple assertions in one controller.
See http://blog.jayfields.com/2007/06/testing-one-assertion-per-test.html
Yes, I agree. Multiple assertion is a bad practice since only the first assertion gets called if code changes alter behavior.
If God would exists it will be you... very thanks for this screencast.
If God would exists it will be you... very thanks for this screencast.
If God would exists it will be you... very thanks for this screencast.
It is a nice article,i appreciate it,i will keep it on my dashboad.
I just want to say the spirit is positive,but the content is simply.
Multiple assertion is a bad practice since only the first assertion gets called if code changes alter behavior.
I think this is a great post. One thing that I find the most helpful is number five. Sometimes when I write, I just let the flow of the words and information come out so much that I loose the purpose. It’s only after editing when I realize what I’ve done. There’s defiantly a lot of great tips here I’m going to try to be more aware of.






