incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS (JIRA) <>
Subject [jira] [Commented] (FLEX-33266) Make it easy for developers to do a targetted Mustella test run that doesnt take hours
Date Mon, 19 Nov 2012 17:27:58 GMT


Frédéric THOMAS commented on FLEX-33266:

Carol, I'm totally in line with your thoughts, I even didn't consider the 3 first steps of
the description to be repeated each time but saved settings and for the second, as soon as
I used it, I felt the file browsing could be improved in many ways.
> Make it easy for developers to do a targetted Mustella  test run that doesnt take hours
> ---------------------------------------------------------------------------------------
>                 Key: FLEX-33266
>                 URL:
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Mustella
>    Affects Versions: Apache Flex 4.8 (parity release)
>            Reporter: OmPrakash Muppirala
>            Assignee: OmPrakash Muppirala
>             Fix For: Adobe Flex SDK Next
> MustellaDependencyDB and MustellaTestChooser provides a very good solution for selecting
tests to be run based on the changes a developer makes.  
> It would be nice to create a tool that automates the rest of the steps as well.  
> Here is the proposed tool and its requirements:
> An AIR app that takes the following inputs
> 1.  Directory location of Apache Flex SDK 
> 2.  Directory location of svn.exe (windows)  
> 3.  Directory location of a bash shell ex. cygwin or git bash (windows)
> Once the developer is done with the changes, they launch the app and on the click of
 a button, the following happens:
> 1.  A nativeprocess invokes svn to get the changes in the Apache Flex SDK directory (via
svn status | grep '^M' )
> 2.  It will write out a file that looks for with the list of test files to
run.  (MustellaTestChooser does this already)
> 3.  A nativeprocess is invoked to open the bash shell and run " -changes"
> 4.  The results of the run is displayed in a log console in the app.  
> Bonus:
> Show a side by side comparison of the baseline bitmaps with the result bitmaps.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message