<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.4">
</HEAD>
<BODY>
On Wed, 2013-08-14 at 07:45 -0500, Kris Borchers wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
Wow, This is a very thorough set of tests! I would definitely like to integrate them into our integration test suite (either replacing or augmenting the current pipeline tests) but that will take some work. If you look at that repo, all of the servers are cloned/downloaded, built and started on the fly to keep those binaries out of the repo. This is to allow all of these tests to be fired up on Travis so the same would need to happen for these tests. It might be easier, and faster, to just set up a quick node.js server that can handle CORS which is actually quite simple, and give it some static JSON to serve up.
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
</BLOCKQUOTE>
I'll definitely check this repo and see how you have setup the environment and the test suites. The biggest problem I faced when writing the CORS/JSONP tests was that some paging tests were failing on Phantom JS. The next step was to use the Arquillian QUnit [1] extension. It automates the QUnit JavaScript testing and integrates with JUnit, therefore it can be easily used in continuous integration environments. As described in the README file [2], I had to use X Virtual Framebuffer and install a new version of Mozilla Firefox on Travis CI machines (using teh addons Travis command) in order to make the QUnit paging tests to pass.<BR>
<BR>
[1]: <A HREF="https://github.com/arquillian/arquillian-extension-qunit">https://github.com/arquillian/arquillian-extension-qunit</A><BR>
[2]: <A HREF="https://github.com/tolis-e/aerogear-js-cors-jsonp-tests/blob/master/README.md">https://github.com/tolis-e/aerogear-js-cors-jsonp-tests/blob/master/README.md</A><BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
One other note is that this line [1] should not be necessary. Luke and I have a task for after the release to take a day and clean up all of our tests so that order does not matter and no tests rely on previous tests. If the tests are written that way, that line is not needed.
</BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
+1 QUnit explicit reorder deactivation should not be required. I have removed it [3]<BR>
<BR>
[3]: <A HREF="https://github.com/tolis-e/aerogear-js-cors-jsonp-tests/blob/master/aerogear-js-qunit-cors-jsonp-tests/src/main/webapp/assets/js/test/pipeline-rest-cors-jsonp-tests.js">https://github.com/tolis-e/aerogear-js-cors-jsonp-tests/blob/master/aerogear-js-qunit-cors-jsonp-tests/src/main/webapp/assets/js/test/pipeline-rest-cors-jsonp-tests.js</A><BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
After the release, I would be more than happy to help with this or meet with you guys if you have questions or suggestions on making that entire suite better. Just let me know.
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
Sure :)<BR>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<A HREF="https://github.com/tolis-e/aerogear-js-cors-jsonp-tests/blob/master/aerogear-js-cors-jsonp-tests/src/main/webapp/assets/js/test/pipeline-rest-cors-jsonp-tests.js#L19">https://github.com/tolis-e/aerogear-js-cors-jsonp-tests/blob/master/aerogear-js-cors-jsonp-tests/src/main/webapp/assets/js/test/pipeline-rest-cors-jsonp-tests.js#L19</A>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
On Aug 14, 2013, at 2:18 AM, Karel Piwko <<A HREF="mailto:kpiwko@redhat.com">kpiwko@redhat.com</A>> wrote:
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
Kris,<BR>
<BR>
Tolis' created a bunch of JS integration tests, running JSON-P and CORS tests<BR>
on top of Aerogear JS in a real browser, hosted at [1]. I think it would be<BR>
great if this can somehow be merged into [2].<BR>
<BR>
Karel<BR>
<BR>
[1] <A HREF="https://github.com/tolis-e/aerogear-js-cors-jsonp-tests">https://github.com/tolis-e/aerogear-js-cors-jsonp-tests</A><BR>
[2] <A HREF="https://github.com/aerogear/aerogear-js-integration">https://github.com/aerogear/aerogear-js-integration</A><BR>
<BR>
On Tue, 13 Aug 2013 15:29:55 -0500<BR>
Kris Borchers <<A HREF="mailto:kris@redhat.com">kris@redhat.com</A>> wrote:<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
JS (remaining tasks)<BR>
<BR>
- Writing more integration tests<BR>
- Final changes to SimplePush quickstart and README<BR>
- Blog post<BR>
<BR>
On Aug 13, 2013, at 3:06 PM, Bruno Oliveira <<A HREF="mailto:bruno@abstractj.org">bruno@abstractj.org</A>> wrote:<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
AeroGear Security:<BR>
<A HREF="https://issues.jboss.org/browse/AGSEC/fixforversion/12322348#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel">https://issues.jboss.org/browse/AGSEC/fixforversion/12322348#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel</A><BR>
<BR>
- Update the whole documentation at aerogear.org site<BR>
- Javadoc review and updates<BR>
- All the demos and projects depending on AGSec were updated with<BR>
PicketLink beta7 (the latest release)<BR>
- All the artifacts deployed on maven central<BR>
- Help on simplepush/android as needed<BR>
- Currently automating snapshot releases to AGSec<BR>
- Listening a good song to write this report.<BR>
<BR>
Douglas Campos wrote:<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
Jay asked for a more detailed release status from the subprojects, could<BR>
y'all please report on this thread?<BR>
<BR>
Top-level:<BR>
- working on the release blog<BR>
- helping review the site content after the restyle (with help from<BR>
Yavuz)<BR>
- aerogear-announce mailing list in progress<BR>
- general help on last-minute issues<BR>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE>
<BR>
-- <BR>
abstractj<BR>
<BR>
<BR>
_______________________________________________<BR>
aerogear-dev mailing list<BR>
aerogear-dev@lists.jboss.org<BR>
https://lists.jboss.org/mailman/listinfo/aerogear-dev<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE>
<BR>
<BR>
_______________________________________________<BR>
aerogear-dev mailing list<BR>
<A HREF="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</A><BR>
https://lists.jboss.org/mailman/listinfo/aerogear-dev<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE>
<BR>
_______________________________________________<BR>
aerogear-dev mailing list<BR>
<A HREF="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</A><BR>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<PRE>
_______________________________________________
aerogear-dev mailing list
<A HREF="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</A>
<A HREF="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</A>
</PRE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BODY>
</HTML>