Josh @ Adobe http://blogs.adobe.com/jgarnett Wed, 22 Jun 2011 18:46:51 +0000 en-US hourly 1 http://wordpress.org/?v=3.5.1 Dropbox Encryption http://blogs.adobe.com/jgarnett/2011/06/22/dropbox-encryption/ http://blogs.adobe.com/jgarnett/2011/06/22/dropbox-encryption/#comments Wed, 22 Jun 2011 18:46:51 +0000 Joshua Garnett http://blogs.adobe.com/jgarnett/?p=104 Continue reading →]]> With the recent security issues with DropBox http://blog.dropbox.com/?p=821 http://blog.dropbox.com/?p=735 http://techcrunch.com/2011/06/20/dropbox-security-bug-made-passwords-optional-for-four-hours/ http://paranoia.dubfire.net/2011/04/how-dropbox-sacrifices-user-privacy-for.html you may be considering adopting an additional encryption strategy.

TrueCrypt http://www.truecrypt.org/ a cross-platform encryption solution has been recommended by a few sites. It works by creating an encrypted disk file, which you can store in Dropbox. The one issue with this strategy is it is very hard to sync differences in the file. This means a few file changes could result in the re-syncing of your entire encrypted disk file, which really diminishes the value of Dropbox.

The solution I ultimately went with is BoxCryptor http://www.boxcryptor.com/ for Windows & EncFS http://www.arg0.net/encfs for OSX. BoxCryptor is compatible with EncFS so data you use on one OS should be viewable on the others. The big advantage of BoxCryptor/EncFS over TrueCrypt is it uses a pass-thru filesystem. Instead of creating one big file that stores all of your data it encrypts each individual file (including its filename) separately. This is a big win when using syncing software such as Dropbox.

BoxCryptor is pretty straightforward to install and run on Windows so I won’t go into the installation details.

Installing EncFS on OSX requires a bit more work. Here are some basic instructions. Note, if you are going to share between Windows & OSX I recommend first creating your Secure directory with BoxCryptor, it’ll keep you from having to pass in special flags to encfs.

  1. Install the Mac Developer Tools (aka XCode)
    • If you have your Snow Leopard disk handy you can install the developer tools from there. I believe it is under the Extras directory.
    • If you are running the latest version of Snow Leopard and have the App Store installed, you can download and install XCode 4 from there, which will give you access to all of the needed tools.
  2. Download and install MacPorts http://www.macports.org/
  3. To make sure macports is up to date, run sudo port –v selfupdate
  4. Then run sudo port install encfs
    • This should automatically resolve any dependencies
    • Note, this takes a long time to run, I recommend grabbing a cup of coffee after kicking it off
  5. Reboot your system
  6. Assuming your Encrypted file system is in ~/Dropbox/Secure run the following
    1. (optional) If you haven’t created your encfs yet run: mkdir ~/Dropbox/Secure
    2. mkdir ~/DropboxSecure
    3. encfs ~/Dropbox/Secure ~/DropboxSecure
      • It’ll ask you for the password
    4. You should now be able to see your files in the ~/DropboxSecure directory
  7. To unmount the encrypted drive run: umount ~/DropboxSecure

The overhead for the encryption is minimal. I was seeing about a 20ms increase in running the ls command on an identical directory. Now your files are secure even if your Dropbox account is compromised.

]]> http://blogs.adobe.com/jgarnett/2011/06/22/dropbox-encryption/feed/ 0 The Way of Testivus http://blogs.adobe.com/jgarnett/2011/06/20/the-way-of-testivus/ http://blogs.adobe.com/jgarnett/2011/06/20/the-way-of-testivus/#comments Mon, 20 Jun 2011 17:25:35 +0000 Joshua Garnett http://blogs.adobe.com/jgarnett/?p=100 Just recently I stumbled across and amusing viewpoint on testing. The Way of Testivus is an interesting slant on encouraging testing karma instead of testing dogma. It’s a fun and short read.

]]> http://blogs.adobe.com/jgarnett/2011/06/20/the-way-of-testivus/feed/ 0 Unit Testing JavaScript http://blogs.adobe.com/jgarnett/2011/06/15/unit-testing-javascript/ http://blogs.adobe.com/jgarnett/2011/06/15/unit-testing-javascript/#comments Wed, 15 Jun 2011 17:56:27 +0000 Joshua Garnett http://blogs.adobe.com/jgarnett/?p=86 Continue reading →]]> I’ve stumbled across a really cool unit testing framework for JavaScript that I wanted to share with everyone. It is called js-test-driver. http://code.google.com/p/js-test-driver/ Most JavaScript unit test frameworks need to be manually run, which requires a dev/qe to open a browser, start the tests, and verify the results. This doesn’t really scale or work for a CI environment. Js-test-driver aims to solve that problem.

