| org.apache.cactus.ServletTestCase
 org.apache.cactus.sample.servlet.unit.TestClientServerSynchronization
| TestClientServerSynchronization | | public class TestClientServerSynchronization extends ServletTestCase (Code) | | Verify that the Cactus client side only reads the test result *after* the
test is finished (ie after the test result has been saved in the application
scope). This JUnit test need to be the first one to be run. Otherwise, the
test result might be that of the previous test and not the current test one,
thus proving nothing !!
version:
$Id: TestClientServerSynchronization.java 238816 2004-02-29 16:36:46Z vmassol $ |
| Method Summary | |
| public void | testLongProcess()
Verify that the test result can be returned correctly even when the
logic in the method to test takes a long time and thus it verifies that
the test result is only returned after it has been written in the
application scope on the server side. | | public void | testLotsOfData()
Verify that when big amount of data is returned by the servlet output
stream, it does not io-block. |
| testLongProcess | | public void testLongProcess() throws Exception(Code) | | Verify that the test result can be returned correctly even when the
logic in the method to test takes a long time and thus it verifies that
the test result is only returned after it has been written in the
application scope on the server side.
exception:
Exception - on test failure |
| testLotsOfData | | public void testLotsOfData() throws Exception(Code) | | Verify that when big amount of data is returned by the servlet output
stream, it does not io-block.
exception:
Exception - on test failure |
|
|