flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik de Bruin <e...@ixsoftware.nl>
Subject Automating Mustella (was: Mustella failures)
Date Thu, 05 Sep 2013 10:04:12 GMT
Alex, you wrote:

"That's why I've invested my time on other mustella tools.  If you
compile every test, then run MustellaDependencyDB, it will create a
database of dependencies such that, if you run MustellaTestChooser, it
will generate a list of tests that need to be run based on the changed
files so you don't have to run ALL of the tests.

Going further, I put in a shell script called
run_mustella_on_git_status.sh.  Assuming you have MustellaTestChooser
already built, it will call git status, run the output through
MustellaTestChooser and run the required tests all while you sleep or
eat or poop or some combination of the above.  Tip: Wait for it to
start dumping the list of tests to run so you get an idea how long you
should go away."

Someone (I think it was Om) started a project to tie this all
together: OneClickMustella. While looking into
updating/extending/finishing it, I ran into some questions about your
comments and tools:

1) Your process seems to start with "compile every test." How do you
do this without running a complete Mustella?

2) Not sure if I "compiled every test", I decided to move on anyway. I
ran MustellaDependencyDB, which produced a valid looking 'deps.xml'. I
made a simple change to Button, so "git status" would show a
modification and then I ran MustellaTestChooser. The 'changes.txt'
looks impressive, but it doesn't list ANY TEST RELATED TO BUTTON!?
What am I doing wrong?

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Mime
View raw message