Hi Sumeet. That's an interesting idea. The easiest way to do this would be to write a simple vAPI script to call the /reports/generate-report-unique endpoint to find which bins are uniquely hit in the failing cases. Whether it really produces useful data is to be seen... :) When submitting the request to the server, you'd use the rs1 to select failing runs from session, and rs2 to select the passing runs, and set the oneWay attribute to true so that it only shows you bins that are unique to the failing runs.![]()
↧