I generate a giant log that list the search plugin order for each
locale. I'm now writing a parser that goes through the log file to
ensure that the search links are
a - in the correct order
b - correctly formatted
The only doc that I've found to work off of is:
http://wiki.mozilla.org/Firefox2/L10n_Requirements#Search_Plugins
Since it is for Firefox2 I'm a little concerned that it may be getting
out of date. I want to ensure that I'm applying the correct rules to
the correct locale.
Is there a more up to date doc? Are the rules staying the same for now?
Thanks,
alice.
Hi Alice,
Mic is in charge of the rules. There are currently no planned changes,
though.
I have talked with Mic about this, too, as she's supposed to spec what
to test, and as you can tell from the quoted log on the wiki, what you
see is not what you GET.
6|eBay|http://search.ebay.com/foofoo_W0QQfrppZ50QQfsopZ1QQmaxrecordsreturnedZ300
is what those tests produce, if you look at
http://people.mozilla.com/~axel/status-1.8/, search tab, you'll see that
the URL that we're supposed to GET from ebay is a completely
different. Hover over the engines to get clickable search strings. They
grey boxens are original en-US plugins.
That's OK, as the server is allowed to redirect in general.
Not sure if you got pointed at my status page yet, those are source
based tests, as opposed to the run time test logs that you're looking
at. The may catch different bugs.
Axel
Just to clarify, you're saying that the logs that I'm auditing are
reporting the url after going through server re-directs? So it does not
reflect the link as it is found in the code?
This is fine, as you say it should catch different types of errors, but
I just want to be sure that I know what it is that I'll be tracking.
Once I get an example of the type of 'errors' I'm catching through my
script I'll post it and get people to look over it - see if I'm actually
finding anything that is of value. QA is interested in having this tool
up and running to help with l10n testing for FF3, so I'm trying to get
on it early so that I can have a history of test runs and results.
Thanks,
alice.