On Tue, Jan 04, 2011 at 04:19:53PM -0200, Cleber Rosa wrote: > On 01/04/2011 03:28 PM, Eric Li(李咏竹) wrote: > > +1 with John. > > > > Renaming autotest_lib to autotest will have a hugely impact to > > ChromeOS test automation project, since we need to go over through all > > test cases to change the import statement... > > > > Eric > > > > I guess we're all aware of the impact, but we should remember that this > would be, as Lucas said, mostly a mechanical change, very easy to > replicate on site specific tests. Again, no change in semantics, just > the module name. > > But that's me, who does *not* maintain site specific tests, saying that.
IMHO, it is OK to do it really carefully and slowly, and think twice before doing those changes, because of existing internal code. However, we must not hold forever from improving the Autotest code maintainability and readability because of existing site-specific code. Maybe the costs outweight the benefits right now, but I would love to see the possibility of improving these details of the API at some point in the future. -- Eduardo _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
