You can now use the Virtual TestNet API to enable a more efficient, automated way to manage your CI/CD pipeline.
The API allows you to run several important actions:
- Bulk cleanup: Delete any number of Virtual TestNets in a single API call. Set up a smooth cleanup process after running complex tests that involve multiple Virtual TestNets.
To make this process even easier, filter and reference the Virtual TestNets you want to delete using four types of IDs: Virtual TestNet ID, Virtual TestNet RPC, container ID, and access key. This way, you don’t need to know the exact ID to delete a Virtual TestNet but pass any of the above parameters. - Virtual TestNet search and listing: List all Virtual TestNets for a given project after completed executions. Compile all relevant Virtual TestNets with corresponding links and use them for reporting, tracking, or even cleanup. You can also use the slug filter for PR name partial matching to extract all Virtual TestNets within a specific PR.
- Transaction search and listing: List all transactions on a given Virtual TestNet and even filter them by address or status. Get a response with transaction links included so you can easily navigate to, for example, failed transactions.
- Virtual TestNet forking: Fork any block on Virtual TestNets using the Forking API. The original Virtual TestNet can be used as a template with the most recent contracts, while the forked instances can be used for local testing or CI runs.
To get started, check out the Virtual TestNet API documentation.