The software itself is built with java and has a client and server side component. To start the server you just pass in a port and fire it up. Ex: java -jar JsTestDriver-1.3.2.jar –port 4224 It also has the option of passing in a list of browser executables, which the server will automatically start and setup to listen for unit tests. Additional browsers can be provisioned manually across a variety of devices by pointing to http://{the_servers_IP}:4224 in any browser window. Think Mobile. The client side is run by setting up a config file with some general information, including the server to connect to and the JavaScript files to load.

Example: jsTestDriver.conf

server: http://localhost:4224
 
load:
  - bin/*.js
 
timeout: 90

The tests are then ran by calling the same jar file: java -jar JsTestDriver-1.3.2.jar –tests all

In my proof of concept, I was able to quickly get 8 browsers, (4 Windows browsers, 2 Mac browsers, iPad Safari, and iPhone Safari), up and running for testing against. The Unit Test itself was a very basic Hello World test. The command took more time initializing the jvm & connections than the actual unit tests, which only took 26ms to run across all of the browsers/devices.

Joshua@Quake ~/js-test-driver
$ java -jar JsTestDriver-1.3.2.jar --tests all
........
Total 8 tests (Passed: 8; Fails: 0; Errors: 0) (1.00 ms)
  Safari 533.21.1 Windows: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (0.00 ms)
  Safari 6533.18.5 iPhone OS: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (1.00 ms)
  Firefox 4.0.1 Windows: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (1.00 ms)
  Firefox 4.0.1 Mac OS: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (0.00 ms)
  Safari 6533.18.5 Mac OS: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (1.00 ms)
  Chrome 12.0.742.100 Windows: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (0.00 ms)
  Safari 533.21.1 Mac OS: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (1.00 ms)
  Microsoft Internet Explorer 9.0 Windows: Run 1 tests (Passed: 1; Fails: 0; Errors 0) (0.00 ms)
 
Joshua@Quake ~/js-test-driver
$
]]> http://blogs.adobe.com/jgarnett/2011/06/15/unit-testing-javascript/feed/ 0 Displaying extremely large strings in a Flex DataGridColumn http://blogs.adobe.com/jgarnett/2011/04/04/displaying-extremely-large-strings-in-a-flex-datagridcolumn/ http://blogs.adobe.com/jgarnett/2011/04/04/displaying-extremely-large-strings-in-a-flex-datagridcolumn/#comments Tue, 05 Apr 2011 03:11:47 +0000 Joshua Garnett http://blogs.adobe.com/jgarnett/?p=54 Continue reading →]]> Recently while working on InMarket, I was tasked with displaying very large strings within a DataGridColumn to our users. The variableRowHeight property of a DataGrid will get you part of the way, but if you start to exceed a few thousand characters, you’ll find that your row has a height larger then your entire DataGrid! As a way around this we ended up using the itemEditor capabilities of the DataGrid.

To start off, first we created an itemRenderer for the DataGridColumn, which displays a maximum number of characters. If the maximum number of characters is exceeded the itemRenderer automatically truncates the string and adds “… Read More” to it.

package
{
	import com.adobe.utils.StringUtil;
	import flash.text.StyleSheet;
	import mx.controls.dataGridClasses.DataGridItemRenderer;
 
	public class PartialTextDataGridItemRenderer extends DataGridItemRenderer
	{
		private static const MAXIMUM_NUMBER_OF_CHARACTERS:Number = 256;
 
		public function PartialTextDataGridItemRenderer()
		{
			super();
		}
 
		public override function validateProperties():void
		{
			super.validateProperties();
 
			if (listData)
			{
				text = "";		
 
				//truncate the text if needed and render text as HTML
				htmlText = truncateLabel(listData.label);
 
				//apply style to text so Read More link looks like a link
				styleSheet = getLinkStyle();
			}
		}
 
		private static function getLinkStyle() : StyleSheet {
			var style:StyleSheet = new StyleSheet();
 
			var styleObj:Object = new Object();
			styleObj.fontWeight = "normal";
			styleObj.fontSize = "12px";
			styleObj.color = "#0000ff";
			styleObj.textDecoration = "underline";
			style.setStyle("a", styleObj);
 
			return style;
		}
 
		private static function truncateLabel(label:String) : String {
			if(label.length > MAXIMUM_NUMBER_OF_CHARACTERS) {
				label = label.substr(0,MAXIMUM_NUMBER_OF_CHARACTERS);
 
				//remove any extra whitespace at the end of the string
				label = StringUtil.trim(label);
 
				//ensure that label ends with ...
				if(label.charAt(label.length-1) == ".") {
					label = label + "..";
				}
				else {
					label = label + "...";
				}
 
				//add read more link to indicate to user that there is more
				//text and that it is clickable.
				label = label + "  <a href=\"#\">Read More</a>";
			}
 
			return label;
		}
	}
}

Next, for the itemEditor itemRenderer we use a TextArea that is set to not be editable. We also strip away the styling that would make it look like a TextArea embeded within the column.

package
{	
	import mx.controls.TextArea;
 
	/**
	 * Creates an non-editable TextArea to be used as renderer and
	 * styled so that it is seamless with the other DataGrid cells.
	 */
	public class FullTextDataGridItemRenderer extends TextArea
	{
		public function FullTextDataGridItemRenderer()
		{
			super();
			this.editable = false;
			this.setStyle("paddingLeft",5);
			this.setStyle("paddingRight",5);
			this.setStyle("paddingTop",2);
			this.setStyle("paddingBottom",2);
			this.setStyle("backgroundAlpha",0);
			this.setStyle("borderStyle", "none");
		}
	}
}

