This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
This guide describes the tasks that you can perform for using virtual services or stubs to simulate parts of an environment if the real services are not yet available or because they are difficult or expensive to use. This guide is intended for API Testers.
You can create and modify database stubs in HCL OneTest™ API.
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing. This guide is intended for API testers.
HCL OneTest™ Virtualization is software that is used for creating, maintaining, publishing, and running message-based stubs and database stubs.
You can use the HCL® Quality Server Environments dashboard to perform various tasks such as starting, stopping stubs and scenarios, and modifying stub configurations after you have published stubs to HCL Quality Server. You can also lock the environment that contain the published stubs.
You can simulate an HTTP connection with a virtual service, also known as a stub.
You can simulate an HTTPS connection with a virtual service, also known as a stub.
You can simulate a TCP connection with a virtual service, also known as a stub.
You can virtualize REST APIs by using the Recording Studio, or by synchronizing WADL, Swagger, or RAML documents. When none of these options is available, you can still manually virtualize REST APIs that use path parameters.
In HCL OneTest™ API, there are several methods that you can use to create a message-based stub.
You can use either the Test Editor or the Stub Editor to create, modify, and enhance any legacy or new stubs created by HCL OneTest™ API.
Before creating any database stubs, you must complete any required software installation tasks and set up the schema that is used for stubbing a physical database.
If you want to create a test or suite of tests for an application that uses a database, you run the test (suite) in a repeatable fashion against a known set of database contents. Therefore, you must stub the database to obtain repeatable conditions. Database stubs enable you to execute tests against some parts of a system under test without affecting a live database.
Database stubs created in HCL OneTest™ API can be non-persistent or persistent.
The HCL OneTest™ API JDBC proxy package is provided with HCL® Quality Server. You must deploy the package on any stand-alone applications, or application servers that host applications that use JDBC to access any live databases that you want to record or virtualize.
If you are using HCL OneTest™ API 8.0.1 or later, you can record and virtualize most stored procedures.
You can find information about the data types supported for database management systems in HCL OneTest™ API.
A synonym is an alias or alternate name for a table, view, sequence, or other schema object. HCL OneTest™ API 8.5.1 or later supports certain synonyms for some supported database management systems.
You use the Recording Studio perspective of the HCL OneTest™ API to create a database stub while SQL events are being recorded from a database.
You can modify database stubs in HCL OneTest™ API.
A stub running on its own may not be sufficient in some cases, because it might have dependencies on services such as HCL® Quality Server or the HTTP proxy. If the stub is running on the public cloud and the services are running in the enterprise, you must configure the stub to connect to these services.
You can publish stubs that are created in HCL OneTest™ API to HCL® Quality Server, Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
You can use HCL® Quality Server to display the results of tests that you run in both HCL OneTest™ API and HCL Quality Server.
HCL® Quality Server collects and stores usage metric data. The metric data might include the number and types of actions that are used, the features that are used in the workbench, details about Operating System or languages set while running, and so forth. You cannot view the metric data on the HCL Quality Server user interface, but it is available from the underlying implementation. Storage is either managed by H2 or optionally Apache Cassandra.
All the project stakeholders can view test reports for multiple testing products from the Results page on HCL OneTest™ Server. You can access the Results page from a web browser. Therefore, there is no need to install the desktop client.
You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.