I just finished my presentation materials for my Test-driven development session at Adobe Max, and I am pretty excited how it turned out. It is a 90-minute BYOL (Bring your own laptop) lab, which is always challenging. Each person showing up with a diverse setup and (hopefully) our files installed.
So, if you are planning to head to Max, and you are interested in TDD, try to attend. I think it will be well worth the effort.
That said, there will also be two sessions at the 360|Flex Max unconference where we will be reviewing the FlexUnit 4 framework from the inside out. The goal here is to provide initial context for those interested in becoming committers on the project. FlexUnit 4 is a highly functional testing framework, but it is also complex. Until we have the chance to document every corner, this might be your best chance to learn the ins and outs of it.
Finally, working on this session has given me the opportunity to work with the FlexUnit plugin in Flash Builder. I must say I am very pleased with how this is evolving. Nonetheless, there are a few enhancements I would still like. If you are of a like mind, read through the bugs and cast your vote.
- Auto Refresh of the flex unit compiler application when deleting a test case or (minimally) re-running the wizard
Right now deleting a test case causes a manualy compilation error that needs resolution. I think this could be more elegant.
- Uncheck Create Constructor by default in FU4 test case
Just a minor inconvenience. You generally don’t need constructors in FU4 test cases, so you uncheck a checkbox… often
- Generate Before/After in place of setup/teardown for FU4 testcases
Right now the wizards don’t know how to generate the FU4 equivalent of setUp() and tearDown(). Not a big deal, but I think it’s low-hanging fruit.
- Remember Last Selected Type when creating test cases from the wizard
Just a minor inconvenience. You always need to re-select the radio button when using the wizard with FU4.