Q1. What is Requirement Traceability Matrix?

The Requirements Traceability Matrix (RTM) is a tool to make sure that project requirement remain same throughout
the whole development process. RTM is used in the development process because of following reasons:
To determine whether the developed project is meet the requirements of the user.
To determine all the requirements given by the user
To make sure the application requirement can be fulfilled in the verification process.
Q2. What is difference between Pilot and Beta testing?
The differences between these two are listed below:
A beta test when the product is about to release to the end user whereas pilot testing take place in the earlier phase
of the development cycle.
In beta testing application is given to a few user to make sure that application meet the user requirement and does
not contain any showstopper whereas in case of pilot testing team member give their feedback to improve the quality
of the application.
Q3. Describe how to perform Risk analysis during software testing?
Risk analysis is the process of identifying risk in the application and prioritizing them to test. Following are some of
the risks:
1. New Hardware.
2. New Technology.
3. New Automation Tool.
4. Sequence of code delivery.
5. Availability of application test resources.
We prioritize them into three categories these are:
High magnitude: Impact of the bug on the other functionality of the application.
Medium: it can be tolerable in the application but not desirable.
Low: it can be tolerable. This type of risk has no impact on the company business.
Q4. What is Silk Test?
Silk Test is a tool developed for performing the regression and functionality testing of the application. Silk Test a tool
is used when we are testing the applications which are based on Window, Java, web or traditional client/server. Silk
Test help in preparing the test plan and management of those test plans, to provide the direct accessing of the
database and validation of the field.
Q5. What is difference between Master Test Plan and Test Plan.
The differences between Master Plan and Test Plan are given below:
Master Test Plan contains all the testing and risk involved area of the application where as Test case document
contains test cases.
Master Test plan contain all the details of each and every individual tests to be run during the overall development
of application whereas test plan describe the scope, approach, resources and schedule of performing test.
Master Test plan contain the description of every tests that is going to be performed on the application where as test
plan only contain the description of few test cases. during the testing cycle like Unit test, System test, beta test etc
Master Test Plan is created for all large projects but when it is created for the small project then we called it as test
plan.
Q6. How to deal with not reproducible bug?
Ans. A bug cannot be reproduced for following reasons:
1. Low memory.
2. Addressing to non available memory location.
3. Things happening in a particular sequence.
Tester can do following things to deal with not reproducible bug:
Includes steps that are close to the error statement.
Evaluate the test environment.
Examine and evaluate test execution results.
Resources & Time Constraints must be kept in point.
Q7.What is the difference between coupling and cohesion?
The difference between coupling and cohesion is discussed below:
Cohesion is the degree which is measure dependency of the software component that combines related
functionality into a single unit whereas coupling means that binding the related functionality into different unit.
Cohesion deals with the functionality that related different process within the single module where as coupling deals
with how much one module is dependent on the other modules within the application.
It is good to increase the cohesion between the software whereas increasing coupling is avoided.
Q8. What is the role of QA in a project development?
The role of Quality Assurance is discussed below:
QA team is responsible for monitoring the process to be carried out for development.
Responsibilities of QA team are planning testing execution process.
QA Lead creates the time tables and agrees on a Quality Assurance plan for the product.
QA team communicated QA process to the team members.
QA team ensures traceability of test cases to requirements.
Q9. When do you choose automated testing over manual testing?
This choice between automated testing over manual testing can be based upon following factors:
1. Frequency of use of test case
2. Time Comparison (automated script run much faster than manual execution.)
3. Reusability of Automation Script
4. Adaptability of test case for automation.
5. Exploitation of automation tool


