Nathan, Tests may be not ideal, but they are as they are. I saw that there were empty lines between methods, fields, classes. Some of them were intentionally removed too though, in particular in field declarations and in anonymous classes, or some nested classes.
There is context preparation in some tests as well as context modification, which were separated with blank lines from assertions. (I guess some tests may be split into separate methods but some are not unfortunately.) And automatic formatting is not much better in some cases (whereas much of the code was manually formatted). Please, don't remove blank lines in test methods too. And thanks for doing this work of removing huge number of compiler warnings. Regards, Alexey. -- Alexey A. Ivanov Intel Enterprise Solutions Software Division >-----Original Message----- >From: Nathan Beyer [mailto:[EMAIL PROTECTED] >Sent: Tuesday, November 28, 2006 8:01 AM >To: [email protected] >Subject: Re: [testing] Swing tests clean up > >Sorry. I guess my formatting was over aggressive while eliminating the >compiler warnings. Note, not EVERY empty line was eliminated, just >those within methods. I actually added a number of lines between >methods, classes, etc. > >Personal, I didn't think that the tests are any less readable. I would >argue that if a test method needs to be separated visually, then the >method should be split up into multiple methods. > >-Nathan > >On 11/27/06, Ivanov, Alexey A <[EMAIL PROTECTED]> wrote: >> Nathan, >> >> >> >> Do you thing empty lines in tests are useless? Why have you removed >> every single empty line in tests? >> >> They were there on purpose! They separate parts of a unit test. I don't >> want them to be dropped! The code is unreadable without them. >> >> >> >> Thank you in advance, >> >> Alexey. >> >> >> >> -- >> Alexey A. Ivanov >> Intel Enterprise Solutions Software Division
