If you do incrementaled layers.
Like read mail and save it to db, so you write functions:
List lst = mailer.getNewMail(x);
dbxyz.saveMail(lst);
where you do you business work in one class (and you can tell its bus.
since you only import your packages, never other packages in bus. layer).
then 2nd layer you
implement those methods, import mail api and unit test very well, and
granualar.
Here unit testing improves your code.
So lets you get a bug in above.
That means your 2nd layer is not granualr enoug and unit tested.
So if you unit tests pass (or fails as sometimes you gibe it GIGA to
negative test)... and each methods is about 1/2 page and human
redable... how would you possibly write a bug?
It makes sense to me. It realy improves productivity to eliminate
(reduce) debuging IMO.
As opposed to doing this big class that does business and tech layer and
then you have non-readable code. Why put bugs in your code?
.V
Frank W. Zammetti wrote:
I don't see how they are comparable though...
Unit testing will tell you if there is a bug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
