Synchronization with the component under test

By default, component tests and stubs are automatically synchronized with the components under test (CUTs). This allows you to create the component tests early in the development cycle without worrying about updating your tests each time your application changes.

Testing your software components throughout the development cycle is the best way to avoid regression defects. You can create components tests for critical application components even before you develop the actual components, using stubs if necessary.

During the development phase, you might need to change packages, names, or method signatures of some components. These changes need to apply to both your component tests and stubs.

Project monitoring

The project monitoring feature applies only to synchronization between stubs and the component under test. When a project is added to the scope of a test project, the project can be flagged for monitoring.

The monitoring property is an attribute of the project containing the component under test. This means that if a monitored project is in the scope of several test projects, it will be monitored by all test projects.

To apply changes to the monitoring property, you need write access to the .project file for the project, which is located in the workspace. This can be a problem when using source control, because the .project file must be checked out before you can make any changes.

Whenever a project is added to the scope of a test project, you are asked if you want it to be monitored for test synchronization. A preference allows you to enable or disable this window. You can manually change the System Under Test Monitoring property at any time in the properties for the project.

Related tasks
Enabling synchronization of stubs with a project
Related reference
Component test general preferences
Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.