Q10. What are the key challenges of software testing?
Following are some challenges of software testing:
1. Application should be stable enough to be tested.
2. Testing always under time constraint
3. Understanding the requirements.
4. Domain knowledge and business user perspective understanding.
5. Which tests to execute first?
6. Testing the Complete Application.
7. Regression testing.
8. Lack of skilled testers.
9. Changing requirements.
10. Lack of resources, tools and training
Q11. What is difference between QA, QC and Software Testing?
Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is
followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.
Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The
process set by QA is implemented by QC. The QC is the responsibility of the tester.
Software Testing: is the process of ensuring that product which is developed by the developer meets the user
requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.
Q12. What is concurrent user hits in load testing?
When the multiple users, without any time difference, hits on a same event of the application under the load test is
called a concurrent user hit. The concurrency point is added so that multiple Virtual User can work on a single event
of the application. By adding concurrency point, the virtual users will wait for the other Virtual users which are running
the scripts, if they reach early. When all the users reached to the concurrency point, only then they start hitting the
requests.
Q13. What is difference between Front End Testing and Back End testing?
The differences between front and back end testing are:
Front End Testing is performed on the Graphical User Interface (GUI).whereas Back End Testing involves
databases testing.
Front end consist of web site look where user can interact whereas in case of back end it is the database which is
required to store the data.
When ender user enters data in GUI of the front end application, then this entered data is stored in the database. To
save this data into the database we write SQL queries.
Q14. What is Automated Testing?
The process of performing testing automatically which reduces the human intervention this is automation testing. The
automation testing is carried out with the help of the some automation tool like QTP, Selenium, WinRunner etc. In
automation testing we use a tool that runs the test script to test the application; this test script can be generated
manually or automatically. When testing is completed then tools automatically generate the test report and report.
Q15. What is Testware?
The testware is:
The subset of software which helps in performing the testing of application.
Testware are required to plan, design, and execute tests. It contains documents, scripts, inputs, expected results,
set-up and additional software or utilities used in testing.
Testware is term given to combination of all utilities and application software that required for testing a software
package.
Testware is special because it has:
1. Different purpose
2. Different metrics for quality and
3. Different users
Q16.What is Exhaustive Testing?
Exhaustive Testing, as the name suggests is very exhaustive. Exhaustive testing means to test every component in
the application with every possible number of inputs. According to Principles of testing Exhaustive Testing is
Impossible because exhaustive testing requires more time and effort to test the application for all possible number of
inputs. This may lead to high cost and delay in the release of the application.
Q17. What is Gray Box Testing?
Grey box testing is the hybrid of black box and white box testing. In gray box testing, test engineer has the knowledge
of coding section of the component and designs test cases or test data based on system knowledge. In this tester
has knowledge of code, but this is less than the knowledge of white box testing. Based on this knowledge the test
cases are designed and the software application under test treats as a black box & tester test the application from
outside.
Q18. What is Integration Testing?
Integration testing is black box testing. Integration testing focuses on the interfaces between units, to ensure that
units work together to complete a specify task. The purpose of integration testing is to confirm that different
components of the application interact with each other. Test cases are developed with the purpose of exercising the
interfaces between the components. Integration testing is considered complete, when actual results and expected
results are same. Integration testing is done after unit testing. There are mainly three approaches to do integration
testing:
Top-down Approach tests the components by integrating from top to bottom.
Bottom-up approach It takes place from the bottom of the control flow to the higher level components
Big bang approach In this are different module are joined together to form a complete system and then testing is
performed on it.
Q19. What is Scalability Testing?
Scalability testing is testing performed in order to enhanced and improve the functional and performance capabilities
of the application. So that, application can meets requirements of the end users. The scalability measurements is
done by doing the evaluating the application performance in load and stress conditions. Now depending upon this
evaluation we improve and enhanced the capabilities of the application.
Q20. What is Software Requirements Specification?
A software requirements specification is a document which acts as a contract between the customer and the
supplier.
This SRS contain all the requirement of the end user regarding that application. SRS can be used as a
communication medium between the customer and the supplier.
The developer and tester prepare and examine the application based on the requirements written in the SRS
document.
The SRS documented is prepared by the Business Analyst by taking all the requirements for the customer.
Q21. What is Storage Testing?
In Storage Testing we test those functionalities of the application which is responsible for storing the data into
database. The data entered by the end user in GUI or front end, is the same data which is stored in the database.
The storage testing determines that the data taken from the front end of the application is stored in correct place and
in correct manner in the database.
Q22. What is Stress Testing?
Stress testing tests the software with a motive to check that the application do not crashes if we increase the stress
on the application by increasing the large number of user working on the application. We can also apply the stress on
the application firing the lots of process which cannot be handled by the application. We perform the stress testing on
the application evaluate the application capabilities at or beyond the limits of its specified requirements to determine.
Generally, this is a type of performance testing performed in a very high level of load and stress condition.
Q23. What is Test Harness?
A test harness is a collection of software and test data required to test the application by running it in different testing
condition like stress, load, data- driven, and monitoring its behavior and outputs. Test Harness contains two main
parts:
Test execution engine
Test script repository
Automation testing is the use of a tool to control the execution of tests and compare the actual results with the
expected results. It also involves the setting up of test pre-conditions.
Q24. Can you define test driver and test stub?
The Stub is called from the software component to be tested. It is used in top down approach.
The driver calls a component to be tested. It is used in bottom up approach.
Both test stub and test driver are dummy software components.
We need test stub and test driver because of following reason:
Suppose we want to test the interface between modules A and B and we have developed only module A. So we
cannot test module A but if a dummy module is prepare, using that we can test module A.
Now module B cannot send or receive data from module A directly so, in these cases we have to transfer data from
one module to another module by some external features. This external feature used is called Driver.
Q25.What is good design?
Design refers to functional design or internal design. Good internal design is indicated by software code whose
overall structure is clear, understandable, easily modifiable, and maintainable; is robust with sufficient error-handling
and status logging capability, and works correctly when implemented. Good functional design is indicated by an
application whose functionality can be traced back to customer and end-user requirements.
Q26. What makes a good QA or Test manager?
A good QA or Test manager should have following characteristics:
Knowledge about Software development process
Improve the teamwork to increase productivity
Improve cooperation between software, test, and QA engineers
To improvements the QA processes.
Communication skills.
able to conduct meetings and keep them focused
Q27. What is Manual scripted Testing and Manual Support testing?
Manual Scripted Testing: Testing method in which the test cases are designed and reviewed by the team before
executing it. It is done by manual testing teams.
Manual-Support Testing: Testing technique that involves testing of all the functions performed by the people while
preparing the data and using these data from automated system. it is conducted by testing teams
Q28. What is Fuzz testing, backward compatibility testing and assertion testing?
Fuzz Testing: testing application by entering invalid, unexpected, or random data to the application this testing is
performed to ensure that application is not crashing when entering incorrect and unformatted data.
Backward Compatibility Testing: Testing method which examines performance of latest software with older versions
of the test environment.
Assertion Testing: Type of testing consisting in verifying if the conditions confirm the product requirements.
Q29. How does a client or server environment affect testing?
There are lots of environmental factors that affect the testing like speed of data transfer data transfer, hardware, and
server etc while working with client or server technologies, testing will be extensive. When we have time limit, we do
the integration testing. In most of the cases we prefer the load, stress and performance testing for examine the
capabilities of the application for the client or server environment.
Q30. What are the categories of defects?
There are three main categories of defects:
Wrong: The requirements are implemented incorrectly in the application.
Missing: When requirement given by the customer and application is unable to meet those application.
Extra: A requirement incorporated into the product that was not given by the end customer. This is always a
variance from the specification, but may be an attribute desired by the user of the product.





