River Container Tests
=====================

/*
 * Licensed to the Apache Software Foundation (ASF) under one
 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership. The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License. You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */


This project contains integration tests that may be run remotely.

The container will be configured with a remote deployer that can be called to 
deploy a system archive that is physically accessible to the container (i.e.
we're not uploading the app, although this may be possible in the future).

The app in question will be a test runner interface that can run unit tests.
Basically you write your unit tests, then deploy them with the remote test 
runner library and call out the remote test runner app.

Then, you run a client JUnit test that calls the test runner app and reports the 
results that the remote test provides.

Alternative - build a container instance that contains the integration tests
to run, then have the JUnit test startup that container and wait for the results
to appear in a local directory.  That's the way it was done in Harvester, but
let's face it - we're going to want remote deployment eventually, so why not put
the infrastructure in place now?  Once we have remote deployment of a locally-
available file, it's a simple matter to add upload capability.