I've been asking this question of applicants "How do you deal with slow-running (automated) test cases?" The answers I'm getting are very different than what I expected. Can you can help me create a better question?

The categories of answers seem to be *solutions* assuming 1) improper execution, 2) defects in SUT, 3) UI tests in selenium with locator issues.

I guess what I'm after is more about the personal process individuals use to determine if test cases can be sped up or what slow test cases are telling us. And then if they are telling us something, how we use that information.

I know many practitioners haven't necessarily defined their process for this explicitly, and I'm open to conversation during an interview where the individual begins making that process explicit. But I do wonder - am I asking too much of folks?

Is it fair to expect a person applying for "Senior Test Automation Engineer" position to be able to describe their process for this? And if so, what question can I script so that they understand what I'm asking for?