As Shiney states, this is not an OOTB feature.
You can roll-your-own code to iterate the VSI (see example). Use a significant amount caution when you do these kinds of things because CA reserves the right to alter the structure and storage mechanism associated with DevTest assets at any time.
In the test case below, point the first step to the VSI you want to consume. The LASTRESPONSE from the second step lists the operations found in the VSI by navigating over the XML. Use the attached example at your own risk. This is not guaranteed to work on your particular VSI - although it did work correctly on my sample VSI.