Some of you may know that Digital Primates released a beta-quality testing framework some time back called dpUInt ( digital primates unit and integration). This started an internal framework we developed for testing UIComponent derivatives. One day we decided it was useful enough to share with the world, so we started a google code project and sent it off into the wild.
Then, wow. More people than we initially expected were running into the same problems we had encountered when testing Flex applications. Soon we were receiving emails and calls from companies using dpUInt who were curious about support and the future of the project. As of this moment, I know of at least a dozen well-known and respected software firms using it for their testing framework and hundreds of developers who have written me with question and suggestions.
Well, I am happy to say that dpUInt has grown up a bit and finally reached the 1.0 stage of its life. Based strongly on the feedback of its users, it is also adopting a new project name, Fluint (pronounced Fluent).
The new google code project, which can be found at http://fluint.googlecode.com/ has been refactored a bit. Instead of acting as a single library project, the new repository has top level directories for each of the following sub-projects:
fluint – Library project used to build fluint.swc
fluint_FlexTestRunner – Simple Flex project with a sample test runner
fluint_AIRTestRunner – AIR project designed to run tests from an automated build environment of simply via command line
fluint_AntTask – Ant Tasks that facilitate running the AIRTestRunner
fluint_Samples – Samples project that will grow to contain samples uses and modules
The source for all component, including the AIR test runner and ant tasks are now included.
Further, a few new features have made the jump to the new project as well:
- Ant tasks / AIR testing modules now supported (No need to recompile the test runner for new tests)
- AIR Test Runner with full source for command line and ANT invocation
- Improved performance
- Tests can now be marked by [Test] metadata which allows the inclusion of descriptions and additional metadata carried through to the testing UI
- And of course, bug fixes
While the code and the name are in better shape, we can still use help adding more documentation. So if you are up for helping improve the Wiki pages or for providing any additional forms of documentation including tutorials and videos, we are game.
The google code project has an issues tab for reporting any issues found during use. So, please report bugs or simply file enhancement requests. Planning for the 1.1 release is soon to be under way. We are already committed to simplifying the syntax and readability of testing sequences, but we need help to define what else is going to be on that list.