In this section:
Parasoft Virtualize can record database queries, along with their corresponding results data, and use that in order to virtualize the data connection. This enables you to decouple your application from database dependencies while working on testing and development activities. Such decoupling alleviates challenges associated with test data management challenges and multiple teams competing over the same database assets, which can often introduce complexity and instability into the environment. Furthermore, being able to virtualize database connections allows load tests to scale better in such environments—without requiring you to allocate or license additional database instances for such purposes.
There are three main steps involved in virtualizing database behavior:
- Capturing the SQL queries that are passed to the database and the result sets that are returned—see About Database Recording below.
- Creating SQL Responders to virtualize the captured behavior—see Creating SQL Responders from a Database Recording.
- Deploying the SQL Responders as a virtual asset—see Deploying Virtual Assets.
About Database Recording
To enable database virtualization, the Parasoft JDBC Driver records live database behavior so it can be virtualized. This driver is described in detail in Using the Parasoft JDBC Driver.
To prepare for database recording, you go to the application server upon which the Parasoft JDBC Driver is deployed, then set it to record mode as described in Recording Queries and Data.
Once the environment is ready to capture traffic, the Parasoft JDBC Driver captures the SQL queries that are passed to the database and the result sets that are returned for the use case or test scenario being executed.
Converting Database Recordings to Virtual Assets
The captured data can be used to generate a virtual asset with a SQL Responder tool. This allows the team to access this database behavior without having to access the database itself. For details, see Creating SQL Responders from a Database Recording.