Internationalization testing has been executed and any issues uncovered by this testing have been fixed. This means that the application (product) runs the same way on a locale OS as it does on the English OS, the data flow supports non ASCII character sets and text expansion has been considered during the design and implementation.
I would also argue that any l10n testing has an element of i18n/functionality testing since some screens don’t come up unless you test functionality. So the fact that a string displays correctly, i.e. without truncation or corruption, is i18n testing. Validating that it is the correct translation for the given context is l10n testing.
Create an automated test plan that embeds the manual test plan (test cases). Automate based on the test cases. Having such an automated test plan will provide the user the flexibility with the following choices:
Have an automated test plan that maps the test cases to automated scripts.
Provide the user with the flexibility to choose what test cases to run from the test plan.
Component two: Allow the user to create test cases DYNAMICALLY. In order to achieve that the test automation tool needs to provide a library. *** Library does not mean that the user needs to learn how to script.