Page History

SOAtest and Virtualize come with skills to increase the capabilities of your AI coding agent when working with test scenarios and virtual assets over MCP. These skills are automatically available for desktop users; other users can install them from GitHub.

SOAtest Skills

The following SOAtest skills can be found in your workspace under /TestAssets/.github/skills.

soatest-scenario-execution

This skill is used to invoke a specific scenario. If the SOAVirt server requires authentication, the skill will obtain an access token and use it for subsequent calls to the SOAVirt server.

You can invoke the skill directly or by using a prompt like, "Execute the scenario with the id '/TestAssets/generated_by_mcp/MyTests.tst'."

soatest-guided-api-test-creation

This skill is used to plan and/or build testing scenarios for API services or endpoints. It is designed to be interactive and can use API definitions (OpenAPI, Swagger, WSDL, and so on) or work just with parameters you specify.

This skill only supports HTTP and HTTPS services.

It is recommended that you invoke this skill directly when you want to use it.

Virtualize Skills

The following Virtualize skills can be found in your workspace under /VirtualAssets/.github/skills.

virtualize-upload

This skill is used to help upload files from the local machine to the Virtualize Server. It is automatically used when the Virtualize MCP server directs the agent to upload files.

virtualize-stateful-virtual-service-creation

This skill creates a complete stateful virtual-service representation folder (MongoDB-backed, Parasoft/Virtualize-style responders) from an API definition (OpenAPI, Swagger, WSDL, and so on), a sample set of request/response files, or a description of the stateful service. This folder is then used by the manageVirtualServices MCP tool to create the stateful virtual service on the Virtualize server.

Before creating a stateful asset, you will need to configure the connection settings for a Data Repository Server that the MCP server can use.

You can invoke the skill directly or by using a prompt like one of the following:

• "Create a stateful virtual service called demoApp for service definition c:\temp\demo-app-v1.json."
• "Create a stateful virtual service using the sample request and response traffic pairs in the shoppingCartTraffic folder."
• "Create a stateful virtual service called shoppingCart. It should have resources for items, customers and carts. Items should have id, name and price. Customers should have id, name, email."

Be sure to include the word "stateful" in your request; the agent is likely to create stateless assets unless otherwise directed.

Note: Your MCP client might have trouble creating a stateful virtual service from more than a handful of request/response pairs. If you experience this, ask the client to create an API definition file from traffic files first and create a stateful service from that definition.

virtualize-stateless-virtual-service-creation

This skill creates a complete stateless virtual-service representation folder (a flat folder of fixed request/response file pairs - Parasoft Virtualize-style) from an API definition (OpenAPI, Swagger, WSDL, and so on), from a sample set of request/response files, or from a description of the stateless service. This folder is then used by the manageVirtualServices MCP tool to create the stateless virtual service on the Virtualize server.

Customizing Skills

You might want to customize one or more of these skills for your specific scenario or environment. It is important to remember that the default skills are reloaded every time the application is started, so any changes you make to them directly will be overwritten. Rather than making changes to these skills directly, you should add your own custom skills inside the associated skills folder as detailed above. You can invoke a custom skill directly to ensure it is used instead of the default skill.

You can also add your own custom instructions to a skill by creating a complementary instruction file (for example, my.instructions.md) and saving it in the instructions folder adjacent to the skills folder. It will be loaded and used alongside the default instructions file for the skill. As with the default skills, it is strongly recommended that you do not change the default instructions file. The steps for adding custom instructions vary by MCP client (for SOAtest desktop users, you can find this under Copilot > Edit Preferences > Custom Instructions). See the help file in Copilot for more information.