Hello automated testers,
i updated a lot of files below framework/extras in the last few days - possibly
about 1500 updates to CVS.
There were a lot of reasons to do this:
a) Each test used a unique way/naming scheme of storing the reference files
which was rather chaotic. Maintaining the list was a - well, an annoyance at best.
b) The files were not brand-aware (we have at least four brands now:
OpenOffice.org, BrOffice.org, StarOffice and StarSuite).
c) The file structure was not suited for versioning (which is a requirement in
case we move to another code line and want to keep compatibility).
d) It was suggested by the OOo community that we use ISO language codes instead
of telephone codes (meaning "en_US" instead of "01") which i implemented for the
newer files.
e) Many files were split up in small chunks (esp. the labels) which resulted in
countless files with names that did not even indicate their purpose.
f) Some of the "old" test cases did not have a proper description included
(meaning that the comments - when extracted from the files - did not give a
step-by-step description of what the tests do). This has been fixed as well.
If i did not miss anything we now should have one single consistent way
throughout the entire framework module to handle localized reference files.
In case someone wants to do automation or wants to learn how the mechanism is
implemented i can recommend studying the test case tLabelTypes() which can be
found in the file ".../framework/extras/inc/extras_labels.inc". For your
convenience i have extracted the documentation to this test case and put it
beside the .inc file as "extras_labels.html".
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
