Master Suite Structure

The project contains the Master Suite that contains predefined web service requests and common groovy scripts.

The MasterSuite includes a suite of TestCases; execute them in the sequence they appear in the soapUI project.

The following screenshot from soapUI displays a list of TestCases:

The Master Suite Test Cases table lists and describes TestCases listed under MasterSuite:

Master Suite TestCases
TestCase Description
BaseActions Defines basic actions that should be executed before running a TestCase. For example, creating an enterprise, creating a user, or uploading metadata. You can execute these TestSteps as a web service request. For more details, refer to TIBCO MDM Web Services Guide.
GroovyUtils Includes groovy TestCases. For more information, refer to Groovy TestCases.
Common Actions Includes various common operations supported by TIBCO MDM and soapUI as TestSteps. It also includes Data Extractor based web service common operations. For more information, refer to CommonAction TestCases
Import Defines TestSteps to complete the Import action. Peform the following TestSteps in sequence:

Execute the import.

Transfer the generated event ID to GetEventDetails web service request.

Run the GetEventDetails web service.

Verify the status of GetEventDetails web service. It can have one of the following status: Success, Failed, or In Progress.

If the status is In Progress, you can delay the execution of this event. You need to specify the delay time in milliseconds.

When the TestCase is called from TestConfig.xml file, these TestSteps are executed in sequence.
ExportAndValidate Defines the TestSteps to export a repository. You can download and save the exported file. You can also compare and validate the file against a master file.
DQ Defines the TestSteps to run a data quality test.
  • SaveTestRunStatus: You can save the status of test.
  • ReloadToNetrics: To load or reload data from TIBCO MDM repository into the Netrics server. During the load or reload of data textIndexMigration.bat utility is used located in $MQ_HOME\bin. This utility deploys the IndexerConfig.xml file when data quality is used in OFFLINE mode.
  • CheckNetricsCount: Returns a number of records in the Netrics server entities. The step executes netricsServer.bat file located in $MQ_HOME\bin and compares the output.
SetPropsFromDB Defines the TestSteps to set the properties in a step depending on values retrieved from the database.