Eyefodder

So, I thought I was doing pretty well, getting svn working on the mac, installing cruisecontrol, even getting SCPlugin working with unsigned certificates. Then I tried to run my ant build, and ended up having all sorts of problems getting my mac debug player to run. Some investigating and help from the ANT folks later, and I have a solution

Continue reading "CruiseControl on the Mac - modifying the build script to work x-platform" »

Posted by Paul BH at 04:10 PM | Permalink | Comments (0)
Tags | Continuous Integration | FlexUnit

As I mentioned a few posts ago, I am looking into how asunit and flexunit can fit into our continuous integration set up. The move into AS3 has given me an opportunity to reassess how the 2 frameworks fit my/our needs. The prior post set out the criteria I was testing against - here is what I found...

Continue reading "FlexUnit / ASUnit deathmatch results" »

Posted by Paul BH at 12:08 PM | Permalink | Comments (2)
Tags | Continuous Integration | Best Practices | Test Driven Development | FlexUnit | ASUnit

When I started looking into how we could use flexunit in our CI build, I was struck by how the UI is closely linked to the actual running of the test suite. I really wanted to be able to use the supplied flexunit GUI out of the box - after all, it does everything the developer needs, and yet in order to have the results understood by our build process, we would need the results printed out differently.

To acheive this, my Flexunit test harness uses a factory method pattern to decide how torunthe test suite. Here's how...

Continue reading "FlexUnit UI factory" »

Posted by Paul BH at 03:19 PM | Permalink | Comments (2)
Tags | Flex | Continuous Integration | Best Practices | Test Driven Development | FlexUnit

If you read my earlier posts on Flex and continuous integration, you will remember that we had to do some work to get ASUnit to spit out its results in a manner that would be understood by Cruise Control. We built a log parser to parse results from the Flash players trace file into an XML file detailing the unit test results, and also a simple status file saying if the test suite succeeded or failed. Here's how I got FlexUnit to print out results that will be understood by our parser...

Continue reading "FlexUnit for Cruise Control - XML output" »

Posted by Paul BH at 01:43 PM | Permalink | Comments (3)
Tags | Flex | Continuous Integration | Best Practices | Test Driven Development | FlexUnit

As part of my evaluation of flexunit and ASUnit for continuous integration, one of the rquirements is the ability to have an asynchronous test setup. Lets say you have a class under test that requires some XML in its constructor, and ideally you want to load that XML from an external source. While this doesnt work straight out of the box for flex unit, I found a very simple way to do this. Basically, Flexunit runs its TestCases by executingthe setUp method, then runMiddle() which runs the normal test method or the next asyncronous test. So the trick here is to get runMiddle to execute only when we are ready for it. This question had come up on the Flexcoders mailing list before, and Matt Chotin suggested a possible solution. Here's mine:

Continue reading "Asyncronous test setup with flexunit" »

Posted by Paul BH at 10:52 AM | Permalink | Comments (2)
Tags | Flex | Continuous Integration | Test Driven Development | FlexUnit

Im currently evaluating FlexUnit and ASUnit as we move over to AS3 and seeing how they will fit in with our continuous integration suite. As you may have read in my previous posts on CI, we ended up significantly reworking ASUnit to get it to integrate with our needs for CI. What we are really looking for now is a framework we do not have to monkey around with too much to acheive our needs. The unit test framework we use needs to fulfil the following:

• Simple syncronous tests


• asynchronous tests


• asynchronous setup (e.g. if you ned to load in some data before performing the tests)


• printing the test result out to a log file so that Cruise Control can interpret the results


• broadcast some sort of event when the test suite is complete so we can close the test harness and continue with the build


• works equally well outside of the flex framework

Posted by Paul BH at 10:40 AM | Permalink | Comments (1)
Tags | Flex | Continuous Integration | Test Driven Development | FlexUnit