----- Original Message ----- From: "David Graham" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 12, 2003 12:45 PM Subject: Re: New Tests
> While testing in a real jsp makes a kind of sense it may not be the best > solution. > > 1. The build will take a lot longer which really hurts productivity when > testing changes. Not exactly, 'running' the tests is the only thing that will take longer. Building will actually be quicker with approach #2, because there's less code to compile. Also, since I'm writing these from scratch (not changing anything that exists), either technique will increase test time. > 2. The jsp test is now dependent on other Struts tags' behavior. What if > one those tags is broken? The goal of testing is to isolate the most basic > usage which your first example does. I thought that was the purpose of tests. If doing it this way, we can identify bugs that might not have been caught before, that should be a good thing. I would think that our latest nested bug(s) would have been caught if such tests existed. I'm not sure if approach #1 would catch that. > > Dave -- James Mitchell --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