What this does is, whenever the column is clicked on, any strings that exceed the maximum length will be converted to their full length and embedded within a scrollable TextArea. It provides a seamless experience for users, by not forcing them to read a tooltip or some other dialog. Here is an example application that puts the two itemRenderers to use.

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
				layout="vertical"
				width="800"
				height="600"
				paddingBottom="0" 
				paddingLeft="0" 
				paddingRight="0" 
				paddingTop="0"
				creationComplete="creationCompleteHandler(event)">
 
	<mx:Script>
		<![CDATA[
			import mx.collections.ArrayCollection;
			import mx.events.FlexEvent;
 
			[Bindable] private var gridDataProvider:ArrayCollection;
 
			/**
			 * On creationComplete, create the data provider for the DataGrid.
			 */
			protected function creationCompleteHandler(event:FlexEvent):void
			{
				gridDataProvider = new ArrayCollection();
 
				var longDescription:String = "Lorem ipsum dolor sit amet, consectetur " +
					"adipiscing elit. Maecenas pellentesque odio eget tortor feugiat " +
					"sit amet auctor neque eleifend. Curabitur pharetra nunc eget " +
					"purus hendrerit sodales. Pellentesque congue commodo felis, sed " +
					"volutpat sem vulputate sit amet. Nulla a dolor consectetur urna " +
					"laoreet rhoncus nec ut lacus. Phasellus neque felis, sagittis sed " +
					"lobortis sed, accumsan suscipit lectus. In nec placerat nulla. Proin " +
					"id sem vitae massa adipiscing luctus. Quisque vitae urna erat, a " +
					"ultrices est. Nulla scelerisque varius turpis et porttitor. Nullam " +
					"convallis elementum condimentum. Nulla ac ornare est. Phasellus " +
					"posuere vestibulum dolor nec cursus. ";
 
				var longShortDescription:String = "Lorem ipsum dolor sit amet";
 
				gridDataProvider.addItem({id:1, description:longDescription, shortDescription:longShortDescription});
 
				gridDataProvider.addItem({id:2, description:longShortDescription, shortDescription:longShortDescription});
			}
 
		]]>
	</mx:Script>
 
	<mx:DataGrid width="100%" 
				 height="100%"
				 dataProvider="{gridDataProvider}"
				 variableRowHeight="true" 
				 wordWrap="true"
				 verticalAlign="top" 
				 editable="true"
				 sortableColumns="false">
 
		<mx:columns>			
			<mx:DataGridColumn width="100"
							   dataField="id"
							   headerText="Id"
							   editable="false" />
 
			<mx:DataGridColumn dataField="description" 
							   headerText="Description"
							   editable="true"
							   itemRenderer="PartialTextDataGridItemRenderer"
							   itemEditor="FullTextDataGridItemRenderer" />
 
			<mx:DataGridColumn width="200"
							   dataField="shortDescription" 
							   headerText="Short Description"
							   editable="false" />
		</mx:columns>
	</mx:DataGrid>
