| com.google.gwt.junit.client.GWTTestCase
 com.google.gwt.dev.shell.test.MultiModuleTest
| MultiModuleTest | | public class MultiModuleTest extends GWTTestCase (Code) | | Tests unloading individual modules when more than one are loaded on a page,
including in nested frames.
The test will load up the initial configuration, then when all frames are
done loading will toggle the first frame, then the second frame, then both at
the same time. Buttons are provided for manual testing.
Currently, there isn't much it can do to actually verify the proper behavior
other than not crashing (which does not verify that the removed module isn't
holding a lot of memory), but it is hard to do more than that without adding
a lot of hooks that would only be used for this test. When tobyr's profiling
changes are merged in, we will have to create some of the hooks to allow
calls into the external object which could be used for the hooks for this
test.
|
| getModuleName | | public String getModuleName()(Code) | | Get the name of the GWT module to use for this test.
the fully-qualified module name |
| testInnerModules | | public void testInnerModules()(Code) | | Create the DOM elements for the module, based on the query string. The top
level (query parameter frame=top) drives the process and sets up the
automated state transition hooks.
This function returns with no effect if gwt.junit.testfuncname is not
passed as a query parameter, which means it is being run as a real test
rather than as a "submodule" of testMultipleModules.
|
| testMultipleModules | | public void testMultipleModules()(Code) | | |
|
|