Debugging a test with multiple iterations

Hello Dennis,

I am sorry to hear you are experiencing this behavior. 
If you are using local data there is no chance to run only the 24th iteration. If you are binding an external data such as excel file, xml, etc you can use to filter the data between rows and select only the data from the particular row to be executed.

For more details refer to the screenshot attached.

Regards,
Ivaylo
Telerik

Hi Ivaylo,

Thank you for your reply. I'm using local data, but I'm curious if a column could be added to the data table that would serve as an "active flag" for each row in the table. The active-flag value would be set to true for the row(s) that need(s) to be debugged (e.g., row 24) and to false for the rows that don't need to be run during debugging (e.g., rows 1-23 and 25). I'm guessing it would require a coded step, but I'm not sure how it would be constructed. Would this approach to work? If so, can you provide some guidelines?

Thanks,

Dennis

Just to be clear, I'm using a parent test to log in to a web site one time and a child test that iterates through various pages of the site. The child test is driven by the local data.

Hello Dennis,

Unfortunately the approach described with the local data will not work as you intend to, the only way to proceed will be as already shown with the filtering, however you need to use excel as a data.

Thank you for your understanding.

Regards,
Ivaylo
Telerik