A Bug is a Bug in Every Language
Welocalize specializes in QA and Testing for software and technology. Recently, MultiLingual Magazine published the Welocalize Whitepaper Multilingual A Bug is a Bug In Any Language. The informative paper outlines the impact of software bugs and the considerations for languages and localization. Read the entire whitepaper for tips and advice on how to avoid bugs in the localization process.
Here are a few excerpts from the whitepaper or click here to read the complete whitepaper.
It only takes one bug to make a software application fail, in any language. According to research conducted by Cambridge University, software developers spend 50% of their programming time finding and fixing bugs. Bugs can be very expensive.
The same research found that the annual cost of fixing bugs is over $300 billion. Last year, a software bug in the securities order system of an Asian brokerage firm led to errant orders in the system valued at $3.8 billion. The incident was reputed to have caused losses totaling $32 million to the brokerage, which was also fined $90 million by Chinese regulators.
When any software product or update is released to the global market, it must be adapted to the linguistic, cultural, legal and technical requirements of each target locale. Bugs and defects cause programs to crash whether in the source or local language versions. Localization software testing evaluates and assesses the quality of the product – measuring given input against expected output.This process includes testing for bugs occurring during the localization phase and eliminating them before any global product launch.
Moving Software Localization & Testing Upstream
The best way to avoid bugs is to eliminate them before they arise. The process of localization should begin early in the development cycle. Using an upstream testing model, it is possible to eliminate many localization bugs (up to 80%) before any real investment in translation begins.
Localization of Mobile Apps
The localization of mobile applications presents a number of additional, unique challenges. Mobile platforms and devices present new areas for bugs to be introduced. Screen size, abbreviations and style guides are important considerations and can result in an influx of bugs.
Which Software Development Approach: Agile or Waterfall?
Many software developers and manufacturers are under increasing pressure to reduce the time-to-market and cost when introducing new products and features. Compressing software development cycles and accelerating new product launches are critical. To speed up the development process, many software developers are switching methodology from the traditional waterfall approach to an agile model. A key driver for implementing agile is to bring software products
and updates to market faster. Waterfall development follows a linear approach in terms of planning, budgets and timelines and can be rigid and inflexible.
Agile Development Requires Agile Localization
In many ways, agile forces the localization effort and the development effort to become meshed. It also changes the philosophy on how a quality deliverable is defined. Put simply, there is a window to test, a window to report and action bug fixes, and everything that falls outside this window joins a queue.
Welocalize Software Localization and Testing Services
Welocalize has a global testing team, based at two key locations, Jinan, China, and Portland, Oregon. Both testing laboratories have the relevant skills and expertise to perform user acceptance, functional and localization UI testing for a wide range of platforms and devices. 24/7 testing for operating systems, mobile devices and applications, browsers, web solutions, virtual, desktops and servers, e-learning and cloud-based solutions.
Read the entire whitepaper here Welocalize Whitepaper Multilingual A Bug is a Bug In Any Language.
If you would like additional information about Welocalize Software Localization and Testing Services, visit www.welocalize.com/quality-assurance-testing-services or contact us today at email@example.com.