<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.3" -->
<rss version="2.0">
	<channel>
		<title>Flex acceptance testing and continuous integration</title>
		<description>Comments for Flex acceptance testing and continuous integration at http://www.blackpepper.co.uk , comment 1 to 6 out of 6 comments</description>
		<link>http://www.blackpepper.co.uk</link>
		<lastBuildDate>Wed, 07 Jan 2009 18:39:12 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.3</generator>
		<item>
			<title>...</title>
			<link>http://www.blackpepper.co.uk/black-pepper-blog/Flex-acceptance-testing-and-continuous-integration.html#comment-42</link>
			<description>Thanks for sharing your ideas on Flex testing in this post. It was very helpful and leads me to the right path.

You can find a Maven integration on top of your ideas:
http://www.agimatec.de/blog/2008/11/selenium-flex-tests-with-maven/

Simon - Simon Tiffert</description>
			<pubDate>Thu, 13 Nov 2008 22:55:04 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.blackpepper.co.uk/black-pepper-blog/Flex-acceptance-testing-and-continuous-integration.html#comment-24</link>
			<description>Thanks for all the nice comments!

Tim - I see that v0.2.2 of SeleniumFlexAPI has been published, but the recording feature is still not implemented.

Ivan - I'm using the above mechanism for integration and system testing driven by Ant, in a Hudson continuous integration environment. 

Bernard - SeleniumFlexAPI comes in 2 parts, and this mechanism only uses the part consisting of ActionScript methods which I included in my Flex code. It doesn't use the other part, the user extensions for SeleniumIDE. The JUnit test class calls the ActionScript methods via the FlashSelenium object. One approach to integrating with Ruby might be to rewrite the FlashSelenium Java class in Ruby, for use with your Ruby testing framework. The Java class is an extension of the Selenium RC Java client driver. It's not long and is mostly boilerplate code. So I'm thinking you could write the equivalent Ruby class to extend the Ruby client driver.

I did make some edits to the SeleniumFlexAPI ActionScript include, to remove the tool tips feature and to include DataGrid access. I've added a link to this file, above.
 - Julia Dain</description>
			<pubDate>Mon, 13 Oct 2008 09:09:46 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.blackpepper.co.uk/black-pepper-blog/Flex-acceptance-testing-and-continuous-integration.html#comment-22</link>
			<description>Excellent post indeed! 
We are using Selenium-RC's ruby client driver. Any idea how we can integrate the Selenium Flex API to it?
In this example, the SeleniumFlash object is calling the methods/functions from Selenium Flex which is a user extension for Selenium IDE. How did you integrate the javascript file to your JUnit test class? import maybe? Any idea how it can be integrated with ruby's test unit?

 - Bernard</description>
			<pubDate>Fri, 10 Oct 2008 11:03:25 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.blackpepper.co.uk/black-pepper-blog/Flex-acceptance-testing-and-continuous-integration.html#comment-21</link>
			<description>Excellent posts... any ideas for testing integration  with back end in a continuous way? I've been using Flex Unit to invoke remote methods and it seems to work ok.. just wondering if you have another idea. Thnks - Ivan</description>
			<pubDate>Thu, 09 Oct 2008 22:32:58 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.blackpepper.co.uk/black-pepper-blog/Flex-acceptance-testing-and-continuous-integration.html#comment-17</link>
			<description>You might also want to check out FlexMonkey, an open source Flex GUI testing tool just open sourced by Gorilla Logic. It provides comprehensive record/playback and generates Action-script based tests that can be managed from xUnit frameworks such as FlexUnit.

http://flexmonkey.googlecode.com

 - Stu Stern</description>
			<pubDate>Sat, 27 Sep 2008 16:22:30 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.blackpepper.co.uk/black-pepper-blog/Flex-acceptance-testing-and-continuous-integration.html#comment-16</link>
			<description>Excellent post.  Seems to be the best Flex app integration testing plan out there now and could close a serious continuous integration testing hole we've got when developing BlazeDS/Spring applications.  It would be nice if Selenium Flex API got their recording feature out the door soon, though :)  No complaints and good work all around :) - Tim Fulmer</description>
			<pubDate>Fri, 26 Sep 2008 21:45:38 +0100</pubDate>
		</item>
	</channel>
</rss>