</mx:Application>

The source code can be downloaded at https://github.com/joshgarnett/JoshAtAdobeSourceCode/tree/master/LargeStringsInDataGrid.

]]> http://blogs.adobe.com/jgarnett/2011/04/04/displaying-extremely-large-strings-in-a-flex-datagridcolumn/feed/ 0 Continuous Integratation testing FlexUnit on CentOS http://blogs.adobe.com/jgarnett/2011/03/13/continuous-integratation-testing-flexunit-on-centos/ http://blogs.adobe.com/jgarnett/2011/03/13/continuous-integratation-testing-flexunit-on-centos/#comments Sun, 13 Mar 2011 22:15:20 +0000 Joshua Garnett http://blogs.adobe.com/jgarnett/?p=4 Continue reading →]]> First let me introduce myself.  My name is Joshua Garnett.  I joined Adobe last fall as a Computer Scientist on the Flash Platform Services Team.  I’m currently working on the InMarket app distribution service. If you’re an app developer and looking to simplify your deployment process, you should definitely check it out.

Now on to the actual reason behind this post.  Recently I was tasked with getting FlexUnit tests to run in our CI environment. There is a lot of documentation out there on how to get things up and running on Hudson, but I wasn’t able to find a fool-proof method for those of us who just want to use an ant build script to run the tests. This is a brief summary of the items that need to be setup and installed in order to do just that.

Here is the software that I ended up using:


I’m not going to cover creating FlexUnit tests, but I wanted to display an example Test Application for running the Unit tests. The key item is adding the CIListener() to the FlexUnitCore.

<?xml version="1.0" encoding="utf-8"?>
<mx:Application 
	xmlns:mx="http://www.adobe.com/2006/mxml"
	creationComplete="runMe()
	xmlns:adobe="http://www.adobe.com/2009/flexUnitUIRunner">
 
	<mx:Script>
		<![CDATA[
			import com.your.company.tests.AllTests;
 
			import flexunit.framework.TestSuite;
 
			import org.flexunit.listeners.CIListener;
			import org.flexunit.listeners.UIListener;
			import org.flexunit.runner.FlexUnitCore;
 
			private var core:FlexUnitCore;
 
			public function runMe():void {
				core = new FlexUnitCore();
				core.addListener(new UIListener(uiListener));
				core.addListener(new CIListener());
 
				core.run( com.your.company.tests.AllTests );
			}
		]]>
	</mx:Script>
 
	<adobe:TestRunnerBase id="uiListener" width="100%" height="100%" />
</mx:Application>

Once the Testing Application is created, we need to create an ant build script to run the tests. The script below is compatible with Ant 1.7.0+ and should run on multiple platforms.

