As far as I got that definitions (thanks Pradeep) you could involve mocking. A list of mock frameworks is available here.
Aslak Hellesoy recommends the usage of jMock
At the moment, I am using a library called jMock, which is the evolution of the first mock object framework that came around created by--Oh my God, I have to mention all the names--I don�t remember all the names. They found some flaws in the initial design and they got together and they figured out a better way to do it, so jMock was born.
./pope [ October 12, 2004: Message edited by: Ali Pope ]
If you're talking about a web application, a relatively popular choice is to use a library such as HttpUnit, JWebUnit, HtmlUnit, Jameleon, FIT, FitNesse, etc. against the UI (or a service layer beneath the UI) with the code executing against a real database and other similar resources that are usually mocked out somehow in unit tests.
Originally posted by Ali Pope: What do you mean by integration testing?
If you are interested in more information about integration testing, look at "Managing your Way through the Integration and Test Black Hole". This article presents approaches to estimate and manage more accurately the integration and test efforts.
Originally posted by Ali Pope: Is it only me that see a difference between integration testing and conitnous integration testing (according to the links on this thread)?
No, it's not only you. They are two othogonal things, I'd say.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus