QA and Testing

QA and Testing


• The product should be suitable for the intended purpose
• It should be right the first time delivered.

• Checking the quality of the source materials (diagnostic)
• Keeping the project on course through production
• Final check of products before delivery to clients

Does it match the English source? (images, format, animation, etc.)
• Layout – truncation issues; alignment
• Display – character corruptions

Is the application fully functional on a localized operating system?
Are hyperlinks functional?
• Fonts - whether it is bold, italicized, the correct size or type.
• Paragraphs - that a given page has the correct number of paragraphs when compared to the English source.
• Double quotes and Single quotes - each page of the target language uses the correct format of the double quotes and single quotes; be sure fonts look the same used on quotes.
• Header and Footer information - correctly translated, with the correct language identifiers.
• Start of a sentence - capitalized, indented, and following the correct formatting for the section (whether title, sub-title, or section heading).
• Tables and Figures - located in the right place, the right size, and match the original English; careful consideration is given to call-outs and captions, as it is easy to overlook these at the translation phase.
• Table of Contents (TOC) - that these should have the same number of entries as the English TOC.
• Glossary - it should be correctly ordered (generally, alphabetized in the target language).
• Translation - no missing items, or sections that are left in English
There are exceptions to this rule. When you encounter this, it is best to communicate immediately to the QA Coordinator.
• Layout - ensure that each page matches the English source file.
• Bullet points and Numbered items - each section with bullet points or numbered items should match the English source file; correctly indented with the correct number of items.
• Punctuation marks - generally language-specific rules should be followed.
However, if the client wants to follow the English, the application of punctuation needs to be consistent throughout.
• Truncation - refers to the cutting off of words due to graphic images extending beyond the established border or because images are overlapping the text.
• Widows and Orphans – double byte language.
• An orphan is a single word that’s either part of a paragraph or a series of points that is left on its own.
• A widow is a single line of a paragraph that appears on the bottom of a page, while the rest of the paragraph continues on the following page.
• Headings and Sub-headings - extra care is needed especially for languages that have a high expansion rate (like German and Russian); make sure the correct hyphenation is used to break long words.

1. Content Errors
• Accuracy, Cohesion, Locale suitability
2. Mechanical Errors
• Orthography, Grammar, Locale conventions
3. Compliance Errors
• Addition/Omission, Not translated, Style, Design

1. Accuracy
• Is it communicating the same message?
2. Cohesion
• Does each sentence flow together?
3. Locale suitability
• Would a person reading the target language be comfortable with the terminology, graphics, etc.?

• Additions/Omissions
• Has additional content been added that is not part of the source?
• Has content been omitted?
• Not translated
• Are there segments left in English that should be translated?
• Style
• Has it been written in the client’s preferred style?
• Such as informal or formal.
• Written for the target audience.
• Design
• Does is follow the instructions given by the client?

• Orthography
• Spelling
• Punctuation
• Capitalization
• Hyphenation
• Word breaks
• Grammar
• Is the sentence correctly constructed?
• Locale conventions
• Numbering
• Date
• Time

Word
• PowerPoint
• PDFs (generated from InDesign, Illustrator, QuarkXpress)
• Excel (occasionally)

• Onscreen text layout
• Graphics
• References/Tutorials accessed in the course
• Give specific instructions on what needs to be changed
• Avoid asking questions, state the change needed
• If something is unclear, ASK the QA coordinator for help