Apache OpenOffice (AOO) Bugzilla – Issue 53051
Define a reduced set of test cases for localized builds
Last modified: 2006-08-07 18:42:56 UTC
For approval of the localized builds of 1.1.5rc3 (and maybe further releases). Given the fact, that many of the current test cases are about basic functionality, that is already covered by automated testing or tests on the english build, we can reduce the amount of work for the native lang teams. Native lang testers could help to test basic functionality, so we might even improove overall teting. This would work for minour releases and only if: - automated tests are run on the english (basic) release - full suite of test cases is done for english release (to enshure functionality) Basic Ideas for the test cases: - do some automated tests for all localized builds framework/first/first.bas framework/first/topten.bas writer/update/w_updt.bas calc/update/c_updt.bas graphics/update/i_updt.bas graphics/update/d_updt.bas - take the smoketests as base for manuel testing, but: * leave out most of the file type tests (covered automated testing) * include filetype tests for files with localized contend (native lang characters, date formats, number formats) for basic docuent types (text, spreadsheet, presentation in OOo, OpenDocument and MS file formt) * leave out most of the file actions tests (covered by automated tests) * leave out insert actions tests (covered by automated tests) * leave out some edit actions * leave out view action * keep only some of the format, tools/options and help tests - collect feedback about the tests done This would reduce number of tests from 140 to about 40. I'll attach a first draft of a checklist (I have only removed some testcesase, but didn't add new, that might be needed) Feel free to comment here or at the list
Created attachment 28580 [details] first draft .. by far not comlete
Andre, I looked at the spreadsheet listing all the smoketests. Its very nice, good presentation. As an aside, it gave me some ideas for looking up information on how documents are displayed on the screen. As always, thank you.
* include filetype tests for files with localized content (native lang characters, date formats, number formats) for basic document types (text, spreadsheet, presentation in OOo, OpenDocument and MS file format): To complement the above, the following tests may need to be added for CJK including Japanese: 1. Vertical written documents 2. Export vertical written documents to PDF And we have the following function which we would be better off testing: 3. Export to Flash And we find the following test in TCM, which we should test: 4. Password setting in native languages.
adding me in cc - Sophie
Proposal for Base smoke tests. This is a set of 17 smoke tests designed by Tony Galmiche. I'll translate them (when I find the time :) and will add them here during this week. 1. Create and save a Base file . select File / New /Database menu . select Create a new database radio button . click on the Next button . click on the Finish button . give a File name (add special characters for your language) and click on the Save button . select File / Close menu . select File / Open et open the previous saved file The file should open without displaying any error message. 2. Create a new table . open the previous created Base file . select the Tables tab . click on the task Create Table in Design View... . Add 3 Field Name containing special characters in your language and 3 different Field Type . right click on the grey square at the left of the first field to add a Primary Key . select File / Save menu and give a name containing special caracters in your language . select File / Close and re-open the file . right click on the previous created Table and select Modify in the contextual menu No message error should appear and the Field Names should display correctly More to come later ;) Kind regards - Sophie
Smoke tests for Base : following 3. Adding datas into a table . open the previous created Base file . select the Tables tab . double clic on the previous created table . add several records using special caracters in your language . add an already existing record, validate the error message and modify the record or hint the Escap key, . close and reopen the file Open the table and check that you can still access the datas. There should be no error. 4. Modifying a table . open the previous created Base file . select the Tables tab . right click on the previous created table and choose Edit . modify a Field type, save and close the table (usually, a Char field type can't be change in Numeric field type without loosing the datas) . close and reopen the file Open the table and check that the datas can still be accessed and that no errors are shown. 5. Create a view . open the previous created Base file . select the Tables tab . click on the Task : Create a View... . select the previous created table and click on the Add button and then on the Close button . double click on the field * to add all the field in the view . select File / Save and give a name to the view using special caracters present in your language. . close and reopen the file Open the pevious created View and check that all the datas are still here. 6. Rename a Base file . using your file manager, rename (using special characters in your language) and move the previous created Base file in another directory. The OOoBase file should open without displaying any error messages, and the table can be accessed. 7. Create an index . open the previously created Base file . select the Tables tab . right click on the table and choose Edit . under Tools menu, choose Index Design... . click on the left icon New Index . give an index name using special caracters in your language . in the Index Field area, select a table field . select a Sort Order . click on the Save Current Index icon . click on the Close button . select File / Close to close the edition mode . close the database No error messages should display 8. Create the CD-Collections sample table . open the previous created Base file . click on the Tables tab . click on the task Use Wizard to Create Table . select the Personal Category . select the Collection-CD in Sample tables . click on the >> button to add all available fields . click on the Finish button . select File / Close menu entry to close the table without adding datas . Close the database No error messages should display more to come later :)
Base smoke test : following 9. Create the Categories sample with the wizard Note : it's important to exactly follow the process in order to be able to proceed the next tests . open the previously created Base file . select the Tables tab . click on the task Use Wizard to Create Table... . select the Personal Category . select the Sample Table "Categories" . click on the >> button to add all the fields . click on Next button to jump on step 2 . click on Next button to jump on step 3 . select Use an existing field as primary key . in the Fieldname, select CategoryID in the listbox . click on the Finish button . select File / Close to close the table without adding datas . Close the database file No error message should display 10. Create Relationships between the two new tables . open the Base file previously created . select the Tables tab . select the Tools / Relationships menu entry . select the Categories table and click on the Add button . select the CD-Collection table and click on the Add button . click on the Close button . drag the "CategoryID" field on the "MusicCategoryID" field . a 1 to n relation line should display between the 2 fields . double click on the relation line to display the Relations dialog . select Update cascade in the Update options and Delete cascade in the Delete options . click on the OK button . select File / Save menu entry . select File / Close menu entry . close the database file No error message should display 11. Add datas in the linked tables . open the previously created Base file . select the Tables tab . double click on the Categories table . add records and close the table . double click on the CD-Collection table . add records, . check that it's not possible to add a record in the MusicCategoryID field that has not been created in the Categories table . close the table . double click on the Categories table, modify and delete categories used in the CD-Collection table, . close the table . double click on the CD-Collection table and check that the categories have been modified and that the deleted lines are deleted too . close the table . close the database file No error message should display more to come later :)
Thanks Sophie :) I am translating these "Proposal for Base smoke tests" into Japanese.
Created attachment 32820 [details] Tempalte for test case description (first draft)
closing as worksforme - TCM scenario "Release Sanity" can be used for that. a first set of tests exists and cen be improved
closed