backporting minor UI changes to keep QA scripts working

Frédéric Buclin LpSolit at gmail.com
Wed Jan 18 21:51:10 UTC 2006


> 2) It's a slippery slope to go down.  Bugzilla is continually evolving,
> and this problem isn't going to go away.  The same problem will happen
> again with 2.24 because of UI changes.  Features are going to change,
> too.  Every version is going to break scripts that we used with the
> previous version...  How many branches do we continue to backport UI
> changes to?

I'm not talking about new features. I'm talking about typos of the form 
product -> Product. Selenium is case sensitive, so I have to write 
regexp of the form /(P|p)roduct/ in many places, and some Selenium 
commands do not accept regexp, so I would have to write |if (version == 
2.20) then "product" else "Product" end| in as many places. That's 
ridiculous for this kind of tiny UI changes (actually, I'm only 
complaining about the UI to admin products).

I wasted hours taking care as much as possible of this kind of typo 
changes (and having ugly scripts with regexp), but now I'm really tired 
of this.

LpSolit



More information about the developers mailing list