If you read our recent posts on ActionScript/Flex refactorings, you might have noticed that UML diagramming in freshly released IntelliJ IDEA 9 works not only for Java. That’s right, you can use it to analyze your ActionScript and Flex classes.
In addition to other refactorings, Maia also has this useful refactoring: push members down the classes hierarchy.
Again, let’s try it on a simple example.
Next Maia’s EAP will bring you new refactoring that helps to be more productive when coding ActionScript or Flex.
Now you can easily move static methods, properties, fields and constants between AS classes and Mxml components: just place caret on a member (or a reference to it) and hit F6 (Move action).
IntelliJ IDEA Team Foundation Server integration now supports checkin notes and policies. Checkin notes are the arbitrary text fields that you can associate with a checkin. You can mark them as mandatory, so that everyone will be required to type something before performing a checkin. This is handy, for example, when you need developers to provide a comment from manager who reviewed their code.
Checkin policies are the rules executed before every checkin to ensure that a selected changeset is OK to commit. For example, a policy may verify that a valid comment is specified for a changeset, or that required work items are associated with it, or that file names that it includes match corporate naming standatds, etc.
IntelliJ IDEA allows you to implement custom policies in the form of plugins and configure them on a server.
This functionality is available in both IntelliJ IDEA 8 and Maia. For more information refer to this Confluence page.
Maia includes support for running FlexUnit 4 tests. All you need is to a add dependency to FlexUnit4.swc library and your FlexUnit4-style tests will be recognized and run. FlexUnit4 runner supports legacy tests (FlexUnit 0.9 and Flunit), so you don’t have to worry about existing code. Maia also includes some nifty testing support features:
Test with pleasure!
Maia is capable of running FlexUnit tests — you can run a single test method, all methods in a certain class, or all classes in a given package and its subpackages. For that, you’re provided with a new FlexUnit Run Configuration, which allows you to specify a module (Flex module or Java module with Flex facet) and configure the test scope:
To run tests you need to set up a dependency on FlexUnit.swc library, but this is something you must have already done to get your tests compiled. Tests are actually executed in debug mode with all the functionality like breakpoints, watches, etc. available.
When a run is finished the results window shows you the tests overview, output and statistics panel:
Mouse click on an item in the tree or statistics panel navigates you to the test source. Same is true for the stack traces of the failed tests.
Also, new context menu actions are provided to run test for a selected method, class, or package. Just right-click them and select Debug Flex, then click FlexUnit.
Twitts about IntelliJ IDEA
