This is  called Internationalization Testing or I18N 
Testing 
thgis testing will be conducted when a product or 
application designing, developing, and engineering products 
that can be launched worldwide.

The most common checklst:
Code review 
English language compatibility? 
DB or Unicode enabled from the ground up? 
Product Rules 
Menu and dialogue box designs; Did they leave room for text 
expansion? 
Source Code Control Rules 
All editions are using Unicode and/or DBCS based on a 
single executable 
Coding Conventions 
Code should NOT assume that characters are 8 or 16 bit

Byee friends 
Rajendra
Rajednra_penumalli@yahoo.com

for the bug which hav high priority has to be rectified 
first

the p3 bug should resolved 1st.

We alway give more importance for  priority and then  
severity 

which is affected very sevior with High priority or low 
priority that particular bug has to be fix as early as 
possible then only we can able to go for further testing 


When you need to consider severity there is no priority 
they have given only severity like FAT, MAJ & MIN 

here you have to consider severity. 

so you have to give more importance for  BUG A

the bug having high priority will be resolved 1st.

As far as I think that every person has it's personeal 
issues then only s/he decides to leave/quit the 
organization. Here in such a scenariao you need to tell the 
HR the exact issues which you have had in your earlier 
organizations.

ITS MY WISH

For Better Prospects and Advnace knowledge.

iam not satisfied with these organisations..
now its my wish to change or not..

It depends on the what sort of Error the user is experiencing.

By using Accessibility testing

It is nothing but STLC
test plan 
test design 
test execution 
result analysis 
bug tracking and reporting

Executing the programe with intent of finding errors called 
testing. In testing process the tester to test the 
application when the developer build relesed to testing 
team if any errors are found in that application then test 
engg prepare defect report and send to developement team 
this process is continuous till the application is defect 
free.
 if any mistakes found please correct

Testing is often confused with the processes of quality
control and quality assurance. Testing is the process of
creating, implementing and evaluating tests. If you are
shopping for a new television, you can call that process
"testing for the best TV for you"... it's kind of
pretentious, but that is what you're doing as you compare
prices and features to find what will work best for you.
Testing usually has a limited scope and duration – you're
just looking at TVs and only in your town, you're not going
to spend a year shopping, are you?
Testing is predicated on the use of a standard of quality:
you have a specification of what's allowable (no broken
links? ALT tags have values? Maximum page weight is 10K?)
and you compare the site to the standard, noting deviations
and shortcomings. This seems simple, but your testing is
only valuable if your standard of quality is comprehensive,
well thought-out, and reasonable. If your standard has
holes, then your testing process has blind spots.
Quality control is a refinement of testing, involving the
formal and systematic use of testing and a precise
definition of what quality means for the purposes of the
test. You aren't just testing; you are testing and then
doing something with the results. Quality control is used
for testing a product or output of a process, with the test
measuring the subject's ability to meet a certain benchmark
or threshold of quality. The tests usually take the form of
"does this product meet requirement X?", and are often
pass-fail.

1) Test Methodology is nothing but implementation of test
strategy i.e description of test levels in which several
test activities are performed. As from testing perspective
integration testing, system testing uses black box testing
methodology. Unit testing uses white box testing methodology.

2) Test data is a real time data prepared with the help of
use cases or sent by the client side. It is used to test the
condition using real time data. 

3) Test scenario is nothing but a sequential steps followed
to design test cases. EXAMPLE: to test ATM withdrawal
process we create scenarios. 

4) Test environment controlled environment replica of real
time environment where where would be executing our test cases.

I tried my best to answer above questions now lets hear what
other members have to say on the above
Thanks

2.low severity and high priority: company logo
severiety is less,it does not affect to the software but 
the priorrity is more.

3.both are high:
arithmetical bug.

4.colour of the page.
it does not affect the s/w

*High P and low s- If a bug has great bussiness importance 
but it is not affecting the funcionality of feature. e.g. 
company name is Kavita Pvt. LTD. but wrongly written as 
Kvita Pvt. LTD. on a build. It has business importance bcoz 
its name is written wrongly. But it has low severity 
becouse the funcnality of feature is working fine.
* Low P high S- a bug which is not easily reporducible by 
end user. For e.g. If the hard disk of your computer 
crashses then Bill Gates will not come to repaire it. In 
this case severity is high but priority is low.
* High P and high S- Any bug filed under sanity testing
(sanity covers test cases which are mandatory to be passed 
or go to the next level of testing) is high P and High S.
Suppose you have to send a report through mail to your 
manager and mangaer's work is based on ur report. But you 
are not able to login your account and therefore not able 
to send mails.
*Low P and Low S- such as font size font color fond family 
etc.

the main diff is associate object repository, copy action 
are not there in 8.2 version.

Hi....,
 Severity:
         Relative Impact of the Defect i.e How far the    
applications is affected by this defect...(Low, Medium, 
High, Critical..)
 
  Priority:
         Relative Importance of the defect i.e Giving 
preference to the Defect...(High, Medium, Low)

Severity means how badly it harms the system .
Priority means how urgently bug is needed to fix. 
Severity is constant....whereas priority might change 
according to schedule
Type of Severity:
                 Critical->defect having high problem
                 Major.
                 Medium.
                 Minor.
                 Cosmetic->Glamour look.
Type of Priority:
                High.
                Medium.
                Low.

Priority - Priority is the order in which developer has to 
fix the bug.
Severity - Severity is how seroisly the bug is impacting 
the application.

Eg.


High Priority & High Severity: A show stopper error which 
occurs on the basic funcationality of the application . 
(Eg. A site maintaing the student details, on saving record 
if it, doesn't allow to save the record then this is high 
priority and high severity bug.)

High Priority & Low Severity: The spell mistakes that 
happens on the cover page or headin or title of an 
application.

High Severity & Low Priority: The application generates a 
show stopper or system error, (for which there is no 
workaround) but on click of link which is rarely used by 
the end user.


Low Priority and Low Severity: Any cosmetic or spell issues 
which is with in a paragraph or in the report (Not on cover 
page, heading, title).

In this we can take only some estimation time but we cant 
tell the exact time why because Untill one phase is 
completed we cant move to the next phase.