Hi folks, I just checked in enough code to get the Button and CheckBox test from the SDK's checkintest to run under FlexJS. There's another half-dozen or so tests we should probably finish converting since we have those components in the FlexJS framework. Getting some sort of checkintest running is one of the last things I want to do before cutting an an initial official FlexJS release.
This checkintest works like the SDK test. It compiles a SWF and runs it and examines the output. The next step is to run the same tests cross-compiled to JS. I'm about to start porting the Mustella classes to JS, but I'm wondering if that is the right strategy or not. I was looking at the Marmotinni stuff that Erik did a while back that uses Selenium to run tests in the browsers. The actual test seem to be written in Java. I think it would be nice to be able to repurpose the MXML mustella tests and get them to run as cross-compiled tests. I think some choices are: 1) See what happens when Mustella is cross-compiled. I'm pretty sure this won't work. It could be an early test of what it will be like to support other third-party AS frameworks, but Mustella is relying on some low-level Flash things like frame events, security sandboxes, etc, so I don't think it is a fair test. We could fork Mustella and strip some of that stuff out though, but I'd rather not have a fork of Mustella around to maintain. 2) Make parallel Mustella JS files. That's the direction I'm taking right now. That's a valid FlexJS way since FlexJS is mostly about parallel AS/JS frameworks. I still need a way to run the test in the browser and collect output. Hence the desire to see if Marmotinni could do that. 3) Write some test converter that converts a Mustella MXML script into Java code or maybe an XML representation that some Java code could interpret to execute the test. 4) Just re-write every test in Java. 5) Something I haven't thought of yet. Thoughts? -Alex
