Run database query, add validations, and extract values

Learn how to connect to database and run SQL queries in Low Code Automation to validate data and extract dynamic values.

This feature lets you connect and query your databases directly in Low Code Automation. There is no extra backend setup needed outside the Low Code Automation platform. You can effortlessly run SQL queries within your automated tests, validate backend data in real-time, and extract dynamic test data. This eliminates the need for extra handling and streamlines your testing process.

Supported databases

Low Code Automation currently allows connections to the following databases:

• MySQL
• PostgreSQL
• Microsoft (MS) SQL
• Oracle DB

Prerequisites for internal databases

You can connect Low Code Automation to internally accessible databases that are not publicly accessible. An internal database is any database that is only accessible within your organization’s internal network or through a VPN.

This section explains how you can run tests with an internal database, both locally and in the cloud.

Local execution

• Ensure the system running your tests has access to the internal database.
• If needed, connect to your VPN before starting the test.

Cloud execution

• Start the local binary before the test suite begins. The local binary should be started without specifying an identifier.
• For scheduled runs, make sure the local binary is running and connected.
• The system running the local binary must have access to the internal database.
• The database hostname should be accessible from your system.
• Refer to Local Testing setup documentation for detailed steps.

After you complete the prerequisites, go to Low Code Automation and follow these steps to connect your database.

Configure a new database connection

To execute a database query while recording a test, you need to first set up a connection between Low Code Automation and your existing database.

1. On the recorder, click the ︙ icon and click Run database query.

2. In the Connect database section, select the database type.

3. Alternatively, click + Add new connection.

4. In the New database connection window, provide the following details:

• Database type: Select the database you want to connect to from the list. Currently supported databases are: MySQL, PostgreSQL, Microsoft (MS) SQL and Oracle DB.
  • Connection name: Enter a name to identify this database connection.
  • Test description (Optional): Add a description to help you or your team understand the purpose of this connection. For example, Test environment for login module.
  • Hostname: Enter the hostname or IP address of your database server.
  • Port: Specify the port number used to connect to the database.
  • Database name: Enter the name of the database you want to connect to.
  • Username: Provide the username with access to the database.
  • Password (Optional): Enter the corresponding password for the username provided.

5. Click Test & connect. This verifies the connection details you’ve entered. If the connection is successful, your database will be linked to Low Code Automation and ready for use in your tests. To run the query, refer to the Run a database query section.

6. Another way to configure a database connection is through the Database section. In the left pane, expand Data configuration and click Database. Then, click +Create new connection and follow the same steps as previously described.

Run a database query

Once the connection between Low Code Automation and your database server is successfully established, you can run queries during test recording.

1. In the recorder, click the ︙ icon and select Run database query.

2. Under the Connect database section, click Connect next to the database you wish to connect to.

3. Enter the query you want to execute and click Run Query.

The results are fetched and appear in a table format.

4. You can then add validations or extract values from these results as needed. Additionally, you have the option to import variables if required by clicking the + Import variable option.

Users should be able to select an existing database connection and execute SQL queries on that database. There are no built-in restrictions to block write operations in SQL queries. Please ensure the connection is configured with a user that has the required access controls.

Manage database connections

To view and manage your database connections in Low Code Automation:

1. Navigate to Data configuration > Database. It displays all the database servers connected to your Low Code Automation account. The list shows the database name, the tests linked to each connection, and information on when and by whom it was last updated.

2. Click the ︙ icon next to the database connection to perform one of the following actions:

• Edit connection: You can modify the connection details. Note that editing a connection affects all tests linked to it.
  • Delete connection: You can remove a connection only if it is not linked to any tests.

Points to remember

• Query results are limited to a maximum of 100 rows and 40 columns.
• A single test can be connected to multiple databases.
• When using database calls in high-concurrency scenarios such as data-driven testing, ensure that the database can support the expected connection load.

Troubleshooting

• If the connection fails, edit the database connection and check the following:
  • Credentials: Verify the username and password are correct.
  • Database name: Double-check the database name.
  • Connect to the database: Click Test & connect button to re-establish the connection.
• If you cannot connect to your internal database, check the following:

  • Network access: Ensure you can ping the database hostname from the system running the local binary. Use the ping command to verify database connectivity:

    • macOS:

      ping <database-hostname>
    

    • Windows:

      ping <database-hostname>
    

  • If the ping fails, check your network, VPN, or firewall settings.

• Concurrent access: If you are also connecting to an internal website, the system running the binary must have access to both the internal website and the internal database.