1) What is the difference between the QA and software testing?

The role of QA (Quality Assurance) is to monitor the quality of the process to produce a
quality of a product. While the software testing, is the process of ensuring the final product
and check the functionality of final product and to see whether the final product meets the
users requirement.

2) What is Testware?

Testware is the subset of software, which helps in performing the testing of application. It is
a term given to the combination of software application and utilities which is required for
testing a software package.

3) What is the difference between build and release?

Build: It is a number given to Installable software that is given to testing team by the
development team.

Release: It is a number given to Installable software that is handed over to customer by the
tester or developer.

4) What are the automation challenges that QA team faces while testing?
Exploitation of automation tool
Frequency of use of test case
Reusability of Automation script
Adaptability of test case for automation
5) What is bug leakage and bug release?

Bug release is when software or an application is handed over to the testing team knowing
that the defect is present in a release. During this the priority and severity of bug is low, as
bug can be removed before the final handover.

Bug leakage is something, when the bug is discovered by the end users or customer, and
missed by the testing team to detect, while testing the software.

6) What is data driven testing?

Data driven testing is an automation testing part, which tests the output or input values.
These values are read directly from the data files. The data files may include csv files, excel
files, data pools and many more. It is performed when the values are changing by the time.

7) Explain the steps for Bug Cycle?
Once the bug is identified by the tester, it is assigned to the development manager in
open status
If the bug is a valid defect the development team will fix it and if it is not a valid defect,
the defect will be ignored and marked as rejected
The next step will be to check whether it is in scope, if it is happen so that, the bug is
not the part of the current release then the defects are postponed
If the defect or bug is raised earlier then the tester will assigned a DUPLICATE status
When bug is assigned to developer to fix, it will be given a IN-PROGRESS status
Once the defect is repaired, the status will changed to FIXED at the end the tester will
give CLOSED status if it passes the final test.
8) What does the test strategy include?

