Hi,

We have added some tests [1] for the AeroGear Android Pipes. The tests are executed on TravisCI [2]

Both [3] simulation tests (like those included inside the aerogear-android-integration-tests which simulate the HTTP response) and real tests (using a rest service which is deployed on a JBoss AS 7 instance on the TravisCI machine) are executed in each build.

The TravisCI build procedure is the following:

1. The Android SDK is installed on the TravisCI headless machine
2. An Android emulator is started (without skin)
3. The REST service is built. Jboss AS 7 distribution is downloaded
4. The JBoss Server is started. This script [4] waits until the server is started up.
5. The REST service WAR is deployed on JBoss AS.
6. The Android tests are executed inside the emulator

I'd like to add some cases to test the CORs support. Is there any specific configuration on pipelines/pipes or CORs is enabled and supported by default?

[1]: https://github.com/tolis-e/aerogear-android-pipe-tests
[2]: https://travis-ci.org/tolis-e/aerogear-android-pipe-tests
[3]: https://github.com/tolis-e/aerogear-android-pipe-tests/blob/master/aerogear-android-pipe-tests/src/org/jboss/aerogear/android/test/RestFullPipeTestCase.java
[4]: https://github.com/tolis-e/aerogear-android-pipe-tests/blob/master/wait_jboss_to_start_up

Thanks,
Tolis Emmanouilidis