dpUInt started as an internal project needed to test frameworks we were developing. FlexUnit was falling short for us and we couldn’t build an enterprise component framework without a way to test it continually and reliably.
It worked for our needs, so we documented some of it, provided some examples and put it online for the community. Now the community seems to be adopting it quickly, which is fantastic, but our to-do list of features and extensions is growing faster than we can tackle it.
So, we are looking for contributors. People who are serious about helping us take the next dpUInt release (the actual 1.0 version) to a better place with more support for automated build systems, automated test running and to realize the integrated code coverage tool completely.
If you have some spare cycles for a worthy testing framework in need of additional love, please let us know. Join the google code group and give us a hand..