The test strategy includes introduction, resource, scope and schedule for test activities, test
tools, test priorities, test planning and the types of test that has to be performed.

9) Mention the different types of software testing?
Unit testing
Integration testing and regression testing
Shakeout testing
Smoke testing
Functional testing
Performance testing
White box and Black box testing
Alpha and Beta testing
Load testing and stress testing
System testing
10) What is branch testing and what is boundary testing?

The testing of all the branches of the application, which is tested once, is known as branch
testing. While the testing, which is focused on the limit conditions of the software is known
as boundary testing.

11) What are the contents in test plans and test cases?
Testing objectives
Testing scope
Testing the frame
The environment
Reason for testing
The criteria for entrance and exit
Deliverables
Risk factors
12) What is Agile testing and what is the importance of Agile testing?

Agile testing is software testing, which involves the testing of the software from the
customer point of view. The importance of this testing is that, unlike normal testing process,
this testing does not wait for development team to complete the coding first and then doing
testing. The coding and testing both goes simultaneously. It requires continuous customer
interaction.

It works on SDLC ( Systems Development Life Cycle) methodologies, it means that the task is
divided into different segments and compiled at the end of the task.

13) What is Test case?

Test case is a specific term that is used to test a specific element. It has information of test
steps, prerequisites, test environment and outputs.

14) What is the strategy for Automation Test Plan?
The strategy for Automation Test Plan
Preparation of Automation Test Plan
Recording the scenario
Error handler incorporation
Script enhancement by inserting check points and looping constructs
Debugging the script and fixing the issues
Rerunning the script
Reporting the result
15) What is quality audit?

The systematic and independent examination for determining the quality of activities is
known as quality audit. It allows the cross check for the planned arrangements, whether they
are properly implemented or not.

16) How does a server or client environment affect software testing?

As the dependencies on the clients are more, the client or server applications are complex.

The testing needs are extensive as servers, communications and hardware are
interdependent. Integration and system testing is also for a limited period of time.

