A malformed test object with no name (which we expect to be the method, but which isn't set if you use the default c'tor to make your test) can hang the test infrastructure indefinitely, because reportResultsAndGetNextMethod throws and causes retries from the client, including for timeout status reporting.  This flags that problem up front and fails, which is what the test will do in execution anyway (because without a name we don't know what method to run).

Review by: bobv

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@3809 8db76d5a-ed1c-0410-87a9-c151d255dfc7
1 file changed