At 03:20 PM 6/5/2006 -0700, Mikeal Rogers wrote:
That framework, the one you had commented on previously, is still
being written. We were spending so much time maintaining the current
framework, and we had so much negative feedback during the last test
writing sprint, particularly about the logger, that we decided to
quickly make this update to chandler automation.
This framework will make the transition to the upcoming framework,
which we're calling OAF, a lot easier as well.
So to answer your question, since this framework was written only for
Chandler and written very quickly, it is out of scope for now. The
goals for OAF is end to end testing across all products in the
"ecosystem" and on the list of features for 1.0 is integration with
unittest.
No problem; I just want to make sure we don't end up with mutually
incompatible ways of doing things at the "platform" level. That is, the
long-term goal is that third-party plugin developers should have access to
the same functional testing tools that we use, and they should be able to
integrate with the unit testing tools that we also provide.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
