Re: [aerogear-dev] Integration test execution policy on Aerogear
On Mon, 15 Jul 2013 09:46:25 -0400
Summers Pittman <supittma(a)redhat.com> wrote:
>
> 4/ Something else?
This is kinda similar problem in AG-Android. We have two sets of
tests. One is a Robolectric powered "unit" test suite which doesn't
need anything other than Java SE running. The second is an integration
test suite which requires an appropriately named AVD running and runs
the tests on the device.
So my something else may be a separate integration test suite project
which downloads internet - porn and runs the tests in a container. Of
course this adds to the project soup under AeroGear already.
This will work for blackbox integration tests. However, we have also whitebox
integration tests - e.g. we deploy only a few EJB/CDI beans that are part of the
implementation and see how they interact together. And such tests are hard
to keep in separate repo, as they'd get broken every refactoring and would need
awkward classpath setup.
I went such way in the past to add integration test to a project we had no
control of and it was a maintenance nightmare.
>
> WDYT? I'd like to reach an agreement so that the same policy could be
> applied across all Aerogear modules.
>
> Thanks,
>
> Karel
>
> [1]
>
https://github.com/aerogear/aerogear-unified-push-server/commit/e1651edb6...
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev