Generate Tests for Specific Areas of Model

For the model to be “source of truth”, model must always be updated for any change in application behavior, so that the tests are always current. However, with such continuous changes, there may be a need to generate tests for specific areas/modules/flows of the application under test, and not the entire model itself. One of the possible use cases is targeting the areas where application is being modified as per the requirements of the particular sprint (Agile) / Release (Waterfall) and continue with per-sprint (or Release basis). Another use case may be targeting areas for sanity check (to generate tests for high-level end to end flow), or regression (to generate tests covering important functionality for regression testing), or Functional (corresponding to changes within the sprint/release) versus the entire application’s test suite.

Generating tests for entire application model might generate a lot of test cases, and the user might have to spend time sifting the entire suite for tests s/he would need for current scope of testing. Generating tests for every change during model development will also delay overall project timeline.

On the other hand, any approach where copies of the original model (either removing/deleting flows in AD for every change, or one copy for each targeted area) are created creates maintenance issues and is an inherently inefficient approach.

Using multiple Test Design Configurations (TDC) is a great way to meet this objective efficiently.

1.“Updated and Current” Test Suites generated for targeted areas. No sifting through a single large suite.

2. All changes are implemented on original, single model (or a group of models with exclusive functionalities), reducing maintenance tasks.

3. Additionally, starting with Creator 4.5.3 - test generation performance improves (ie., tests for targeted areas are generated in quicker time) with correct definition of TDC Test Target settings.

In contrary, for similar test generation times, the envelop of how much functionality a single model can hold is greatly enhanced when compared to splitting the functionality into multiple models. Please note recommendation of section Impact of Model Size on Test Generation is still applicable but can be implemented only if size grows beyond the control of multiple TDCs.

On versions 4.5.2 and prior, more than one TDC could be enabled at the same time. However, starting 4.5.3, only ONE TDC can be enabled at any given point in time.

See section Review Testing Target Settings before Analyzing Your Model and section Use Multiple Test Design Configurations to Optimize for Different Test Targets for more information on “Test Design Configurations”.