integration testing is performed when any of the two or more
components are joined together to work as one. it may be
integration of two systems or two modules or so. in case of
integration testing we test that are those components
capable of working together. In case of integration testing
interfaces of joined components is given more importance. it
is checked that the data flow b/w the components is correct
and their shld be no leakage at the interface and so on.
But in case of system testing we test the sys as whole for
both its functional and non functional requirements.

intergration testing means data flowing between 2 modules.

system testing means end to end testing done by end user 
and testing engineer.

Integration Testing;

The unit tested module has to be integrated to build the 
application.

For Eg: When we test the With draw and Deposit option after 
integrating both the functionality it is the integration 
testing

where as System Testing involves testing the entire 
functionality of the application.

EG; Testing the all the functionalities in Banking

A. integration testing:testing of combined parts of an 
application to determine if they function together 
correctly. The 'parts' can be code modules, individual 
applications,client and server applications on a network, 
etc. This type of testing is especially relevant to 
client/server and distributed systems.


System Testing:system testing will conducted on the entire 
system to check whether 
it is meeting the customer requirements r not

We can test a web application by measuring the response 
time by using visual studio.

Equivalence Class Testing is when you create sets of input
that have equivalent expected behavior. You do this until
all possible inputs show up in one of the groupings. Now
when you test one item from each of the inputs you should be
covering all the possible inputs in that grouping.

Some types of inputs lend themselves really well to this
type of testing – the first is a range of values. You break
it down into values within the valid range, invalid values
above the valid range and invalid values below the valid
range. Lets have an example to better illustrate what I am
trying to describe. We are going to test the
appointment-making part of the program. An appointment has
four fields:

   1. Time
   2. Day
   3. Month
   4. Year


Lets look at the month input field. Depending on how it is
implemented it could take valid values from 1-12 or it could
take the months in a string format. Lets look at the input
of values from 1-12 and what equivalence classes world be
necessary to test this input.

    * valid range of 1-12
    * invalid range below the valid range <1
    * invalid range above the valid range >12


If the input was a string you would end up with two sets.
One that had the valid inputs in it and one that had every
thing else you could think to put in it.

So along with the month input you would also have a day,
year, and time input. The program is written in such a way
that they all have to be tested at the same time. So you
list all the groupings for all the other inputs fields and
test them at the same time. You will notice that you can
test most of the valid test cases at the same time, but you
will have to test the error cases one field at a time so you
can make sure the error is handled appropriately.

This kind of testing will allow you to keep the number of
test cases small, and you could use this type of testing at
any level of testing from unit all the way up to acceptance
testing. One of the limiting factors of this type of testing
is that it assumes identical behavior for all items in a
grouping. This is best suited to testing programs where
inputs are within ranges or values in sets

EQC =equlience class particision, this is used to find the 
defect in less time, by dividing 
example in a login screen user ID accpect up 100 string ,if 
we want to test every time we have to pass onstring and it 
is time waste ,so we divide in to 10 parts and check

Requirements should clear, complete and precise.

PK

A Good Requirement is one which covers all the required 
features(Functions).The Required features should be met.
Even the usability features and Performance requirements 
should be mentioned in it.

Well one can proceed with adhoc testing .

mail:akshay_bali2001@yahoo.co.in

Proceed with Exploratory testing

Code coverage is nothing but testing the whole code once to 
checking whether it is up to testing or not.

statement coverage,
decision coverage,
boundary analysis ,
multiple condition decision coverage ,