17) What are the tools used by a tester while testing?
Selenium
Firebug
OpenSTA
WinSCP
YSlow for FireBug
Web Developer toolbar for firebox
18) Explain stress testing, load testing and volume testing?
Load Testing: Testing an application under heavy but expected load is known as Load
Testing. Here, the load refers to the large volume of users, messages, requests, data,
etc.
Stress Testing: When the load placed on the system is raised or accelerated beyond
the normal range then it is known as Stress Testing.
Volume Testing: The process of checking the system, whether the system can handle
the required amounts of data, user requests, etc. is known as Volume Testing.
19) What are the five common solutions for software developments problems?
Setting up the requirements criteria, the requirements of a software should be
complete, clear and agreed by all
The next thing is the realistic schedule like time for planning , designing, testing,
fixing bugs and re-testing
Adequate testing, start the testing immediately after one or more modules
development.
Use rapid prototype during design phase so that it can be easy for customers to find
what to expect
Use of group communication tools
20) What is a USE case and what does it include?

The document that describes, the user action and system response, for a particular
functionality is known as USE case. It includes revision history, table of contents, flow of
events, cover page, special requirements, pre-conditions and post-conditions.

21) What is CRUD testing and how to test CRUD?

CRUD testing is another name for Black Box testing. CRUD stands for Create, Read, Update
and Delete.

22) What is validation and verification in software testing?

In verification, all the key aspects of software developments are taken in concern like code,
specifications, requirements and document plans. Verification is done on the basis of four
things list of issues, checklist, walkthroughs and inspection meetings. Following verification,
validation is done, it involves actual testing, and all the verification aspects are checked
thoroughly in validation.

23) What is thread testing?

A thread testing is a top-down testing, where the progressive integration of components
follows the implementation of subsets of the requirements, as opposed to the integration of
components by successively lower levels.

24) What is configuration management?

It is a process to control and document any changes made during the life of a project.
Release control, Change control and Revision control are the important aspects of
configuration management.

25) What is Ad Hoc testing?

It is a testing phase where the tester tries to break the system by randomly trying the
systems functionality. It can include negative testing as well.

) What is data-base testing? Data base testing is segmented into four different categories.


Testing of Data Integrity
Testing of Data Validity
Data base related performance
Testing of functions, procedure and triggers
2) In database testing, what do we need to check normally?

Normally, the things that we check in database testing are:


Constraint Check
Validation of a Field size
Stored procedure
Matching application field size to database
Indexes for performance based issues
3) Explain what is data driven test?

In a data-table, to test the multi numbers of data, data-driven test is used. By using this it can
easily replace the parameters at the same time from different locations.

4) What are joins and mention different types of joins?

Join is used to display two or more than two table and the types of joins are:


Natural Join
Inner Join
Outer Join
Cross Join
The outer join is divided again in two:
Left outer join
Right outer join
5) What are indexes and mention different types of indexes?

Indexes are database objects and they are created on columns. To fetch data quickly they are
frequently accessed. Different types of indexes are:
B-Tree index
Bitmap index
Clustered index
Covering index
Non-unique index
Unique index
Database Testing

6) While testing stored procedures what are the steps does a tester takes?

The tester will check the standard format of the stored procedures and also it checks the
fields are correct like updates, joins, indexes, deletions as mentioned in the stored
procedure.

7) How would you know for database testing, whether trigger is fired or not?

On querying the common audit log you would know, whether, a trigger is fired or not. It is in
audit log where you can see the triggers fired.

8) In data base testing, what are the steps to test data loading?

Following steps need to follow to test data loading
Source data should be known
Target data should be known
Compatibility of source and target should be checked
In SQL Enterprise manager, run the DTS package after opening the corresponding
DTS package
You have to compare the columns of target and data source
Number of rows of target and source should be checked
After updating data in the source, check whether the changes appears in the target or
not.
Check NULLs and junk characters
9) Without using Database Checkpoints, how you test a SQL Query in QTP?

By writing scripting procedure in VBScript, we can connect to database and can test the
queries and database.

10) Explain how to use SQL queries in QTP ?

In QTP using output database check point and database check, you have to select the SQL
manual queries option. After selecting the manual queries option, enter the select queries
to fetch the data in the database and then compare the expected and actual.

11) What is the way of writing testcases for database testing?

