Comments on: How to run FlexUnit in a continuous build http://misko.hevery.com/2009/02/01/how-to-run-flexunit-in-a-continuous-build/ Testability Explorer Thu, 02 Sep 2010 04:05:01 -0400 http://wordpress.org/?v=2.8 hourly 1 By: misko http://misko.hevery.com/2009/02/01/how-to-run-flexunit-in-a-continuous-build/comment-page-1/#comment-3386 misko Fri, 23 Apr 2010 00:14:44 +0000 http://misko.hevery.com/?p=388#comment-3386 have you tried XVFB? http://en.wikipedia.org/wiki/Xvfb have you tried XVFB? http://en.wikipedia.org/wiki/Xvfb

]]> By: jensendarren http://misko.hevery.com/2009/02/01/how-to-run-flexunit-in-a-continuous-build/comment-page-1/#comment-3383 jensendarren Thu, 22 Apr 2010 12:42:24 +0000 http://misko.hevery.com/?p=388#comment-3383 Thankyou for your informative insight. I am very new to Flex and have been literally thrown into an existing project which already has a set of tests written by another developer. My task is to get these tests to run as part of our nightly build. I took the example you provided and applied it against our own test runner using Rake instead of ANT. After half a day of figuring out how Flex works and how to compile it etc, etc, I adjusted our runner to write out an XML file and successfully compiled it using the AIR libraries. However, when I run this on our deployment server (Ubuntu 9.04 Server) I see the following error "Gtk-WARNING **: cannot open display". How can I get adl to run without a GUI? Thankyou for your informative insight. I am very new to Flex and have been literally thrown into an existing project which already has a set of tests written by another developer. My task is to get these tests to run as part of our nightly build.

I took the example you provided and applied it against our own test runner using Rake instead of ANT. After half a day of figuring out how Flex works and how to compile it etc, etc, I adjusted our runner to write out an XML file and successfully compiled it using the AIR libraries.

However, when I run this on our deployment server (Ubuntu 9.04 Server) I see the following error “Gtk-WARNING **: cannot open display”. How can I get adl to run without a GUI?

]]> By: zwetan http://misko.hevery.com/2009/02/01/how-to-run-flexunit-in-a-continuous-build/comment-page-1/#comment-644 zwetan Tue, 03 Feb 2009 10:59:32 +0000 http://misko.hevery.com/?p=388#comment-644 Hi, I took another shot at the problemthe Flash Player or AIR runtime both use the Tamarin VM to execute ActionScript, and on top of it add their respective APIso basically I added few extras to the Tamarin VM and ported my own unit tests framework to run in a CLI, so my unit tests can run in that VM on the command-linea longer more detailled explanation can be found here <a href="http://groups.google.co.uk/group/flex-mojos/msg/a03b08871bab137a" rel="nofollow">http://groups.google.co.uk/group/flex-mojos/msg/a03b08871bab137a</a> let me know what do you think about it :) Hi, I took another shot at the problemthe Flash Player or AIR runtime both use the Tamarin VM to execute ActionScript, and on top of it add their respective APIso basically I added few extras to the Tamarin VM and ported my own unit tests framework to run in a CLI, so my unit tests can run in that VM on the command-linea longer more detailled explanation can be found here http://groups.google.co.uk/group/flex-mojos/msg/a03b08871bab137a let me know what do you think about it :)

]]> By: misko http://misko.hevery.com/2009/02/01/how-to-run-flexunit-in-a-continuous-build/comment-page-1/#comment-643 misko Mon, 02 Feb 2009 19:48:21 +0000 http://misko.hevery.com/?p=388#comment-643 I was not aware of those projects, let me check them out... I was not aware of those projects, let me check them out…

]]> By: Luke Bayes http://misko.hevery.com/2009/02/01/how-to-run-flexunit-in-a-continuous-build/comment-page-1/#comment-642 Luke Bayes Mon, 02 Feb 2009 19:24:38 +0000 http://misko.hevery.com/?p=388#comment-642 There are still some problems here.1) It's ideal to run your test harness in an environment that is as close as possible to your production environment, and unless your application is intended for AIR, then compiling to AIR includes a lot of unintended code. The same goes for ActionScript only projects that are tested using FlexUnit, Flex applications are not the same as ActionScript applications.2) Just like the desktop and browser debug Flash Players,  AIR launches a GUI dialog with any uncaught runtime exceptions. This means that your CI machine will hang and at best - simply fail with a timeout and no useful information, whenever an exception occurs with the frame clock at the top of the stack.The solution?<a href="http://asunit.org">AsUnit</a> and <a href="http://projectsprouts.org">ProjectSprouts</a>.Among many things, Sprouts includes a Continuous Integration Rake task that runs in the Flex Debugger instead of the Flash Player, this gives us the ability to capture uncaught runtime exceptions, output the failure stack trace and all variables (and values) in the local scope where the failure occurred, and close down properly.Of course test results, including failures, are always output to an XUnit XML results file.Check it out and let us know what you think!Thanks There are still some problems here.1) It’s ideal to run your test harness in an environment that is as close as possible to your production environment, and unless your application is intended for AIR, then compiling to AIR includes a lot of unintended code. The same goes for ActionScript only projects that are tested using FlexUnit, Flex applications are not the same as ActionScript applications.2) Just like the desktop and browser debug Flash Players,  AIR launches a GUI dialog with any uncaught runtime exceptions. This means that your CI machine will hang and at best – simply fail with a timeout and no useful information, whenever an exception occurs with the frame clock at the top of the stack.The solution?<a href=”http://asunit.org”>AsUnit</a> and <a href=”http://projectsprouts.org”>ProjectSprouts</a>.Among many things, Sprouts includes a Continuous Integration Rake task that runs in the Flex Debugger instead of the Flash Player, this gives us the ability to capture uncaught runtime exceptions, output the failure stack trace and all variables (and values) in the local scope where the failure occurred, and close down properly.Of course test results, including failures, are always output to an XUnit XML results file.Check it out and let us know what you think!Thanks

]]>