That's a bit up in the air right now I think.
The way I'm writing tests is AS -> JS google closure. But I'm right in
the middle of refactoring the emitter classes.
The tests I'm writing can be run from ant or whatever, just like the
Falcon tests. I just haven't made a build file yet.
Have you looked at the source code for FalconJx and it's tests?
We don't want to duplicate work but I need to write these tests first.
All I know is, once I get these emitters refactored, the JS output is
going to be what the closure compiler wants. So we could just write an
extension in the assertOut() method that maybe could tests with
Jasmine as well? I don't know I have never used Jasmine testing.
PS, my days with FalconJS are numbered, I've decided it's to
complicated for what I see a relatively simple solution for just
getting plain JS, so I probably won't be working on that code base at
all, I think Alex is doing something with the code.
Mike
Quoting Erik de Bruin <e...@ixsoftware.nl>:
Hi,
I'm trying to figure out how to build tests for the AS to JS cross
compilation.
Should we write AS "strings" and have a script put those through the
FalconJS/FalconJx compiler and compare the result with a pre-defined
"intermediate JS" result? If so, what would be the best tool to write
those tests in? Ant? Shell script? Something else?
I'll be writing the JS tests in Jasmine (mainly because that's what I
know), to test the result from putting the FalconJx output through the
Google Closure Compiler and later on the Closure Builder.
Preferably we would be able to integrate both test suites, so we can
test AS -> "final JS" in one go.
Thoughts?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