<project name="YourProject" default="test">
 
	<property name="SRC_DIR" value="./src" />
	<property name="TEST_DIR" value="./bin-test" />
	<property name="FLEX_UNIT_DIR" value="./flexunit-output" />
 
	<property name="flexunit.jar" value="./libs/flexUnitTasks-4.1.0_RC2-28.jar" />
 
	<property name="flexunit.swc" value="./libs/flexunit-4.1.0_RC2-28-flex_3.5.0.12683.swc" />
	<property name="flexunit-uilistener.swc" value="./libs/flexunit-uilistener-4.1.0_RC2-28-flex_3.5.0.12683.swc" />
	<property name="flexunit-cilistener.swc" value="./libs/flexunit-cilistener-4.1.0_RC2-28-flex_3.5.0.12683.swc" />
 
	<!-- Setup platform booleans -->
	<condition property="isMac">
		<os family="mac" />
	</condition>
 
	<condition property="isWindows">
		<os family="windows" />
	</condition>
 
	<condition property="isLinux">
		<os name="Linux" />
	</condition>
 
	<!-- 
		Different platforms can have different SDK locations, mxmlc scripts, 
		and FlexUnit properties.
	-->
	<target name="setupEnvironment" depends="setPropsMac,setPropsWindows,setPropsLinux" />
 
	<target name="setPropsMac" if="isMac">
		<property name="FLEX_HOME" value="/Applications/Adobe Flash Builder 4/sdks/3.5.0/" />
		<property name="MXMLC" value="${FLEX_HOME}/bin/mxmlc" />
		<property name="HEADLESS" value="false" />
	</target>
 
	<target name="setPropsWindows" if="isWindows">
		<property name="FLEX_HOME" value="C:\Program Files (x86)\Adobe\Adobe Flash Builder 4\sdks\3.5.0" />
		<property name="MXMLC" value="${FLEX_HOME}/bin/mxmlc.exe" />
		<property name="HEADLESS" value="false" />
	</target>
 
	<target name="setPropsLinux" if="isLinux">
		<property name="FLEX_HOME" value="/opt/flex_sdk_3.5.0.12683" />
		<property name="MXMLC" value="${FLEX_HOME}/bin/mxmlc" />
		<!-- only linux should run in headless mode -->
		<property name="HEADLESS" value="true" />
	</target>
 
	<!-- this is used for running flexunit from the command line -->
	<taskdef resource="flexUnitTasks.tasks" classpath="${flexunit.jar}"/>
 
	<target name="clean" depends="">
		<delete dir="${TEST_DIR}" />
		<delete dir="${FLEX_UNIT_DIR}" />
	</target>
 
	<target name="test" depends="clean,setupEnvironment">
		<property name="debug" value="true" />
		<antcall target="flexUnitTest" />
	</target>
 
	<target name="flexUnitTest" depends="">
		<exec executable="${MXMLC}" failonerror="true">
			<arg value="-debug=${debug}" />
			<arg value="-compiler.source-path=${SRC_DIR}" />
			<arg value="-source-path=${SRC_DIR}" />
			<arg value="-link-report=linkReport.xml" />
			<arg value="-library-path+=${flexunit.swc}" />
			<arg value="-library-path+=${flexunit-uilistener.swc}" />
			<arg value="-library-path+=${flexunit-cilistener.swc}" />
			<!-- Be sure to include any other swcs needed to build the swf -->
			<arg value="-output=${TEST_DIR}/FlexUnitTestingApp.swf" />
			<arg value="--" />
			<arg value="${SRC_DIR}/FlexUnitTestingApp.mxml" />
		</exec>
 
		<mkdir dir="${FLEX_UNIT_DIR}"/>
 
		<!-- 
			Note: By specifying haltonfailure, the ant script will use a return 
			code of 1 instead of 0, which you can use to script validation of
			the test results.
		-->
		<flexunit swf="${TEST_DIR}/FlexUnitTestingApp.swf" 
					toDir="$FLEX_UNIT_DIR}"
					haltonfailure="true"
					headless="${HEADLESS}"
					verbose="true"
					localTrusted="true" />
 
		<junitreport todir="${FLEX_UNIT_DIR}">
			<fileset dir="${FLEX_UNIT_DIR}">
				<include name="TEST-*.xml"/>
			</fileset>
			<report format="frames" todir="${FLEX_UNIT_DIR}/html"/>
		</junitreport>
	</target>
</project>

Lastly, we need to install a few packages on CentOS 5.5. All of these commands should be run as root.

# Download and install the flash projector
wget http://download.macromedia.com/pub/flashplayer/updaters/10/flashplayer_10_sa_debug.tar.gz
tar xzvf flashplayer_10_sa_debug.tar.gz
 
# Add it to the PATH and make the symbolic link gflashplayer
mv flashplayerdebugger /usr/bin
ln -s /usr/bin/flashplayerdebugger /usr/bin/gflashplayer
 
