I'm willing to live with that risk. It's already kind of crazily belts-and-suspenders to have all the redundant invocations of PanelTestBase via subclass. It would make more sense to just test Panel directly, and rely on subclasses that override the bits it tests to provide their own tests for their new code paths. But today isn't the day to change that.
By that reasoning, since RootPanel just inherits the default behavior, it should be satisfied with the default coverage. http://gwt-code-reviews.appspot.com/612802/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
