compatability testing:
                      it is also known as portability 
testing, during this test we will(test enggs) validates 
that whether our application build is running on customer 
expected platforms or not?
     eg:operating sytems,compilers,browsers..etc
there are two types of compaltability problems we hav such 
as forward compatability and backward compatability.
    
Configuration testing/hardware compatability:
                during this test test enggs validates 
whether the application build is suppporting different 
technology hardware devices or not?
      eg diff technologies of printers
          "       "          "  n/ws
          "       "         popology n/ws.......etc

both are the concepts of non-functional testing 
Compatibily is testing is done on platforms,"whether our 
software is running on customer expected platforms or not"?
It is also called as portability testing.That means what 
s/w we develop it should support all other operating 
systems.

Configuration:Here we check whether pur s/w is supporting 
all types of h/w devices.

Hi there,

here u can use "Sendkeys" concepts..for further info please 
see the QTP help.

need urgentlyy

colcount = datatable.GetSheet(Sheet name).GetParametercount

using above GetParameterCount u can get how many columns in 
Datatable.

Informal review is otherwise called as peer review.  It is 
a friendly approach and is conducted among the testers.  It 
is not scheduled before and no reports are prepared for 
this review.

Hi Aman,

Peer review is a small review which is done/shared within 
the team membersi,e you have written some testcases and 
your friend has written some testcases u share ur testcases 
for a review with your friend,just to know whether u have 
missed anything or not 

review is nothing but a checking process

Hi Tulsi,
Thnx a lot dear 4 ur answer.. i think its a perfect 
answer.. i really needed this.. Tulsi, r u workin smwhere?? 
i think u can help me a lot in testing.. thnx again Tulsi..

Peer Review is nothing but an informal review and is the 
process to forward the testing documents to your colleagues 
and tell him/her to check that find out for any errors what 
unintentionally you have missed out.

in simple words Peer Review means "two testing teams, 
testing each other's work" it is also known as buddy testing
but this is not followed by the orgs currently.

Peer review is a Informal meeting between the team members
who are working under the same Project.This can be done
between the testers or between the tester and the developing
team to check whether they both are in the same path on the
requirements or anything needs to be changed.This will be
done during each phase of the project.

bug is nothing but devition from requirement.

Bug is mainly defined as a deviation from the requirement 
if any field doesnot perform its functionality as per the 
requirement functionality then it is called as abug

Bug is a Flaw in a system or system component which may 
cause to fail the system or the system component to provide 
its desired operation.
                      Normally bug is found if there is a 
mismatch between Expected and Actual result.

When a bug is found it is marked by digits 1 to 4.It is the 
priority(HOW FAST THE BUG SHOULD REMOVE) associated with 
bug set by the tester or the test lead.Like

1 - Very Major
2 - Major
3 - Average
4 - Low

Do's:
1.Understand the thorough knowledge of application
2. Think different scenarios per funtion
3. Make a attitude of breaking the application
4. Have good rappo with developers team
5. do write test cases lots for functions
6. follow the timelines, test plan regularly
7. make a habit of documentation of each and every work 
your doing
8. send the daily status, to the reporting team and check 
it out in cm tool.
9. solve your system issues on your own which leads you 
more confident.
10. reduce your rework in all phases.
11. Make effective description so that developers will 
understand the bug easily 
Don'ts:
1.Don't overtake developers
2.Don't hide bugs just to make your bug count high
3.Don't be tired of testing, do as much as you can
4.Don't think what you have done is enough
5.Don't be harsh to explain your views to others in tough 
situation

please comment me, if i am wrong?

Prioritization is nothing but how fast a work has to be 
completed so based on the importance we prioritize our works

In Relation to testing it indicates that on which platform 
u would like to work whether it is .Net,Java,C# Asp and sap 
etc

Its called Internationalisation testing i,e I18N. I18N is 
the term used for testing among different international 
languages .
Localisation testing is the term used for testing among 
various regional languages .

MULTI-LANGUITY/FOREIGN LANGUAGES TESTING.

