Table of Contents:


Adding a Connection Profile

Before adding a connection profile, you need to setup a Data Catalogue. To do this, select 'Catalogues' under the 'Data Catalogue' tab in the left side menu, here, you can add, save, delete and rename your Data Catalogues.

To add a new connection profile, click on 'Connections' under the 'Data Catalogue' tab, click on 'New Connection' and a popup will show:

Enter the following into the popup:

  • Name – Give the connection a recognisable and unique name.

  • DBMS Type – Select required type from the dropdown list.

  • Connection String – Use a standard Java connection string.

Some example connection strings are:

Data Source=xe;user id=iban;password=iban;
server=BIGONE\SQL2016;user id=sa;password=xxxx;database=AdventureWorks;

This field can also be left empty if you choose to override the Test Modeller server, it is this server that connects to the database.

To override the connection string, navigate to: C:\VIPExcel\Configuration\VIPTDM\DataAllocation\LocalConnections.xlsx

This Excel contains the override connections. Note that the third expression has been encrypted using the VIP Encryption Feature.

The allocation process will check if there is a connection name match and then substitute in the connection details from this file.

When you are running the allocation it is entirely possible to connect to a database with the name that is hosted on multiple different servers. For example, our Splendid database has a DEV server, QA server, a cloud UAT and a cloud Production server.

Next, enter the Database Name and Schema Name, you may leave these empty if you wish. These are the values that get substituted into the SQL that is run.For example, when the tool creates the SQL to find the data it will add in the database.schema to the Table Names:

Enter: SELECT FIRST_NAME FROM splendid.dbo.LEADS

When you connect to a database you can specify the database as part of the connection string and set a default schema to autocomplete the schema and database fields. For example, Oracle will link you to specific schemas so there is no need to enter the schema and database name in the connection details.

You may need to set up a few simple SQL queries to test that the connections and the parameters are working correctly together. Don't worry it may take a couple of goes to get it right.


Managing Database Connections

Firstly, we will cover how to define SQL queries and link them to development and testing environments.

Before you can create a new SQL lookup you need to define what databases it will be connecting to. To do this, click on Connections in the left side menu:

This will open the list of current connections, here you may activate, edit, create or delete connections.

SQL needs to run against specific databases and different database types. Inside Test Modeller you need to create connections that are linked to each SQL query that will be run to find the test data. Before you begin adding in connections and SQL to Test Modeller use an SQL Management studio to test run the SQL. This will check the validity of the syntax and make sure you can connect to the databases being used by the application under test.

The example above shows the SQL Server Management studio running SQL to find leads for testing a CRM system.

TEST DATA AUTOMATION TEST DATA ALLOCATION DATA CATALOGUES