Building system models by using synchronization

When design-time assets are available, building by using synchronization is the preferred technique. Synchronization builds the system under test for you, which simplifies your testing work.

The Architectural School perspective is used to build a simple, graphical view of the system under test. The main aim of building this system model is to understand and validate the dependencies, interactions, and constraints between the interfaces. By itself, the system model does not contain enough information to be testable. To enable the creation and execution of tests, the configuration details of the infrastructure components that make up the logical system must be provided. HCL OneTest API provides this synchronization capability to simplify this process. Synchronization does the work of building the system under test and automatically adds logical and physical components, dependencies, and interactions.

Consider the following points:
  • Use the synchronization process for modeling and testing web services.
  • After the synchronization is complete, verify that the components are synchronized. You can verify the services, operations, schemas, dependencies, and their interactions. This stage is a checkpoint for you to decide on one of the following course of action:
    • Move forward to the next phase of activity, such as recording initial messages and creating tests
    • Revisit the system model to rectify the invalid or missing components