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 indeed needed! 
--> 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" level of the project;
Instead, I'd prefer a separate PushEE-integration-tests project, which does the same.

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@redhat.com> wrote:
Hi All,

I've just sent a PR for PushEE testing [1]. The idea is to write tests covering
specification and simply execute those against a real running server instance.
More details at [2].

I have evaluated multiple API approaches, described here[3], Groovy and Spock
seems to be the best to me.

Any comments/suggestions/objections very welcomed. My plan is to start covering
specs we have so far and run it on a CI server.



[1] https://github.com/matzew/pushee/pull/6/
[2] https://github.com/kpiwko/pushee/blob/tests/tests/readme.txt
[3] https://gist.github.com/kpiwko/5612949
aerogear-dev mailing list

Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf