In our project whenever we get META Response from VSE we don't have clue whether elements added/deleted or value changed from existing stubbing. This is taking too much time to triage and fix the issue. IN order to save the time weare planing to to write utils in SDP to find closet match from incoming request to Stateless transactions from VSI and provide the difference to the users. Please let me how we can get all the stateless transaction in List<com.itko.lisa.vse.stateful.model.Transaction>.
DevTest Version 10.1
VS-->Inspection view can provide why the specific match is not happening if you turn on DEBUG in logging.properties.
Other than the above may be customization is feasible, need to work with CA Services but as is DevTest doesn't provide the functionality you are looking.
Thanks for reply, So we can get all the stateless transaction in List<com.itko.lisa.vse.stateful.model.Transaction> in SDP? Can you confirm this?
Without adding a customization, there are no public methods that return a List object containing the stateless transactions. The logic would have to iterate the VSI and perform what amounts to the exact same comparisons that DevTest VS Image Selection processing logic performs -- DevTest does this using multiple threads for performance reasons.
It is one thing to create a customization that matches the incoming request argument list (number of and names) to the argument list (number of and names) contained in the VSI. It would require much more complex logic that takes into consideration the argument list and applies Comparison logic (equal, less than, greater than, Regex, Property expression) and Match Styles (operation, signature, exact). Also, you need to consider the affect that DPHs have on the incoming request (removal of arguments, addition of arguments, etc.) and how your logic would cater for those scenarios.
Where would you anticipate adding this type of customization? As Prema pointed out, the inspection view in Portal provides some insight to this. Perhaps, parsing of the vse_matches.log into a tool such as Splunk or Elastic Stack could give some insights.
I am planning to add this logic in SDP Script when response from DevTest is META( ((com.itko.lisa.vse.stateful.model.Transaction) testExec.getStateObject("lisa.vse.matched.transaction")).getParent()==null ) then I would like our utils tell us what could close matches from VSI