@Shabbir Merchant, I thought about two other ways, unfortunately those are at a lower level:
1) Python unittest using XML/RPC directly. see http://docs.python.org/library/unittest.html and http://doc.openerp.com/developer/6_22_XML-RPC_web_services/index.html#python-example Basically starting thye GTK server with --l debug_rpc allows you to find out what would be the requests simulating a standard client inter-action. 2) Use Ruby RSpec behind my OpenERP Rails connector (yet to be announced officially) in much the same way. http://code.google.com/p/ooor/source/browse/trunk/README Still I agree those are unit test frameworks, not acceptance testing. I've no idea how exactly improve Selenium compatibility. Hope this testing thing gets support from the editor. Indeed, dynamic languages are cool and productive but without a strong test suite I think it' really risky and we saw lot's of regressions happening. The current built'in test framework is cool, but it's far from enough because it has no support at all to test just any Python method with arbitrary fixtures data or mockup, and no roll back support in order to test intensively and in an independent manner. Raphaël Valyi ------------------------ http://www.smile.fr -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=33996#33996 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
