Depending on what you actually want to test, you have several options. You could write a JUnit test (see my recent test for LocalAccess). This typically tests behaviour of one class in isolation. IF you have a more complex scenario, i.e. you need Jini infrastructure (class servers, lookup service, etc), you could write a QA test.
2010/9/11 Patricia Shanahan <[email protected]> > I'm looking for documentation, guidance, or even a good example for River > test construction. > > My tests only need one JVM - although I'll use multiple threads to set up > concurrency stress for e.g. TaskManager. It looks as though some of the > existing qa classes might be useful, and I don't like duplicating code, but > I'm not sure how to use them. > > Patricia > > >
