Globalization Testing

Globalization Testing ensures the application can function in any culture/locale. The goal of globalization testing is to detect potential problems in application design that could inhibit globalization. It makes sure that the code can handle all international support without breaking functionality that would cause either data loss or display problems. The following must be part of your globalization-testing plan:

1.) Decide the priority of each component :

To make globalization testing more effective, assign a testing priority to all tested components. Components that should receive top priority:

* Support text data in the ANSI (American National Standards Institute)format.

* Extensively handle strings (for example, components with many edit controls).

* Use files for data storage or data exchange (e.g., *Windows metafiles, security configuration tools, and Web-based tools).

2.) Select a test platform,

3.) Create the test environment,

4.) Execute tests,

5.) Recognize the problems.

LIFE begins when we loose,

LIFE ends when we win,

So, make sure that you always win.

-------AMAR DEEP MARADANA

Localization testing

Localization : is a service that are acceptable for a particular culture or locale that makes users to accept the adaptable software. For example MS OFFICE is used in many languages as a packagable software, as i use the software in english and others may use in Japanese or Hindi etc.

Localization testing checks how well the build has been translated into a particular target language. This test is based on the results of globalized testing where the functional support for that particular locale has already been verified. If the product is not globalized enough to support a given language, you probably will not try to localize it into that language in the first place!

Bug Tracking System

Bug Tracking System is an application used for programmers to track of software bugs in there work. it is essential in companies and used in doveloping software products. A major component of bug tracking system is database that records facts about known bugs. Facts may include the time of the bug was reported, its severity, the erroneous program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it.

In a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. However, this may sometimes yield inaccurate results because different bugs may have different levels of severity and complexity. The severity of a bug may not be directly related to the complexity of fixing the bug. There may be different opinions among the managers, architects and the developers about the relative ease of fixing bugs.

About Test Cases

Test cases plays a major role in the QA's life. The probability of fixing the bugs is always depends on the way the test cases are communicated. They should never be confused. Test Cases are written in such a way that they are tracable,self contained and should not be duplicated in preparing they should always be atomic. So every tester has to spend some time on the test cases before writing. Test conditons has to be clear and most of the test conditions wont be clear,so deep thinking is necessary for the testers. In the context to the DEEP THINKING, I do like to discuss an example given by the Jsmes Bach.

REQUIREMENTS :
1.THERE ARE FOUR CARDS. (cards are E,7.V.4)
2.THERE IS A LETTER ONE SIDE AND A NO. ON REVERSE SIDE.
3.IF THERE IS A VOWEL ON ONE SIDE AND A EVEN NO. ON OTHER SIDE.

In this Requirements, if we consider the first case which is clear, where as in second and third cases where the deep thinking should be there.

So for a Tester, deep thinking is always an important.

One of my friend asked a question about test requirement, i wondered how to answer to his question. One of the requirement in the web page is to check the back ground colour of the Username and Password.HE asked me whther i will check or not. I thought for a second and gave the answer, as "i will check the background colour of both the fields",but the thing is we have to make sure of the TEXT of the font colour also is checked. Even though iam wrong in this Example i learnt a new thing in Exploring a my knowledge towards the SOFTWARE TESTING.

NEVER GIVE UP TILL YOU SUCCEED

KEY PRINCIPLES OF SOFTWARE TESTING

1) TESTING ALWAYS SHOWS THE PRESENCE OF DEFECTS.

2) EXHAUSTIVE TESTING IS POSSIBLE.

3) EARLY TESTING.

4) DEFECTIVE CLUSTERING.

5) PESTICIDE PARADOX.

6) TESTING IS CONTEXT DEPENDENT.

7) ABSENCE OF ERRORS IS FAILURE.