The testing applicable on multi languity s/w's ,which are
developed in JAVA UNICODE TECHNOLOGY.
This can be done in two ways-

Localization- Tester can go to convert english to different
languages.

Globalization/Internationalization-Tool can go to convert
english to diffenrent languages.

Manual testing is the process where the tester puts his 
100% effort on the tool to test the application.

to check out something(error ,bug,mistake,defect) without 
tool is called manual testing

Identify the bugs in an application without using any tool

Testing with a Testing tools is know as manual testing.
Check me if i have  miss some thing or if i am wrong

Thanks & Regards,
Vikash Chandra

Sorry plz ignore my first answer( #4)

This what i wanted to write :

Testing without Testing tools is known as manual testing.


Thanks & Regards,
Vikash Chandra

A tester conducts any test in the application build without 
using any tool is called manual testing

black box testing techniques based on external 
specification without of how the system is constructed.

 black box Testing Strategies/Techniques

1. black box testing should make use of randomly generated 
inputs (only a test range should be specified by the 
tester), to eliminate any guess work by the tester as to 
the methods of the function  
2. data outside of the specified input range should be 
tested to check the robustness of  the program  
3. boundary cases should be tested (top and bottom of 
specified range) to make sure the highest and lowest 
allowable inputs produce proper output 
4. the number zero should be tested when numerical data is 
to be input 
4.stress testing should be performed (try to overload the 
program with inputs to see where it reaches its maximum 
capacity), especially with real time systems 
5. crash testing should be performed to see what it takes 
to bring the system down 
6. test monitoring tools should be used whenever possible 
to track which tests have already been performed and the 
outputs of these tests to avoid repetition and to aid in 
the software maintenance 
7. other functional testing techniques include: transaction 
testing, syntax testing, domain testing, logic testing, and 
state testing. 
8.finite state machine models can be used as a guide to 
design functional tests

The Black Box techniques are
1.Boundary Value Analysis(BVA)
2.Eqivalence class partitions(ECP)
3.Decision Table(DT) and 
4.State Transition Diagram(STD)

B.V.A (Boundary Value Analysis)

E.C.P( Equallence Class Partition)

Error Guessing

Black Box Design Techniques :

1. B.V.A(Boundary Value Analisys)

Input values of the boundaries of input domain are tested.

Example :
An inventory raises from 10,000 unit to 20,000 unit.
If A is valid boundary of 10,000 and B is valid boundary of 
20,000 then invalid boundary of A is A-1 and same for B is 
B-1.

Then Valid Boundary values are : 10,000(A) and 20,000(B)
and Invalid Bounadry values are 9,999(A-1) and 19,999(B-1).

Advantages :
i)Small set of inputs
ii)Very clear guideline for choosing inputs

Disadvantages :
i)Doesn't combine all possible set of inputs.

2. E.C.P(Equivalence Class Partitioning)

Same types of inputs will be placed in same class;

Example:
For above example 
Valid Class for A & B
Invalid Class for A-1 & B-1

Advantages :
i)Minimizes set of inputs
Disadvantages :
i) No guide line for choosing inputs
ii)Doesn't combine all possible inputs

Error Guessing

An informal technique where experienced tester apply his or 
her logic to find out defects after when a lot of formal 
techniques have applied already.

yes , we do functional testing inside integration testing 
wether modules are integrating corectly or not

yes u can . make an action of a test as an resuable action 
and then call that action in another test

Testing can be majorly divided into following types;

1) White Box Testing.
2) Black Box Testing.

White Box Testing: Generally it is performed on the code of 
software. To perform white box testing, you have to 
understand the logic behind the code.

Black Box Testing: To perform black box testing, you need 
not have to understand the logic behind the code. Black box 
testing is further divided into sub types, which are as 
follows;

a) Functional Testing.
b) System Testing.
  i)  Usability Testing.
  ii) Performance Testing.
      1) Load Testing.
      2) Stress Testing.

BVT: Build validation testing