testing products for global readiness

36
SDL Proprietary and Confidential SDL Customer Success Summit Testing Products for Global Readiness Herb Bauer, Testing Manager, September 19, 2013

Upload: sdl-language-solutions

Post on 04-Dec-2014

838 views

Category:

Technology


0 download

DESCRIPTION

 

TRANSCRIPT

  • 1. SDL Proprietary and Confidential SDL Customer Success Summit Testing Products for Global Readiness Herb Bauer, Testing Manager, September 19, 2013
  • 2. Testing is important, but bug prevention is even better! Do runtime testing, but minimize its impact! Two simple QA methods before testing, reduce costs and speed up the process Testing and QA
  • 3. Insufficient QA means painful testing! Thank you YouTube! 3
  • 4. Impact of bad QA and lack of testing 4
  • 5. Lost time and money 5 $60,000,000
  • 6. Lost market share 6 Priceless
  • 7. The need for run-time testing
  • 8. Lets do run-time testing spot the bugs! 8
  • 9. Thumbs-Up and Russian plurality issue 9 Icons are missing, of course One year, two years. five summers, six summers! Thumbs-up may be problematic in certain countries
  • 10. You will need to do run-time testing 10 Label width and textbox width are the same: Why is the clipping not identical? Why not prevent clipping in the first place?
  • 11. Heres a pretty easy bug to spot 11
  • 12. Missing translations happen very often 12
  • 13. Character / font display issues 13
  • 14. This one would be hard to spot, admittedly 14
  • 15. Looks like mighty fine Chinese to me 15 , , . VR STR8-FIT , , , . VR STR8-FIT Heres how it should have looked (missing characters in red; punctuation corrected)
  • 16. Again, you will need to test to see this 16 Bad hyphenation, abbreviations, line breaks Strings are shared between narrow and wide version of a product and stored in TM after fixes are applied Solutions Test the software using various display sizes or screen resolutions Provide maximum string length and maximum line number specs to translators. Dont store every fix in the TM.
  • 17. Start with QA & Bug Prevention
  • 18. Planning Development Localization Testing 0 10 20 30 40 50 60 Time to software release The testing tail is wagging the development dog 18
  • 19. Of all 667 bugs analyzed, how many could have been probably prevented? 506 bugs Time for bug logging, fixing, creating new builds for these bugs (at a minimum)? 500 hours Time to prevent these bugs through pseudo- localization and string table review? 110 hours Cost savings of preventing these 506 bugs (at a minimum)? $23,000 Time savings not having to fix so many bugs and missing market release deadlines? Priceless ROI of bug prevention recent analysis 19
  • 20. Can we prevent the usual suspects? 20
  • 21. Multi-lingual translation table Multi-genius 21 Quickly find and highlight: Completely missing translations (blank cells) Un-translated text (still in English) Text that is much longer than English likely to cause clipping Inconsistent translations within a single language Inconsistent translations across languages Completely misaligned translations compared to the English Font display problems, corrupted characters
  • 22. Multi-lingual translation table heat map 22
  • 23. Pseudo-localization can stop many issues 23
  • 24. Pseudo-localization can stop many issues 24
  • 25. The pseudo-localization process is fairly easy .. 25 Client sends strings to get translated SDL creates simulated translations SDL / client creates test scenarios Client creates pseudo-localized build SDL reports internationalization issues
  • 26. SDL Passolo for pseudo-localization 26 Customize expansion $$ used as pre/suffix Pick special characters Custom features
  • 27. Functional localization issues found 27 Date format wrong date should not be translated and the function should call the system clock instead Code was exposed to over-translation
  • 28. Clipping alert; Japanese fonts is OK! 28 Lots of potential clipping issues detected Potential clipping, but Japanese font is OK
  • 29. Un-translated strings alert no $$ signs! 29
  • 30. Too much expansion, but Cyrillic is OK! 30 Potential text expansion problem perhaps redesign graphics? Cyrillic font checks OK.
  • 31. The cost of not testing your software can be very high There is no good substitute yet for live run-time testing The key to make testing manageable is early QA Pseudo-localization is one effective QA method Scheduling the review of a multi-lingual translation table is one of the quickest and cheapest way to avoid bugs Take away 31
  • 32. Appendix The Russian plurality issues
  • 33. If the number is 1, or the number ends in the word '' (example: 1, 21, 61) (but not 11), then you should use the case (singular) that is suitable for the position in the sentence. The number one declines like an adjective. Here are some examples. 1, 21, 61 , (1, 21, 61 year) 1, 21, 61 (1, 21, 61 month) 1, 21, 61 (1, 21, 61 week) 1, 21, 61 (1, 21, 61 day) 11 (11 years) 11 (11 months) 11 (11 weeks) 11 (11 days) Numbers ending in: 1 33
  • 34. If the number, or the last digit of the number is 2, 3 or 4, (example: 22, 42, 103, 4) (but not 12, 13 & 14), then you should use the genitive singular case.. Here are some examples. 2, 3, 4, 22, 42, 103, - 2, 3, 4, 22, 42, 103, year 2, 3, 4, 22, 42, 103, - 2, 3, 4, 22, 42, 103, months 2, 3, 4, 22, 42, 103, - 2, 3, 4, 22, 42, 103, weeks 2, 3, 4, 22, 42, 103, - 2, 3, 4, 22, 42, 103, days 12, 13, 14,15,16,17,18,19,20 12, 13, 14,15,16,17,18,19,20 years. 12, 13, 14,15,16,17,18,19,20 12, 13, 14,15,16,17,18,19,20 months 12, 13, 14,15,16,17,18,19,20 12, 13, 14,15,16,17,18,19,20 weeks 12, 13, 14,15,16,17,18,19,20 12, 13, 14,15,16,17,18,19,20 days Numbers ending in: 2, 3, 4 34
  • 35. If the number ends in any other digit you should use the genitive plural. All the 'teens' (-) fit in to this catagory (11, 12, 13, 14, etc) And that is by no means all that can be said to that subject! Numbers ending in: 5,6,7,8,9,0, - 35
  • 36. Copyright 2008-2013 SDL plc. All rights reserved. All company names, brand names, trademarks, service marks, images and logos are the property of their respective owners. This presentation and its content are SDL confidential unless otherwise specified, and may not be copied, used or distributed except as authorised by SDL.