
	Where results make sense

Topic: Integration testing

Related Topics

System testing

Software testing

Stress testing

White box testing

Load testing

Black box testing

Regression testing

Installation testing

Performance testing

Conformance testing

Usability testing

User acceptance testing

Stability testing

Computer software

Software engineering

In the News (Mon 7 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	14. What are unit, component and integration testing? (Site not responding. Last check: 2007-10-22)
		Note that the definitions of unit, component, integration, and integration testing are recursive: Unit.
		The outcome of the test of B may or may not be affected.
		System testing specifically goes after behaviors and bugs that are properties of the entire system as distinct from properties attributable to components (unless, of course, the component in question is the entire system).
	www.faqs.org /faqs/software-eng/testing-faq/section-14.html (494 words)

	Integration testing - Wikipedia, the free encyclopedia
		Integration testing (sometimes called Integration and testing and abbreviated IandT) is the phase of software testing in which individual software modules are combined and tested as a group.
		Integration testing takes as its input modules that have been checked out by unit testing, groups them in larger aggregates, applies tests defined in an Integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.
		All test cases are constructed to test that all components within assemblages interact correctly, for example, across procedure calls or process activations.
	en.wikipedia.org /wiki/Integration_testing (268 words)

	Integration Testing
		The simplest application of structured testing to integration is to combine module testing with integration testing so that a basis set of paths through each module is executed in an integration context.
		When structured testing has already been performed at the module level, module design complexity can be used to drive integration testing, requiring a basis set of paths through each module's reduced graph to be tested in integration.
		Integration tests are derived from the reduced graphs using the techniques of sections 7.4 and 7.5.
	hissa.nist.gov /HHRFdata/Artifacts/ITLdoc/235/chapter7.htm (2657 words)

	5.6.1.5 Integration testing (Site not responding. Last check: 2007-10-22)
		Integration testing can proceed in a number of different ways, which can be broadly characterised as top down or bottom up.
		In top down integration testing the high level control routines are tested first, possibly with the middle level control structures present only as stubs.
		These would be tested in breadth-first manner, but over a period of time each would be replaced with successive refinements which were closer to the full functionality.
	www.scism.sbu.ac.uk /law/Section5/chap6/s5c6p15.html (366 words)

	Software Testing
		The art of testing is to design a small, manageable set of test cases so as to maximize the chances of detecting a fault while minimizing the redundancy amongst of the cases.
		Equivalence testing, combined with boundary value analysis, is a fl-box technique of selecting test cases in such a way that new cases are chosen to detect previously undetected faults.
		Acceptance testing is done either by the client organization, by the SQA group in the presence of client representatives, or by an independent SQA group hired by the client for this purpose.
	sern.ucalgary.ca /courses/seng/411/w04/Testing.htm (3099 words)

	Integration Testing
		Integration Testing can encompass a wide variety of different types of test, but in an application development project there are five forms of component integration which are recognized and which are likely to account for most Integration Testing.
		A key concern of dialog component integration testing is to verify that the use of this communication area is correct and consistent i.e.
		Once again, Integration Testing must verify that invocation of the global from each transaction works as specified, that appropriate data is sent (and received by the global component), and that when global processing is completed, control is returned to the context from which the global was invoked.
	www.sei.cmu.edu /intro/process/technqs/q_it.htm (1960 words)

	Integration Testing for Application Blocks (PAG Documentation)
		Test the external interfaces for various types of input that are at the boundary of the specified range of expected input for an application that integrates the application block.
		Test the external interfaces for various types of input that are outside the specified range of expected input for an application that integrates the application block.
		Integration testing is important because a piece of code that functions correctly when it is tested as a separate unit can demonstrate problems when it is integrated into the actual application.
	msdn.microsoft.com /library/en-us/dnpag2/html/MTF_ch09.asp?frame=true (7938 words)

	[No title] (Site not responding. Last check: 2007-10-22)
		Test Report - Integration Testing * The test report documents test results and list any discrepancies which must be resolved before the tested components can be used as the foundation for another integration level.
		Integration Test Procedure * Each time a module or build is incorporated into the overall structure, tests are generated for the new addition and add tests are re-run to assure that intermodular "noise" has not caused problems in other (already integrated) modules.
		White-box testing (program-based testing) - it uses the logical flow of the detailed design (or code) as a driver for test case design; and the possibility of other significant test cases is ignored.
	www.njit.edu /v2/ClassNotes/CIS673/CIS673Q2.txt (1409 words)

	Eggplant Integration Testing Use Case
		An Integration Test is actually composed of different types of test, but its objective is to ensure that the interaction of two or more components produces results that satisfy functional requirements.
		Integration Tests resemble actual usage more than Unit Tests do; therefore, functional deficiencies are more likely to be detected at this level of testing than they are with Unit Testing.
		An Integration Test at the UI level is often used to validate a new UI component or to validate an application's collaboration with other utilities/applications on a system.
	www.redstonesoftware.com /Testing/IntegrationTesting (573 words)

	Integration Testing
		Now the integration tests introduces a level of testing that falls beyond the scope of the unit tests or the TCK tests.
		The integration test is designed to be run after the assemblies are built but as a part of the same build process.
		The integration test is part of the regular geronimo tree and it resides under geronimo/testsuite.
	cwiki.apache.org /GMOxDEV/integration-testing.html (738 words)

	John Fraser's Weblog (Site not responding. Last check: 2007-10-22)
		The integration of this module is tested, thus the term integration testing.
		This tends to add to the confusion of terms, but if you think about it, when you are unit testing a facade (or component interface) you may be unit testing that component, but all the aggregated components in the background are going through integration testing at the same time.
		Integration testing is used again to attack higher and higher levels of the system.
	radio.weblogs.com /0133680/2005/03/05.html (778 words)

	ploeh blog : Integration Testing Principles
		As I've written before, integration tests are different from unit tests, but that does not mean that unit testing tools such as Visual Studio Team System can't or shouldn't be used to define integration tests.
		However, many integration tests will, by their nature, require the presence of external infrastructure, such as a relational database, web services, queues, etc. This may seem to conflict with the ambition that a test suite should be fully automated and driven only by its code.
		Integration tests may not completely be able to meet the xcopy requirement, since they will often rely on external infrastructure, but this doesn't mean that you shouldn't adopt a set of similar principles.
	blogs.msdn.com /ploeh/archive/2006/11/15/IntegrationTestingPrinciples.aspx (741 words)

	Continuous Integration
		Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.
		Continuous Integration assumes a high degree of tests which are automated into the software: a facility I call self-testing code.
		Continuous Integration is all about communication, so you want to ensure that everyone can easily see the state of the system and the changes that have been made to it.
	www.martinfowler.com /articles/continuousIntegration.html (7360 words)

	Object-Oriented Testing, Part 1
		The problem of testing function calls in OO is the same as testing code that takes a function as a parameter and then invokes it.
		The test inputs may be appropriate for both classes, but the expected results might differ in the derived class.
		But simple tests tend to find only the faults you specifically target; complex tests are better at finding both those faults and also stumbling across other faults by sheer dumb luck.
	www.testing.com /writings/1-fault.htm (1390 words)

	ONJava.com: Automating EJB Unit Testing
		Although using a server-side testing framework to test EJBs looks more comfortable, from our experience in terms of unit testing, the outside container testing is safe enough for programmers to prove the beans are still working as expected during development.
		When we say unit testing as in the title of this article, we actually mean a little bit more than the original rigorous definition of unit testing, which is commonly limited to the class level in Java.
		By "integration," we mean at the time beans from different developers are integrated together and integration test suites are run, since beans may behave differently when assembled together.
	www.onjava.com /pub/a/onjava/2003/02/05/automate_ejb.html (1021 words)

	shocks - Unit, System and Integration Testing
		Integration Unit Tests, which ensure that two or more Objects function together as they are supposed to.
		My guess is that, like all feature platforms, a pluggable testing platform could be built on top of the internal framework which (to take a page from the REST architectural style) could monitor the state of the representation throughout the different stages of workflow by using Filters (more specifically, FilterSupport implementations).
		Testing a JSP means ensuring the JSP code itself works, but also it validates the underlying beans, and maybe the struts if it's used.
	blogs.codehaus.org /projects/shocks/archives/000516_unit_system_and_integration_testing.html (967 words)

	Strategies for Integration and Interoperability Testing
		Testing with other applications that have met compliance standards; the ability of two or more systems or components to exchange information and to use the information that has been exchanged.
		As low-level tests are performed and passed in the development environment, they are migrated to the system test environment for integration testing.
		The integrated domain is inherently risky and there is a tension between interoperability standards and the freedom to innovate and deploy new technologies quickly.
	www.riceconsulting.com /articles/integration_interoperability_testing.htm (1924 words)

	Meeting the challenges of integration testing- ADTmag.com
		First, integration project architectures are message-based, not code-based, and the failure points are generally in the messages, not in the code as they would be in an application development project.
		As I mentioned earlier, the testing is message-based, there may be many different protocols to test and there is the logistics challenge of having all the components ready.
		We think that integration projects are going to force application developers to come out of their cocoons, and to understand and work with the larger enterprise context.
	www.adtmag.com /print.asp?id=7962 (773 words)

	[No title]
		Testing can find defects whose consequences are obvious but which are buried in complex code.
		Drivers in bottom-up testing have a similar role to stubs in top-down testing, and are time-consuming to write.
		Advantage: Each piece being tested is complete in itself Problem: Need to write lots of drivers, functionality may not be easy to visualize¡XteüC * e ü § Õª$I ó0¨Sandwich testing ¡ § ª ¨ Sandwich testing is a hybrid between bottom-up and top down testing.
	www.se.rit.edu /~se361/slides/TestingPhases.ppt (947 words)

	Integration Testing \| Non-Functional Testing - ReadyTestGo
		Our software integration testing services are designed with the objective of ensuring that every component system, from source to destination interacts seamlessly with other components.
		Our integration testing team, with a mix of domain and technology experts, test the system right down to the internal functionality and integration of the supporting systems.
		Integration testing of the payment transaction system with 45 external applications helps a leading bank go live in 4 european countries - A case study
	www.readytestgo.com /integration-testing.htm (164 words)

	ploeh blog : Integration Testing WCF Services
		This would allow you to keep unit testing your operation implementations, but obviously, you also need to test the authorization manager itself, and it turns out that integration testing is the easiest way to accomplish this task.
		For this reason, integration testing is the most efficient approach to testing a custom authorization manager, and indeed all code involving operation context in general (such as message interceptors, etc.).
		The integration tests should follow my principles for integration testing, which in this case are pretty easy to accomplish because WCF allows you to host a service in any managed process.
	blogs.msdn.com /ploeh/archive/2006/12/04/IntegrationTestingWcfServices.aspx (2272 words)

	the { buckblogs :here }: Integration Testing in Rails 1.1
		Integration tests are a new feature of Rails 1.1 that take testing your applications to a new level.
		Integration tests are broad story-level tests that verify the interactions between the various actions supported by the application, across all controllers
		Jamis, these "integration" tests are really nice and I think they hit a sweet spot in between exercising a large portion of your application without requiring too much testing infrastructure.
	weblog.jamisbuck.org /2006/3/9/integration-testing-in-rails-1-1 (1957 words)

	Software Component Integration Testing
		The software components themselves may be specified at different times by different specification groups, yet the integration of all of the pieces must work together under the rules of a new or revised system specification.
		The feasible processes of object-oriented software can then be represented as data flows on a directed graph, where nodes are determined from states, guards, and transitions of the finite state machine, and where edges are determined from data and control flow resulting from method invocation.
		An overall goal is to automate the entire process so that test cases can be derived directly from an arbitrary object-oriented specification, such as those using UML modeling facilities.
	www.itl.nist.gov /div897/docs/software_test_statistical.html (452 words)

	System Integration Testing Services
		As an independent testing unit with intimate knowledge of the products to be tested, direct contact with the development teams, and field-proven testing methodologies supported by procedures, tools and libraries, we are able to ensure that communication service providers meet their business objectives, with a shortened time to production and reduced testing costs.
		We have also developed a structured and field-proven testing methodology that is supported by procedures, automated tools, testing scripts and libraries.
		Regardless of the scale of the testing project, whether for a specific area or an end-to-end solution, our level of involvement in the project is geared to match your particular needs.
	www.amdocs.com /page.asp?ID=754&SID=754 (522 words)

	Efficient Integration Testing using Dependency Analysis
		Test teams therefore add an integration testing step to their process to ensure that programs will continue to operate with different versions of the external subsystems.
		As full testing may take days or weeks to run, it is useful to understand how to prioritize these tests.
		We present an integration testing system to understand and quantify the impact of a change, so test teams can focus their testing efforts on the most likely affected parts of the program.
	research.microsoft.com /research/pubs/view.aspx?msr_tr_id=MSR-TR-2005-94 (342 words)

	Integration Best Practices - Testing The Limits of Integration - ebizQ
		Since integration platforms were new, the number of applications being connected was often limited, and development and deployment of integration solutions were tightly controlled and thoroughly engineered.
		More and more companies are using integration platforms to connect a larger number of databases and applications in different deployment scenarios.
		Any while integration products have evolved to meet these types of needs, often through the addition of capabilities such as business process modeling, business activity monitoring, more flexible adapter models, better abstraction capabilities and increased commitments to industry standards, there’s another important component of an integration solution that organization must think about in advance: testing.
	www.ebizq.net /hot_topics/int_sbp/features/1484.html?rss (480 words)

Try your search on: Qwika (all wikis)