You can add stubs from external mocking tools to use those definitions as Mock Services in BlazeMeter.
The following external tools are supported:
You can add the Transactions by exporting them to a JSON file or by uploading them to the Transaction repository directly from the code.
Note: In-code import requires the Transaction Repository extension, which is coming soon. Until then, only exporting to JSON is supported.
Exporting Transactions to a JSON file
Export virtual endpoint definitions from your code into a JSON transaction file, which you can then import into the Transaction Repository through the Mock Services UI. Using this method, developers using mocking tools can share the artifacts they created in their code with other team members who can load them into the Mock Services UI, augment them as needed, and run them as Mock Services hosting the content imported from the code.
Note: The vanilla Wiremock library lets you export a JSON DSL file using the WireMock.saveAllMappings(); method. Any file exported using this approach could be imported to Mock Services.
After you export the definitions into JSON, you can add them as Transactions from a file to the Transaction Repository.