Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Sequoyah/localization checklist
< Sequoyah
Revision as of 14:35, 6 July 2010 by Unnamed Poltroon (Talk) (New page: '''Readme first''' * Since the Sequoyah provides a framework for the Localization Files Editor, you should implement an actual editor in order to test it. There is a reference implementat...)
Readme first
- Since the Sequoyah provides a framework for the Localization Files Editor, you should implement an actual editor in order to test it. There is a reference implementation for Android files that can be used to test most features apart from the automatic translation. If you want to also test the automatic translator you should implement a translator class (even if it is a stub one).
- When I do not say where to find a feature, it is probably on the “right click popup menu” of the table editor.
- It would be very very nice if you perform these tests on all supported operating systems.
- This is a guideline, created not to let the tester forget any feature. As a guideline it is simple and do not cover details. Please, use your creativity to make the testing more funny and efficient.
Pre requisites
- The editor is up and running, with all classes implemented.
- There is a project in the workspace.
- There are at least two localization files in the project.
Testing
Below you have a basic checklist that can be used as a guideline to test all Localization Files Editor features.
What to test
1. Open the Localization Files Editor via double clicking one of the files.
The editor should open and all files should be listed in the first page (table editor). Each file is also shown in individual pages.
2. Click on the columns headers.
The contents ordering should change accordingly.