Do you really need to verify that the record was inserted in a separate test? The server-side code which inserts the record should be throwing an exception if the insert fails which means that your onFailure callback will run which should fail the test. If the backend database you are using for testing fails to insert a record without throwing an exception then your problem lies outside the scope of testing.
Even database clients that do not do explicit error-checking by default (e.g., MongoDB) have an option to force error-checking. This should be enabled by your testing framework before any test is run if that is the case. If you absolutely cannot get away from doing a manual insertion check why don't you just fire the record verification request from within the onSuccess callback of the original? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
