Wikipedia

Software testing: Difference between revisions

Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Reverted 1 edit by Sify2024 (talk): Unsourced
m Reverted edit by Careerpedia11044 (talk) to last version by Amire80
 
(7 intermediate revisions by 7 users not shown)
Line 23:
== Economics ==
 
A study conducted by [[NIST]] in 2002 reportsreported that software bugs cost the U.S. economy $59.5 billion annually. More than a third of this cost could be avoided, if better software testing was performed.<ref>{{Cite web |date=May 2002 |title=The Economic Impacts of Inadequate Infrastructure for Software Testing |url=https://www.nist.gov/director/planning/upload/report02-3.pdf |access-date=December 19, 2017 |publisher=[[National Institute of Standards and Technology]]}}</ref>{{Dubious|NIST study| date = September 2014}}
 
[[Outsourcing]] software testing because of costs is very common, with China, the Philippines, and India being preferred destinations.{{cn|date=March 2024}}
Line 267:
Testing for [[internationalization and localization]] validates that the software can be used with different languages and geographic regions. The process of [[pseudolocalization]] is used to test the ability of an application to be translated to another language, and make it easier to identify when the localization process may introduce new bugs into the product.
 
Globalization testing verifies that the software is adapted for a new culture, (such as different currencies or time zones).<ref>{{Cite web |title=Globalization Step-by-Step: The World-Ready Approach to Testing. Microsoft Developer Network |url=https://msdn.microsoft.com/en-us/goglobal/bb688148 |access-date=January 13, 2012 |publisher=Microsoft Developer Network |archive-url=https://web.archive.org/web/20120623050851/https://msdn.microsoft.com/en-us/goglobal/bb688148 |archive-date=June 23, 2012}}</ref>
 
Actual translation to human languages must be tested, too. Possible localization and globalization failures include:
 
* Some messages may be untranslated.
* Software is often localized by translating a list of [[String (computer science)|strings]] out of context, and the translator may choose the wrong translation for an ambiguous source string.
* Technical terminology may become inconsistent, if the project is translated by several people without proper coordination or if the translator is imprudent.
* Literal word-for-word translations may sound inappropriate, artificial or too technical in the target language.
* Untranslated messages in the original language may be left [[Hard coding|hard coded]] in the source code, and thus untranslatable.
* Some messages may be created automatically at [[Run time (program lifecycle phase)|run time]] and the resulting string may be ungrammatical, functionally incorrect, misleading or confusing.
* Software may use a [[keyboard shortcut]] that has no function on the source language's [[keyboard layout]], but is used for typing characters in the layout of the target language.
* Software may lack support for the [[character encoding]] of the target language.
* Fonts and font sizes that are appropriate in the source language may be inappropriate in the target language; for example, [[CJK characters]] may become unreadable, if the font is too small.
* A string in the target language may be longer than the software can handle. This may make the string partly invisible to the user or cause the software to crash or malfunction.
* Software may lack proper support for reading or writing [[bi-directional text]].
Retrieved from "https://en.wikipedia.org/wiki/Software_testing"