What type of designs are needed to write integration test cases?

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Testing and Quality Assurance Why do performance testers write new scripts so often? How to create performance testing workload models Fixing Web application performance troubleshooting problems Expert advises on implementation of Selenium IDE for effective software testing When should regression testing occur in an automated test plan? Achieving peak performance in integration testing Getting answers about OpenSTA script problems Defining core software regression tests Breaking in functionality on UI application pages Where to find good methodology guides for software testing Software integration testing Ajax testing: Using available tools is key Building, using tests on Microsoft Visual Studio Team System Configuration testing: QA pros discuss 10 things you may not know What is system integration testing? Who is responsible for integration testing, developer or tester? How to develop a checklist for unit, integration and system testing Integration testing: Is it black box or white box testing? How to use tools for system integration testing An approach to integration testing Unit, integration testing first steps toward SOA quality Software Testing For Agile Teams and Testers How to test usability for a positive user experience Data warehouse/BI performance testing tool recommendations Free Web-based GUI test automation tools Integration testing: Is it black box or white box testing? The future of software testing Software testing methodologies should match context Soak testing and performance testing terms Regression testing is more than retesting

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary continuous integration  (SearchSoftwareQuality.com) integration testing  (SearchSoftwareQuality.com) V-Model  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

The answer to this depends on the goals of the integration testing, the scope of the components being integrated, and the complexity of the technology and problem being solved. Integrating two Web services that pass a single piece of information between them is different than two real-time systems that stream data in both directions. On top of the question of scope, what's "required" is often dictated by the project context, not necessarily the type of testing taking place. That is to say, the exact same testing problem at two different companies (say a startup and a government project) will require entirely different sets of documentation as evidence that proper testing took place, or possibly that testing can even begin.

To answer this, I'll take a different approach. Instead, let me tell you what I look for when I'm doing integration testing. I'm often looking for disagreements between the parts. To be able to test for those disagreements, it's often helpful to understand what's supposed to happen. There are a number of ways I can develop my understanding of what the various components should be doing.

I can learn about expectations for the interaction based on:

• my understanding of the business problem trying to be solved.
• conversations about the functionality with other people on the project team.
• design documents for the components, the integration or the system in general.
• mapping documents or data-flow diagrams that show how information is moved through the components and what transformations take place.
• state diagrams that show what events take place and when.
• database, XML and other data schemas used in the process.
• other testing I've done or reviewed (at the unit level or system level).
• other similar types of integration I've worked with on past projects.
• and the very last integration test case I've executed (because I'm always thinking of new tests as I'm executing tests).

I suspect I even missed a couple of things I do to come up with test case ideas when I'm doing integration testing. The point is, there are a number of ways you can come up with your integration test cases, only some of them are requirements or design documents. Your project development methodology will likely dictate what's required, but that doesn't mean it's either sufficient or useful to actually accomplish the testing you'll be doing -- it does typically indicate that in the past those documents have been found helpful when solving integration testing problems.