I just set up a QA site for a new project I’m working on called “Fluffy” — just because it’s a word that starts with the letters “FL”. It’s a research project born out of a conversation with my friend Nate at a BBQ last week.
Fluffy is an investigation into Flex testing and automation. Nate mentioned that tools and techniques for testing Flex are rudimentary, if used at all. Since he’s a Flex developer, it’s a pain he feels acutely. We agreed to work together to try to improve this.
A quick search on Google turns up FlexUnit and AsUnit. There is also the Automated Testing API on the other end.
How do you do functional testing with Flex? That’s the type of question we want to find answers to.
What kind of tools are needed? Do we want a recorder or UI scripting? Something like selenium? A test player? Performance tools? Randomized or parameterized data? Mocks or stubbing?
Just like on my other blogs, I’ll post links here for completeness and just in case anyone wants to get involved.
Here is the Fluffy QA Site with subversion, bugzilla, projectpier, trac, blogs, and forum.
What do I get out of it?
I get to learn Flex. And a project to work on with a friend. It’s my aim to also improve the QA site / PM site tools and process as well while working on this project. And maybe I’ll make some money out of it. Though if we do develop any tools, they’ll most likely be open sourced.
We welcome any other interested participants.
Recent Comments