Localization and Internationalization Testing

-

Localization Testing :


  • Localization testing is the software testing process for checking the localized version of a product for that particular culture or locale settings. The areas affected by localization testing are UI and content.
  • Localization testing is performed to verify the quality of a product's localization for a particular target culture/locale and is executed only on the localized version of the product.
  • It is a type of non-functional testing.
  • Whereas Localization is a process of adapting internationalized software for a specific region or language by adding local specific components and translating text.

Example: If the project is designed for Tamil Nadu State in India, The designed project should be in the Tamil language, Tamil virtual keyboard should be present, etc.

Internationalization Testing : 


  • Internationalization testing is the process of verifying the application under test to work uniformly across multiple regions and cultures.
  • Internationalization testing is to ensure that application can function in any culture or locale (language, territory and code page) It is also called as Globalization Testing. The main purpose of internationalization is to check if the code can handle all international support without breaking functionality that might cause data loss or data integrity issues. Globalization testing verifies if there is proper functioning of the product with any of the locale settings.
  • It is a type of non-functional testing.
  • Internationalization is a process of designing a software application so that it can be adapted to various languages and regions without any changes.

Example: In India, the Zip codes are 6 numeric digits (no alphabets). So, if you have selected your country like India then while entering the pin code of your area, it should only accept the 6-digit code. But, if your country is Canada, then the Zip codes include 6 alphanumeric characters.

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more