Hello Peter Pan,
That is a fair question. There really isn't a better way, but I would like to suggest an alternative. First I'm assuming you spawned a secondary thread (a worker thread) to execute the test separate and independent from your UI thread. Have your UI thread set or clear some sort of a global RUN flag when your Stop/Abort button is clicked. Then have your testing thread periodically check this flag. When they see it set they should throw an assert. Any assert will do. That will cause the test to stop right there and do a full and proper cleanup.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items