/
Reuse Existing Assets to Create Structure Diagrams Automatically

Reuse Existing Assets to Create Structure Diagrams Automatically

Over the past years numerous importers have been developed to create structure diagrams and from various existing assets such as automation information (like framework functions, object repository recordings from various test automation tools like HP UFT/QTP and Tricentis Tosca, etc), application information (like WSDL versus WADL versus OpenAPI web service definitions, SOAP versus JSON web service captures, etc), simple Excel based interface specifications (GUI versus mainframe interfaces), etc.

Recommendation: Instead of starting with an empty project and blank initial structure diagrams, save valuable time in modelling, and reduce time to eventually automate execution of generated tests. Make use of various importers to complement or even just create a starting point for interface object specification in structure diagrams.

If you have any automation or application assets in a format which is currently not supported by importers reach out to support@conformiq.com for help.

Importers generally expect input sources to be provided to follow a correct format. In particular when it comes to failures in web service definition imports, the validity of the source should be checked with 3rd party tools.

Recommendation: Use online web service definition validators available or other 3rd party tools supporting the file format to be imported to ensure that interface definitions to be imported comply to the respective standards.

When creating structure diagrams from external sources care should be taken to import only the relevant parts of the interfaces, i.e., avoid importing complete web service definitions but instead import only the message and information elements you need from a definitions file, or do not import complete web pages modify object repositories to only contain the widgets you need for modeling the functionality to be tested. Notice this also helps to reduce model complexity.

Recommendation: Restrict the import of interface information to only those definitions, e.g., message, parameters, widgets, etc required for modeling the functionality to be testing in the current Creator project.

 

 

Related content

Impact of Model Size on Test Generation
Impact of Model Size on Test Generation
Read with this
Reuse Existing Assets to Create Models Automatically
Reuse Existing Assets to Create Models Automatically
More like this
Test Generation
Test Generation
Read with this
Use Structure Diagram (SD) Libraries to Reuse Interfaces across Multiple Projects
Use Structure Diagram (SD) Libraries to Reuse Interfaces across Multiple Projects
More like this
Modeling Interfaces
Modeling Interfaces
Read with this
Only Model Items Required for Functional Testing
Only Model Items Required for Functional Testing
More like this

Copyright © 2023 Conformiq and its subsidiaries. All rights reserved.