Ideally it says what the current max depth is and provides a link to rerun with a higher max depth or no max depth.

@scottgonzalez I've updated the PR. Screenshot:

1. Added maxDepth in url parameter, maxDepth = -1 implies run the tests without any maxDepth.
2. Although maxDepth = someVal in URL parameters will work, but not explicitly showing the option of inputting the value from user because the UI will be cluttered as we will need to add input box, button etc.
3. Showing QUnit.dump.maxDepth as hint, in case user wants to change maxDepth.
4. The color of Rerun looks dull in the message, any suggestions for a different color?
5. As QUnit.dump is not in scope when we are parsing URL params, hence I've added extra property QUnit.config.maxDepth.

@jzaefferer Please provide your valuable suggestions as well.

I think the tests are failing because of the timeout. How can I re-run the tests?

@shivamdixit thanks for the PR. I have very little bandwidth to review anything this week. I added one comment above. I'd like to discuss the general concept for tackling this issue, but that has to wait a few days.

That screenshot looks great. You should wrap QUnit.config.maxDepth in <code> instead of quotes.

Fixing the styling of the rerun link should be very simple, but let's wait for the team to discuss.

@jzaefferer @scottgonzalez Thanks for your suggestions. I've updated the code.

Let's add some CSS to display the Rerun link properly, just change color to something with more contrast.

How is it looking?

LGTM