Skip to main content link. Accesskey S
  • Log In
  • Help
  • IBM Logo
  • IBM Notes and Domino Application Development wiki
  • All Wikis
  • All Forums
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
  • API Documentation
Search
Community Articles > Designing Applications > Designing Composite Applications > Designing composite applications: Unit testing
  • New Article
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

Click to view profileIBM contributorDeanna Drschiwiski
Contribution Summary:
  • Articles authored: 76
  • Articles edited: 227
  • Comments Posted: 8

Recent articles by this author

Getting started with XPages

Need help getting started with XPages? This guide provides links to overview content, videos, tutorials, and other content that will get you up to speed quickly.

XPages Domino Object Map 8.5.2

This topic contains a map of the domino objects contained in XPages.

Best practice to develop a good Notes application from the globalization perspective

This presentation shows the best practice to develop a good Notes application from the globalization perspective

Introducing of Domino Global WorkBench 8.5

This presentation shows how to localize Domino templates with Domino Global WorkBench 8.5

XPages Extensibility API Developers Guide

Welcome to the XPages Extensibility API Developers Guide; the Official Resource for Development using the XPages Extensibility API.
Community articleDesigning composite applications: Unit testing
Added by IBM contributorDeanna Drschiwiski on October 29, 2009 | Version 1
  • Edit
  • More Actions Show Menu▼
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: test
The ease with which users can assemble composite applications from components increases the need to unit test your components before users use them. This article, fourth in our series on composite applications, describes how to test your components prior to assembling composite applications.

Unit testing

The creation of composite applications differs from traditional application development in one important way: The development effort occurs in two stages. First, components are written, and then later are assembled into applications. This approach has several advantages. Because components can be reused in multiple ways, you optimize your effort with a "build once, use many" approach. Second, the task of assembling components is not as technical as building components, so a broader mix of people can be involved in the process. As a result, application development is brought closer to the end user, which yields application designs that build more upon domain expert knowledge.

With these advantages, though, come concerns that must be addressed. Because components are not custom built for specific uses, you must attempt to anticipate all scenarios. Because composite applications are being assembled later in the process by less technical people, components must behave consistently and predictably. Components should also have good documentation describing the valid values to pass to their interfaces.

One essential approach to ensure the successful development and deployment of components is unit testing. If the components are guaranteed to work well before they are deployed, there will be fewer problems and less frustration in the field when they are put together, providing a better and more cost-effective experience for all.

To read the entire article, see Designing composite applications: Unit testing on the developerWorks website.

Editor's note: This article is the fourth in a series of articles on composite applications to be published on developerWorks Lotus over the next few months. See the other developerWorks articles, "The Lead Manager application in IBM Lotus Notes V8: An Overview," "Designing composite applications: Component design," "Designing composite applications: Design patterns," "Designing composite applications: Writing an Eclipse component for IBM Lotus Notes", and "Designing composite applications: IBM Lotus Notes components".


  • Edit
  • More Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (1)Oct 29, 2009, 7:28:28 PMDeanna Drschiwiski  IBM contributor
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkThe Social Lounge
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use