Setting configuration management preferences in the QM application

Set preferences for projects that are enabled for configuration management. For example, if the test results or test execution records from one project do not matter to another project, you can exclude them when you create streams from baselines, merge a baseline to a stream, or clone artifacts from a baseline of a component. You can change these settings as needed for a specific task, and change them back when you finish that task.

Before you begin

  • The quality management (QM) project area must be enabled for configuration management. See the related topic.
  • You must have permission to modify the project area properties.

About this task

Because test execution records might indicate an environment and an iteration, you can choose to exclude these records for tests for a different environment.

By contrast, if you start a new round of testing using the same environments (and even iterations), you might choose to keep the execution records (clear the check box for the records), and exclude only the results (select the check box for the results).

Procedure

  1. Click Administration Administration menu > Manage Project Properties.
  2. In the Properties section, click Configuration Management Preferences.
  3. Set preferences. Remember, each test result references an execution record, so if you exclude the records, the related results are also excluded.
    • Exclude from new streams: A new stream will not copy this information from the parent stream or baseline. Examples:
      • For a new version of a product for a different region, the information from other regions might not matter.
      • If your stream is similar to the parent, such as in a maintenance release, you might want the information from the parent baseline.
    • Exclude when you merge into a stream: This information is not merged from the source baseline. Example: The information from a maintenance stream might not be useful for a development stream.
    • Exclude when you clone from a component: This information is not copied from the source baseline into the target stream. Reuse only the test artifacts, when you clone test artifacts from a baseline of a component. Examples:
      • Clone an Engine component to start a different one, such as a new hybrid engine that meets stricter emissions standards. You might exclude the original test results and records because they aren't relevant to the new hybrid engine.
      • If you are splitting a larger Airplane component into smaller pieces such as Engine, Fuselage, Wing, and so on, you might keep this information so that you have the test history after you reorganize the project.
  4. Click Save.

Results

The settings are applied immediately. If you change a setting to achieve different results for a specific task, remember to return to this page and revert the setting to the preferred value for your project.
Example: Typically, your team excludes test results and records when cloning from a component. However, you decide to split an existing component into smaller pieces, and you want to keep the test history. You created the new components and are ready to clone the artifacts:
  1. Go to the Manage Project Properties page and click Configuration Management Preferences.
  2. Change the settings for this specific cloning task: in this case, clear both Exclude when you clone from a component check boxes.
  3. Clone the artifacts from the original component into the new ones as needed.
  4. Return to the Manage Project Properties page and change the values back: in this case, select both Exclude when you clone from a component check boxes.

What to do next

To resume working on test artifacts, select a QM project from the Home menu. Then, choose a component and configuration from the menus on the toolbar.

To create components, streams, or baselines, click Administration Administration menu > Manage Components and Configurations.