<br><br><div class="gmail_quote">On Mon, Feb 25, 2013 at 2:58 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><br><div><div class="im"><div>On Feb 25, 2013, at 7:57 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite">
<br><br><div class="gmail_quote">On Mon, Feb 25, 2013 at 2:27 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm not sure how I feel about this. On the one hand, I like the idea of some server app somewhere that I can do my integration tests against since having someone contributing to JS deploy a server themselves to be able to run or add to integration tests is a blocker. On the other hand, this is another piece for us to maintain.<br>
</blockquote><div><br></div><div><br></div><div>yes - tests need to be maintained :) </div></div></blockquote></div>Obviously tests need to be maintained :P I was talking about another server piece running out in the world that would have to be kept up to date and running at all times.</div>
</div></blockquote><div><br></div><div><br></div><div>Two things:</div><div>- client side test app (for each platform)</div><div>- a 'test server' app (e.g. some restful endpoint). </div><div><br></div><div>IMO having integration tests is a quality plus, mocking is OK, but I usually trust real servers a bit more :) </div>
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br><blockquote type="cite"><div class="im">
<div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br>
On Feb 25, 2013, at 4:27 AM, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> for testing of timeout[1] and cancel[2], apart from the unit tests (that used a mocked http), I have updated our iOS integration tests to go against a simple server app[3] that does a "sleep" on the requests methods so I can properly verify the methods do work [both in iOS 5/6].<br>
><br>
> Because as I understand, the "sleep" simulation applies to other platforms too, what should we do for this case? Have a branch on the "TODO" app eg. "TODO-integration" that will be used in our integration tests, or have a different server application for that purpose.<br>
><br>
> wdyt?<br>
><br>
> Thanks,<br>
> Christos<br>
><br>
> [1] <a href="https://issues.jboss.org/browse/AEROGEAR-931" target="_blank">https://issues.jboss.org/browse/AEROGEAR-931</a><br>
> [2] <a href="https://issues.jboss.org/browse/AEROGEAR-898" target="_blank">https://issues.jboss.org/browse/AEROGEAR-898</a><br>
> [3] <a href="https://github.com/cvasilak/RESTfulExample" target="_blank">https://github.com/cvasilak/RESTfulExample</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br></div>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
_______________________________________________<div class="im"><br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div>
</blockquote></div><br></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>