thanks for putting some test work together.
Looking at https://gist.github.com/kpiwko/5612949
, this reminds me of what
I have called "integration tests" in previous projects. This is great and
--> that way you can _really_ tell if something is broken, since executed
against a real (separated) server, and not against something that is mocked.
However, not sure I really like having a new "tests" folder at "root"
of the project;
Instead, I'd prefer a separate PushEE-integration-tests project, which does
For me, tests inside of the project should be more mock/unit/BDD kinda
tests. Integration tests should be on their own repo, IMO
Once, we have an "official" AG-PushEE repo, do you think having these
"integration" in an isolated repo makes sense?
On Mon, May 20, 2013 at 6:21 PM, Karel Piwko <kpiwko(a)redhat.com> wrote:
I've just sent a PR for PushEE testing . The idea is to write tests
specification and simply execute those against a real running server
More details at .
I have evaluated multiple API approaches, described here, Groovy and
seems to be the best to me.
Any comments/suggestions/objections very welcomed. My plan is to start
specs we have so far and run it on a CI server.
aerogear-dev mailing list