Writing a testcases is like functional testing. First you have to know the functional
requirement of the application. Then you have to decide the parameters for writing testcases
like
Objective: Write the objective that you would like to test
Input method: Write the method of action or input you want to execute
Expected: how it should appear in the database
12) To manage and manipulate the test table what are the SQL statements that you have
used in Database testing?

The statements like SELECT, INSERT, UPDATE, DELETE are used to manipulate the table,
while ALTER TABLE, CREATE TABLE and DELETE TABLE are used to manage table.

13) How to test database procedures and triggers?

To test database procedures and triggers, input and output parameters must be known.
EXEC statement can be used to run the procedure and examine the behaviour of the tables.
Open the database project in solution explorer
Now in View menu, click the database schema
Open the project folder from schema View menu
Right click on the object that has to be tested, and then click on the dialog box that
says Create Unit Tests
After that create a new language test project
Select either a) Insert the unit test or b) Create a new test and then click OK
Project that has to be configured will be done by clicking on the Project Configuration
dialog box.
Once it configured click on OK
14) How you can write testcases from requirements and do the requirements represents
exact functionality of AUT (Application Under Test)?

To write a testcases from requirements, you need to analyse the requirements thoroughly in
terms of functionality. Thereafter you think about the appropriate testcases design
techniques like Equivalence partitioning, Black box design, Cause effect graphing etc. for
writing the testcases.
Yes, the requirements represent exact functionality of AUT.

15) What is DBMS?

DBMS stand for Database management system, there are different types of DBMS
Network Model
Hierarchical Model
Relational Model
16) What is DML?

DML stands for Data Manipulation Language, It is used to manage data with schema objects.
It is a subset of SQL.

17) What are DCL commands? What are the two types of commands used by DCL?

DCL stands for Data Control Language, it is used to control data.

The two types of DCL Commands are:

Grant: By using this command user can access privilege to database

Revoke: By using this command user cannot access the database

18) What is white box testing and black box testing?

Black box testing means testing the software for the outputs on giving particular inputs. This
testing is usually performed to see if the software meets the users requirements. There is no
specific functional output expected for running this test.

The white box testing is done to check the accuracy of code and logic of the program. This
testing is done by the programmer who knows the logical flow of the system.

19) How does QTP evaluate test results?

Once the testing is done, QTP will generate a report. This report will show the checkpoints,
system message and error that were detected while testing. The test results window will
show any mismatches encountered at the checkpoints.

20) Explain the QTP testing process?
QTP testing process is based on following steps:
Creating GUI (Graphical User Interface) Map files : Identifies the GUI object which has
to be tested
Creating test scripts: Test scripts are recorded
Debug tests: Test should be debugged
Run tests: Testcases should be run.
View results: The results reflects the success or failure of the tests
Report detects: If the test is failed, the reasons will be recorded in the report detect
file
21) What is load testing and give some examples of it?

To measure the system response, load testing is done. If the load exceeds the users pattern
it is known as stress testing. Examples of load testing are downloading the set of large files,
executing multiple applications on a single computer, subjecting a server to large number of
e-mails and allotting many tasks to a printer one after another.

22) How to test database manually?

Testing the database manually involves checking the data at the back end and to see whether
the addition of data in front end is affecting the back end or not, and same for delete, update,
insert etc.

23) What RDBMS stands for and what are the important RDMBS that SQL use?

RDBMS stands for Relational Database Management Systems that use SQL, and the
important RDBMS that SQL uses are Sybase, Oracle, Access ,Ingres, Microsoft SQL server
etc.

24) What is performance testing and what are the bottlenecks of performance testing?

Performance testing determines the speed of the computer system performance. It includes
the quantitative tests like response time measurement. The problem in performance testing is
that you always need a well-trained and experienced man power also the tools you use are
expensive.

25) What is DDL and what are their commands?

To define database structure, DDL is used. DDL stands for Data Definition Language. The
various DDL commands include Create, Truncate, Drop, Alter, Comment and Rename.


What is the difference between Functional and Non-functional testing?