# install xvnc
yum install vnc-server
 
# install windowing system
yum groupinstall "GNOME Desktop Environment"
 
# Setup VNC Password
vncpasswd

We are now ready to run the FlexUnit tests on a CentOS instance. By running either ant or ant test we should see the swf build, flex unit run, and then finally see the creation of the HTML files for viewing the results. Sample output below.

Buildfile: build.xml
 
clean:
   [delete] Deleting directory /opt/bin-test
   [delete] Deleting directory /opt/flexunit-output
 
setPropsMac:
 
setPropsWindows:
 
setPropsLinux:
 
setupEnvironment:
 
test:
 
flexUnitTest:
     [exec] Loading configuration file /opt/flex_sdk_3.5.0.12683/frameworks/flex-config.xml
     [exec] /opt/bin-test/FlexUnitTestingApp.swf (911489 bytes)
    [mkdir] Created dir: /opt/flexunit-output
 [flexunit] Validating task attributes ...
 [flexunit] OS: [Linux]
 [flexunit] Generating default values ...
 [flexunit] Using default working dir [/opt]
 [flexunit] Using default reporting dir [/opt]
 [flexunit] Using the following settings for the test run:
 [flexunit]     FLEX_HOME: [/opt/flex_sdk_3.5.0.12683]
 [flexunit]     haltonfailure: [true]
 [flexunit]     headless: [true]
 [flexunit]     display: [99]
 [flexunit]     localTrusted: [true]
 [flexunit]     player: [flash]
 [flexunit]     port: [1024]
 [flexunit]     swf: [/opt/bin-test/FlexUnitTestingApp.swf]
 [flexunit]     timeout: [60000ms]
 [flexunit]     toDir: [/opt]
 [flexunit] Setting up server process ...
 [flexunit] Starting server ...
 [flexunit] Starting xvnc
 [flexunit] Attempting start on :99 ...
 [flexunit] Executing 'vncserver' with arguments:
 [flexunit] ':99'
 [flexunit] 
 [flexunit] The '' characters around the executable and arguments are
 [flexunit] not part of the command.
 [flexunit] 
 [flexunit] Opening server socket on port [1024].
 [flexunit] Waiting for client connection ...
 [flexunit] 
 [flexunit] Starting applications specified in /root/.vnc/xstartup
 [flexunit] 
 [flexunit] Setting DISPLAY=:99
 [flexunit] Executing 'gflashplayer' with arguments:
 [flexunit] '/opt/bin-test/FlexUnitTestingApp.swf'
 [flexunit] 
 [flexunit] The '' characters around the executable and arguments are
 [flexunit] not part of the command.
 [flexunit] 
 [flexunit] Client connected.
 [flexunit] Setting inbound buffer size to [262144] bytes.
 [flexunit] Receiving data ...
 [flexunit] Sending acknowledgement to player to start sending test data ...
 [flexunit] 
 [flexunit] Stopping server ...
 [flexunit] End of test data reached, sending acknowledgement to player ...
 [flexunit] Closing client connection ...
 [flexunit] Closing server on port [1024] ...
 [flexunit] Terminating xvnc on :99
 [flexunit] Executing 'vncserver' with arguments:
 [flexunit] '-kill'
 [flexunit] ':99'
 [flexunit] 
 [flexunit] The '' characters around the executable and arguments are
 [flexunit] not part of the command.
 [flexunit] 
 [flexunit] Killing Xvnc process ID 3685
 [flexunit] Analyzing reports ...
 [flexunit] 
 [flexunit] Suite: com.your.company.tests.ParserTest
 [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec
 [flexunit] Suite: com.your.company.tests.ModelTest
 [flexunit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec
 [flexunit] 
 [flexunit] Results :
 [flexunit] 
 [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.069 sec
 [flexunit] 
[junitreport] Processing /opt/flexunit-output/TESTS-TestSuites.xml to /tmp/null2057278126
[junitreport] Transform time: 267ms
[junitreport] Deleting: /tmp/null2057278126
 
BUILD SUCCESSFUL
Total time: 21 seconds
]]> http://blogs.adobe.com/jgarnett/2011/03/13/continuous-integratation-testing-flexunit-on-centos/feed/ 4