Functional Testing covers:
Unit Testing
Smoke testing / Sanity testing
Integration Testing (Top Down, Bottom up Testing)
Interface & Usability Testing
System Testing
Regression Testing
Pre User Acceptance Testing(Alpha & Beta)
User Acceptance Testing
White Box & Black Box Testing
Globalization & Localization Testing

Non-Functional Testing covers:
Load and Performance Testing
Ergonomics Testing
Stress & Volume Testing
Compatibility & Migration Testing
Data Conversion Testing
Security / Penetration Testing
Operational Readiness Testing
Installation Testing
Security Testing (Application Security, Network Security, System Security)

Hi All,
According to me
Functional Testing:Functional testing is what a system is supposed to do?
e.g. interoperability

Non-Functional Testing means How a system is supposed to do?

e.g. Eficiency,accuracy.


I will give an example regarding both functional and non-functional testing.Suppose you send
an email to an user .Here the functional testing is to check the email is going to the proper
email tht you have specified or not.But the non-functional testing is to how the system send
the email to the specified address,what are the protocols used to send an email..


I think you will get a fair idea about functional and non-functional testing.
Software testing Phases:
Software testing has various different phases such as
1) Test plan
2) Testing Requirement
3) Testing Design
4) Test Execution
5) Test Reporting
6)Maintenance testing
he Testing phases are as follows:

1. Requirements Analysis
2. Test Designing
3. Test Planing
4. Test Development
5. Test Execution
6. Test Reporting
7. Test Result Analysis
8. Defect Retesting
9. Regression Testing
10. Test Closure

The Testing phases are as follows:

1. Requirements Analysis
2. Test Case Designing
3. Test Planing
4. Test Development
5. Test Execution
6. Test Reporting
7. Test Result Analysis
8. Defect clustering
9. Regression Testing
10.Re-testing
11. Test Closure Activities

Testing is a process that involves many activities. These activities can be grouped into
following step:

Test planing and control.
Analysis and design.
Implementation and Execution
Evaluating Exit Criteria and Reporting.
Test Closure.

Tips on Localization Testing
Do you know:

A little care at pre release stage of a localized Software product can save precious dollars !!

Software Localization Services is as important as software development. We at QA InfoTech
understand that Testing software in a particular language necessarily entails providing all
inputs in that language. By entering data in localized characters, a tester cleanses the
process to a great extent and ensures the end user doesnt waste time over possible errors.
At QA InfoTech, we have ample experience of localized testing of software. We have a
partnership with universities and experienced linguists who help us understand the subtle
differences in the languages and cultures.

- Our Globalization experts analyze the product code to establish its existing
internationalization level and validated by our testing experts who run manual or script based
tests as well.
- Our aim is to validate products so that they offer proper functionality across different
languages. Proper functionality ensures that the internal design of the product is such that it
performs the same functions regardless of international environment settings or
cultures/locales and the correct representation of data.
- Expertise on Localization Testing of bi-directional languages.

Our functional and cosmetic checks ensure that the product is validated and verified in the
local language and issues if any are successfully regressed. For more info, please visit:

Localization is the process of adapting a globalized application to a particular culture/locale.
Localizing an application requires a basic understanding of the character sets typically used
in modern software development and an understanding of the issues associated with them.
Localization includes the translation of the application user interface and adapting graphics
for a specific culture/locale. The localization process can also include translating any help
content associated with the application.

Localization of business solutions requires that you implement the correct business
processes and practices for a culture/locale. Differences in how cultures/locales conduct
business are heavily shaped by governmental and regulatory requirements. Therefore,
localization of business logic can be a massive task.

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.
Localization Testing in the software testing process for checking the localized version of a
product (e.g., Japanese product for Japanese user). Localization Testing checks the quality
of a localized version for a particular that culture/locale setting. Localization Testing is based
on the results of Globalization Testing which verifies the functional support for that particular
culture/locale setting. We should invite the local staff to help our localization testing by
checking the quality of translation as well.